Typos, Formatting, and COC Template #40
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi All,
This pull request includes several non-policy, and hopefully non-controversial, updates to the conda governance proposal:
Typos and formatting in the main governance doc (README.md).
These are all in this commit. Changes are all for typos, formatting, and what I thought were straightforward clarity changes. (I'll be creating an issue shortly about any clarity questions that I didn't think were straightforward.)
Replaces a link to code of conduct for NumFOCUS organization, with a copy of the NumFOCUS template
If the section title is confusing then please read it again, and also follow the links. Here's what's happening.
Our previous COC was the NumFOCUS Organization's COC. That is, we were using the COC that governs interactions within NumFOCUS. The NumFOCUS COC is not written to govern interaction in projects that belong to NumFOUCS. Linking to this COC communicates our intentions, but in a confusing way.
The PR creates our own COC. This COC is based on the NumFOCUS template for member communities. This template was also used to create the NumFOCUS COC.
The template has a number of placeholders that are meant to be replaced when deployed to member communities. However, this PR only updates the project name in our version. Other placeholders are left in place because these require significant discussion.
Summary
There are no policy changes in this PR. This is only meant to make things less confusing before we take on any policy updates.