-
Notifications
You must be signed in to change notification settings - Fork 0
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 moby#7186 from jamtur01/community
Added proposed Docker Community Guidelines
- Loading branch information
Showing
1 changed file
with
61 additions
and
0 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 |
---|---|---|
|
@@ -242,3 +242,64 @@ Don't forget: being a maintainer is a time investment. Make sure you | |
will have time to make yourself available. You don't have to be a | ||
maintainer to make a difference on the project! | ||
|
||
## Docker Community Guidelines | ||
|
||
We want to keep the Docker community awesome, growing and collaborative. We | ||
need your help to keep it that way. To help with this we've come up with some | ||
general guidelines for the community as a whole: | ||
|
||
* Be nice: Be courteous, respectful and polite to fellow community members: no | ||
regional, racial, gender, or other abuse will be tolerated. We like nice people | ||
way better than mean ones! | ||
|
||
* Encourage diversity and participation: Make everyone in our community | ||
feel welcome, regardless of their background and the extent of their | ||
contributions, and do everything possible to encourage participation in | ||
our community. | ||
|
||
* Keep it legal: Basically, don't get us in trouble. Share only content that | ||
you own, do not share private or sensitive information, and don't break the | ||
law. | ||
|
||
* Stay on topic: Make sure that you are posting to the correct channel | ||
and avoid off-topic discussions. Remember when you update an issue or | ||
respond to an email you are potentially sending to a large number of | ||
people. Please consider this before you update. Also remember that | ||
nobody likes spam. | ||
|
||
### Guideline Violations — 3 Strikes Method | ||
|
||
The point of this section is not to find opportunities to punish people, but we | ||
do need a fair way to deal with people who are making our community suck. | ||
|
||
1. First occurrence: We'll give you a friendly, but public reminder that the | ||
behavior is inappropriate according to our guidelines. | ||
|
||
2. Second occurrence: We will send you a private message with a warning that | ||
any additional violations will result in removal from the community. | ||
|
||
3. Third occurrence: Depending on the violation, we may need to delete or ban | ||
your account. | ||
|
||
**Notes:** | ||
|
||
* Obvious spammers are banned on first occurrence. If we don't do this, we'll | ||
have spam all over the place. | ||
|
||
* Violations are forgiven after 6 months of good behavior, and we won't | ||
hold a grudge. | ||
|
||
* People who commit minor infractions will get some education, | ||
rather than hammering them in the 3 strikes process. | ||
|
||
* The rules apply equally to everyone in the community, no matter how | ||
much you've contributed. | ||
|
||
* Extreme violations of a threatening, abusive, destructive or illegal nature | ||
will be addressed immediately and are not subject to 3 strikes or | ||
forgiveness. | ||
|
||
* Contact [email protected] to report abuse or appeal violations. In the case of | ||
appeals, we know that mistakes happen, and we'll work with you to come up with | ||
a fair solution if there has been a misunderstanding. | ||
|