The code of conduct #1692

aliveevie · 2022-04-07T13:39:57Z

PR Checklist:

make all edits to the docs in the src directory, not in docs or in the html files
note any issues closed by this PR with closing keywords
put any other relevant information below

kathatherine

Thanks so much! You should also make this a .rst file instead of a .md file.

kathatherine · 2022-04-12T23:07:43Z

aliveevie/code_of_conduct.md

@@ -0,0 +1,48 @@
+# code of conduct and reporting guidelines


Headers should have the first word capitalized.

Also, please put a blank line between a header and any content beneath it.

Let's put -------- under this first header, to move it up one header level.

kathatherine · 2022-04-12T23:09:04Z

aliveevie/code_of_conduct.md

@@ -0,0 +1,48 @@
+# code of conduct and reporting guidelines
+# Teams & Roles


And another blank line is needed beneath this header as well.

kathatherine · 2022-04-12T23:09:32Z

aliveevie/code_of_conduct.md

@@ -0,0 +1,48 @@
+# code of conduct and reporting guidelines
+# Teams & Roles
+Here are defined the primary teams participating in conda-forge activities.


This sentence should end in a colon, since it is introducing a list. And it also needs a blank line beneath it.

kathatherine · 2022-04-12T23:13:39Z

aliveevie/code_of_conduct.md

+- **external contributors:** This group encompasses all others who are not on core, part of staged-recipes, or maintainers. This includes first-time contributors, collaborators, and funders. They have no special rights within the conda-forge organization itself.
+
+- **emeritus-core:** Core members that are inactive (commits, GitHub comments/issues/reviews, dev meetings and voting on polls) in the past six months will be asked if they want to become emeritus-core developers. Any core member can also request to become emeritus if they wish to do so (e.g. taking a sabbatical or long vacation). Emeritus core members can still vote and move back to active core anytime. Emeritus votes are used to count towards quorum but the quorum size is computed from the size of the active core group. The core.csv list should be updated when a change in the status of a member occurs.
+


Did you get the information above from anywhere in particular or did you do some research and put it together?

kathatherine · 2022-04-12T23:17:25Z

aliveevie/code_of_conduct.md

+
+- **emeritus-core:** Core members that are inactive (commits, GitHub comments/issues/reviews, dev meetings and voting on polls) in the past six months will be asked if they want to become emeritus-core developers. Any core member can also request to become emeritus if they wish to do so (e.g. taking a sabbatical or long vacation). Emeritus core members can still vote and move back to active core anytime. Emeritus votes are used to count towards quorum but the quorum size is computed from the size of the active core group. The core.csv list should be updated when a change in the status of a member occurs.
+
+## Sub-Teams


You also need a blank line beneath this header.

kathatherine · 2022-04-12T23:19:33Z

aliveevie/code_of_conduct.md

+
+- There should always be an option to abstain from voting.
+
+- Voting items are labeled as either standard or sensitive. Standard items are ones where public record and discourse is preferable. Sensitive voting items are ones where the results of the vote should remain private to the voters after the vote has occurred. Sensitive votes should take place on a secure anonymous voting platform in order to retain election integrity and anonymity. (We have used Polys and the Helios voting system, but are open to any secure, anonymous system.) The email capability of your chosen voting platform should be used for sending voting invitations and reminders, and you should use the email list from https://github.com/conda-forge/conda-forge.github.io/blob/main/src/core.csv and https://github.com/conda-forge/conda-forge.github.io/blob/main/src/emeritus.csv as the authoritative list of emails to use.


Let's make those CSV links into actual links.

kathatherine · 2022-04-12T23:19:53Z

aliveevie/code_of_conduct.md

+
+- The default voting period is 1 week (7 days). This may be modified at the time when a vote is called, but may never be less than 24 hrs.
+
+- Additional requirements may apply in case low turnouts have to be handled, see “Quorum” below.


I don't see a Quorum section.

jaimergp · 2023-06-22T11:13:17Z

#1640

The code of conduct

9ff9b62

aliveevie requested a review from a team as a code owner April 7, 2022 13:39

kathatherine suggested changes Apr 12, 2022

View reviewed changes

jaimergp closed this Jun 22, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The code of conduct #1692

The code of conduct #1692

aliveevie commented Apr 7, 2022

kathatherine left a comment

kathatherine Apr 12, 2022

kathatherine Apr 12, 2022

kathatherine Apr 12, 2022

kathatherine Apr 12, 2022

kathatherine Apr 12, 2022

kathatherine Apr 12, 2022

kathatherine Apr 12, 2022

kathatherine Apr 12, 2022

kathatherine Apr 12, 2022

jaimergp commented Jun 22, 2023

		@@ -0,0 +1,48 @@
		# code of conduct and reporting guidelines
		# Teams & Roles

		- external contributors: This group encompasses all others who are not on core, part of staged-recipes, or maintainers. This includes first-time contributors, collaborators, and funders. They have no special rights within the conda-forge organization itself.

		- emeritus-core: Core members that are inactive (commits, GitHub comments/issues/reviews, dev meetings and voting on polls) in the past six months will be asked if they want to become emeritus-core developers. Any core member can also request to become emeritus if they wish to do so (e.g. taking a sabbatical or long vacation). Emeritus core members can still vote and move back to active core anytime. Emeritus votes are used to count towards quorum but the quorum size is computed from the size of the active core group. The core.csv list should be updated when a change in the status of a member occurs.


		- emeritus-core: Core members that are inactive (commits, GitHub comments/issues/reviews, dev meetings and voting on polls) in the past six months will be asked if they want to become emeritus-core developers. Any core member can also request to become emeritus if they wish to do so (e.g. taking a sabbatical or long vacation). Emeritus core members can still vote and move back to active core anytime. Emeritus votes are used to count towards quorum but the quorum size is computed from the size of the active core group. The core.csv list should be updated when a change in the status of a member occurs.

		## Sub-Teams


		- There should always be an option to abstain from voting.

		- Voting items are labeled as either standard or sensitive. Standard items are ones where public record and discourse is preferable. Sensitive voting items are ones where the results of the vote should remain private to the voters after the vote has occurred. Sensitive votes should take place on a secure anonymous voting platform in order to retain election integrity and anonymity. (We have used Polys and the Helios voting system, but are open to any secure, anonymous system.) The email capability of your chosen voting platform should be used for sending voting invitations and reminders, and you should use the email list from https://github.com/conda-forge/conda-forge.github.io/blob/main/src/core.csv and https://github.com/conda-forge/conda-forge.github.io/blob/main/src/emeritus.csv as the authoritative list of emails to use.


		- The default voting period is 1 week (7 days). This may be modified at the time when a vote is called, but may never be less than 24 hrs.

		- Additional requirements may apply in case low turnouts have to be handled, see “Quorum” below.

The code of conduct #1692

The code of conduct #1692

Conversation

aliveevie commented Apr 7, 2022

kathatherine left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jaimergp commented Jun 22, 2023