Add contributor convenant 3.0 as code of conduct#104
Open
florisdenhengst wants to merge 2 commits into
Open
Conversation
kgd-al
requested changes
Jun 9, 2026
kgd-al
left a comment
kgd-al
left a comment
Contributor
There was a problem hiding this comment.
The core of the code looks good to me. We do need to discuss the specifics though
|
|
||
| Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm. | ||
|
|
||
| When an incident does occur, it is important to report it promptly. To report a possible violation, **[NOTE: describe your means of reporting here.]** |
Contributor
There was a problem hiding this comment.
Definitively need to have something here
|
|
||
| When an incident does occur, it is important to report it promptly. To report a possible violation, **[NOTE: describe your means of reporting here.]** | ||
|
|
||
| Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution. |
Contributor
There was a problem hiding this comment.
Do we need to design/elect/request for volunteering such community moderators?
Collaborator
Author
There was a problem hiding this comment.
I think we could adopt the following strategy which is set-and-forget:
When an incident does occur, it is important to report it promptly. We use GitHub's **Private Vulnerability Reporting** to enable reporting Code of Conduct violations in a private, and secure manner. You must have a GitHub account to use this method.
To submit a private report:
1. Navigate to the main page of this GitHub repository.
2. Click on the **Security** tab located under the repository name.
3. In the left sidebar, click on **Reporting**.
4. Click the **Report a vulnerability** button.
5. In your report, clearly state in the description that this is a **Code of Conduct Violation**, and provide details of the incident (including links or screenshots if applicable).
### Conflict of Interest Bypass
Because we are a very small academic team, private repository reports will automatically notify all core repository maintainers.
If your report involves a specific maintainer of this project and you do not want them to see it, **do not use the GitHub Security tab**. Instead, please reach out directly to an alternative team member or a neutral departmental ally via their institutional email:
* **Alternative Contact A:** Firstname1 Lastname1 — [first name and last name without whitespace]at[google's mail service]
* **Alternative Contact B:** Firstname2 Lastname2 - [first name and last name without whitespace]at[uni.nl]We'll have to discuss who these alternative contacts are and how to reach them though
| ## Addressing and Repairing Harm | ||
|
|
||
| **[NOTE: The remedies and repairs outlined below are suggestions based on best practices in code of conduct enforcement. If your community has its own established enforcement process, be sure to edit this section to describe your own policies.]** | ||
|
|
| 3) Repair: There is no possible repair in cases of this severity. | ||
|
|
||
| This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community. | ||
|
|
Contributor
There was a problem hiding this comment.
Should we be more explicit about the actions? It seems github does have moderation tools available: https://docs.github.com/en/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #103
Add contributor convenant 3.0 as code of conduct