-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #17 from js6450/patch-1
Suggesting potential structure for Code of Conduct
- Loading branch information
Showing
1 changed file
with
16 additions
and
2 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,21 @@ | ||
# Code of Conduct | ||
|
||
|
||
1. (Should we only provide technical guidelines or include rules in concept as mentioned in What does "Open Source Even Mean"?) | ||
2. I think the Recurse Center's code of conduct would be a good reference if we decide to write our own: https://www.recurse.com/code-of-conduct | ||
3. In service of reuse, I think we should build upon what others have already done.. https://help.github.com/articles/github-community-forum-code-of-conduct/ | ||
4. Is it acceptable to work on this during class? | ||
4. Is it acceptable to work on this during class? | ||
|
||
|
||
If we were to write our own, below is a potential structure (based on the [Contributor Covenant's Code of Conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct.txt)): | ||
|
||
## Our Pledge | ||
|
||
## Our Standards | ||
|
||
## Our Responsibilities | ||
|
||
## Scope | ||
|
||
## Enforcement | ||
|
||
## Attribution |