WAITP-1502: code guidelines #5293
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
edmofro
requested changes
Dec 21, 2023
|
|
||
| This project and everyone participating in it is governed by the | ||
| [BES Open Source Code of Conduct](code-of-conduct.md). | ||
| By participating, you are expected to uphold this code. Please report unacceptable behaviour to [opensource@bes.au](opensource@bes.au). |
There was a problem hiding this comment.
Have created this email address, forwards to me
| All open-source contributors to Tupaia will be required to sign a Contributor License Agreement (CLA) | ||
| before BES can accept your contribution into the project code. This is done so that we can continue | ||
| to maintain the codebase covered by a single license. Signing a CLA can be done through GitHub | ||
| before merging in your first pull request. |
There was a problem hiding this comment.
I actually copied this from Michelle's and it was reviewed by Felix, so I assume that's right? But also happy to remove
| to maintain a cohesive vision for the project. While we encourage collaboration and contributions, | ||
| we also want to avoid fragmentation that could compromise Tupaia's usability, maintainability, | ||
| and value. We believe that the best way to contribute is to align your efforts with our existing | ||
| product roadmap. |
There was a problem hiding this comment.
I recognise this as my own writing! Nice. Must've come through from Slab.
.github/code-of-conduct.md
Outdated
Comment on lines
47
to
71
| ## Enforcement guidelines | ||
|
|
||
| ### 1. Correction | ||
|
|
||
| Community Impact: Use of inappropriate language or other behaviour deemed unprofessional or unwelcome in the community. | ||
|
|
||
| Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behaviour was inappropriate. A public apology may be requested. | ||
|
|
||
| ### 2. Warning | ||
|
|
||
| Community Impact: A violation through a single incident or series of actions. | ||
|
|
||
| Consequence: A warning with consequences for continued behaviour. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. | ||
|
|
||
| ### 3. Temporary Ban | ||
|
|
||
| Community Impact: A serious violation of community standards, including sustained inappropriate behaviour. | ||
|
|
||
| Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. | ||
|
|
||
| ### 4. Permanent Ban | ||
|
|
||
| Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. | ||
|
|
||
| Consequence: A permanent ban from any sort of public interaction within the community. |
There was a problem hiding this comment.
I think we can simplify these, given how immature and small our community is likely to be. Let's just go for "1. Warning" and "2. Temporary or Permanent Ban". The first can have the content from the existing "Correction", and the second the content from the "Temporary Ban" with a tweak:
"A ban from any sort of interaction or public communication with the community, either permanently or for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period."
Co-authored-by: Edwin Monk-Fromont <edwin.monkfromont@gmail.com>
Co-authored-by: Edwin Monk-Fromont <edwin.monkfromont@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue WAITP-1502: code guidelines
Changes: