https://github.com/mymicds/mymicds-code-of-conduct
Collection of documents establishing the code of conduct and team norms and roles for MyMICDS
https://github.com/mymicds/mymicds-code-of-conduct
micds mymicds
Last synced: 3 months ago
JSON representation
Collection of documents establishing the code of conduct and team norms and roles for MyMICDS
- Host: GitHub
- URL: https://github.com/mymicds/mymicds-code-of-conduct
- Owner: MyMICDS
- License: mit
- Created: 2017-11-21T22:04:23.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-01-04T22:34:40.000Z (over 7 years ago)
- Last Synced: 2025-01-08T03:53:55.514Z (4 months ago)
- Topics: micds, mymicds
- Size: 4.88 KB
- Stars: 0
- Watchers: 4
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# MyMICDS Code of Conduct
## Goal
This repository is aimed at establishing a code of conduct, team norms, and different roles for developers on MyMICDS.
## Scope
The [CODE_OF_CONDUCT.md](#) is adapted from the Contributor Covenant Code of Conduct. This is a generic open-source "Code of Conduct." In addition to this Contributor Covenant, other files are specific to the leadership and organization of MyMICDS.
The sets of rules outlined in this repository apply to all repositories under the MyMICDS organization whether under the MyMICDS GitHub organization or not. This also applies to any forms of communication about MyMICDS such as face-to-face conversation or under online communications like the MyMICDS Slack.
## Enforcement
This Code of Conduct is meant to be a general guide so the vision can stay aligned as passed down from student to student. Favor "the spirit of the law" compared to the "rule of the law" or what the words literally say. Members violating of this Code of Conduct should receive proper warning, and if problems continue, be dismissed from the development team.
## Revisions
This Code of Conduct is meant to be a set of rather static rules. Revisions should only be made via Pull Requests after the initial drafting stage (before and including commit hash [#XXXXXX](#)). **A Pull Request after the drafting period should be made for every change, no matter how small (Yes, even a typo!)** Pull Requests must then be reviewed and approved by designated leader [(see team roles)](#) and and at least a majority of active developers [(see team roles)](#).