-
Notifications
You must be signed in to change notification settings - Fork 44
Add a general CoC for LDK contributors #184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
# LDK Code of Conduct | ||
|
||
The LDK community is open to pretty much anyone. To ensure that project forums such as the Discord server and GitHub repository are open and friendly, we count on maintainers and project representatives to behave in a way that is not disruptive to LDK's culture or to any one participant's well-being. | ||
|
||
Therefore, we came up with some easy to follow guidelines. | ||
* Be friendly. Interact in a way that fosters openness, inclusivity, and collaboration. | ||
* Be respectful. We may disagree, but disagreement is no excuse for rude behavior or personal attacks. | ||
* Be considerate. Provide and accept constructive criticism. | ||
|
||
Private or public harassment of any kind will not be tolerated. Since harassment can take many forms, here's a non-exhaustive list of what we consider unacceptable behavior: | ||
* Offensive language directed at individuals or groups of people | ||
* Bullying (verbal, physical, social, or cyber) | ||
* Interfering with someone's ability to contribute, like with excessive nitpicking | ||
* Continued one-on-one communication after a party has requested it cease | ||
* Stalking online or offline | ||
* Doxing or unauthorized publication of private information or communication | ||
* Unwelcomed sexual attention | ||
* Inappropriate visual displays such as sexually-oriented or offensive photography, cartoons, drawings, or gestures | ||
* Retaliation for reporting or threatening to report harassment | ||
|
||
Additionally, spam and other content which disrupts or prevents LDK contributors from working on LDK is not acceptable. | ||
|
||
## The Code of Conduct Team | ||
|
||
A small team of LDK contributors has volunteered to enforce the LDK Code of Conduct. If you feel like a community member has engaged in inappropriate behavior, please don't hesitate to contact one of the following LDK contributors via email or on Discord: | ||
* Matt Corallo - ldkcocpoc on mattcorallo.com | ||
* Val Wallace - vwallace on protonmail.com | ||
* Devrandom - devrandom99 on proton.me | ||
|
||
## The Code of Conduct Team’s Responsibilities | ||
|
||
Team members are tasked with responding to reports within 24 hours. They will review each incident and determine, to the best of their ability: | ||
* Does the event constitute a Code of Conduct violation? | ||
* Is the behavior on our list of inappropriate behavior? Is it borderline inappropriate? | ||
* Did the event occur in a space within our Code of Conduct's scope? | ||
* If the incident occurred outside community forums and the individual is seen as a project representative or identifies as an LDK contributor, the incident may be in scope. | ||
* Additionally, an incident may be in scope if a community member's ability to contribute to LDK is impacted. | ||
* Did this incident occur in a private conversation or in a public space? | ||
* Is the situation isolated or ongoing? | ||
* How is the reported person's behavior negatively impacting others? | ||
* Does the incident impact the ability of individuals to freely contribute to LDK? | ||
* Does this incident include sexual harassment? | ||
* Does this pose a safety risk or severely negatively impact someone's mental health? | ||
* Is there a risk of this behavior being repeated? | ||
* Does the reported person understand why their behavior was inappropriate? | ||
|
||
If a report is insufficiently detailed or involves multiple parties, the Code of Conduct Team may seek additional information from witnesses or the accused. Neither party should contact the other to discuss the incident. Likewise, the team will do its best not to disclose who reported a given incident, either to the accused or generally, though we recognize that circumstantial disclosures to the accused might be unavoidable. | ||
|
||
The Code of Conduct Team aims to resolve all reports within one week. If a resolution is not possible within that time frame, the team will respond to the reporter(s) with an adjusted one. | ||
|
||
## Possible responses to an incident include: | ||
|
||
### Taking no further action: | ||
If the Code of Conduct Team determines that no action is needed, they will inform the reporter. | ||
|
||
### Simple warning: | ||
This applies to disruptive behavior, but not insulting behavior. The Code of Conduct Team will contact the individual(s) and request that they stop. | ||
|
||
### Final warning: | ||
If an incident or series of incidents creates sustained toxicity within the LDK Community, the Code of Conduct Team will sternly warn the reported party and raise the possibility of further disciplinary action. In addition, they may request that the reported party: | ||
* Not use specific language | ||
* Not participate in specific types of discussions | ||
* Not send private messages to a community member | ||
* Not review a particular person's PRs on GitHub (but still allow them to privately share review comments with a maintainer) | ||
* Not lead sub-projects like code review sessions | ||
* Take a step away for a short period to cool off | ||
* Lose maintainer/merge access | ||
|
||
### 2-3 months imposed break: | ||
If the Code of Conduct Team’s warning goes unheeded, the individual(s) may be asked to avoid participating with the LDK Community on its preferred platforms for several months. After time has passed, the individual(s) will have the option of meeting with the team to discuss returning to the community. | ||
|
||
### Extended or permanent ban: | ||
If a temporary break does not remedy a serious offense, the offender may be removed from the Discord server and Github repository. The Code of Conduct Team may also choose to un-ban a user for a first offense, depending on its severity and pending that the user has offered the offended party a genuine apology. |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know much familiarity people have with the notion of "due process" in vigor in most of respectable jurisdictions, and the rights of the defense -- Here we should give far more prerogatives to the "accused" for a fair trial, otherwise we open the door to pure arbitrary. Being an online community doesn't exempt us to respect the defense principles recognized by numerous international treatises and constitutions all around the world.
Among the rights of the defense:
The default delay of 1 week sounds very far from reasonable to produce a grounded defense for the accused and in fact no delay should be given -- It should be function of the respect of the procedural steps guaranteeing the fairness of the disciplinary process.