Added proposed Docker Community Guidelines
| ... | ... |
@@ -242,3 +242,64 @@ Don't forget: being a maintainer is a time investment. Make sure you |
| 242 | 242 |
will have time to make yourself available. You don't have to be a |
| 243 | 243 |
maintainer to make a difference on the project! |
| 244 | 244 |
|
| 245 |
+## Docker Community Guidelines |
|
| 246 |
+ |
|
| 247 |
+We want to keep the Docker community awesome, growing and collaborative. We |
|
| 248 |
+need your help to keep it that way. To help with this we've come up with some |
|
| 249 |
+general guidelines for the community as a whole: |
|
| 250 |
+ |
|
| 251 |
+* Be nice: Be courteous, respectful and polite to fellow community members: no |
|
| 252 |
+ regional, racial, gender, or other abuse will be tolerated. We like nice people |
|
| 253 |
+ way better than mean ones! |
|
| 254 |
+ |
|
| 255 |
+* Encourage diversity and participation: Make everyone in our community |
|
| 256 |
+ feel welcome, regardless of their background and the extent of their |
|
| 257 |
+ contributions, and do everything possible to encourage participation in |
|
| 258 |
+ our community. |
|
| 259 |
+ |
|
| 260 |
+* Keep it legal: Basically, don't get us in trouble. Share only content that |
|
| 261 |
+ you own, do not share private or sensitive information, and don't break the |
|
| 262 |
+ law. |
|
| 263 |
+ |
|
| 264 |
+* Stay on topic: Make sure that you are posting to the correct channel |
|
| 265 |
+ and avoid off-topic discussions. Remember when you update an issue or |
|
| 266 |
+ respond to an email you are potentially sending to a large number of |
|
| 267 |
+ people. Please consider this before you update. Also remember that |
|
| 268 |
+ nobody likes spam. |
|
| 269 |
+ |
|
| 270 |
+### Guideline Violations — 3 Strikes Method |
|
| 271 |
+ |
|
| 272 |
+The point of this section is not to find opportunities to punish people, but we |
|
| 273 |
+do need a fair way to deal with people who are making our community suck. |
|
| 274 |
+ |
|
| 275 |
+1. First occurrence: We'll give you a friendly, but public reminder that the |
|
| 276 |
+ behavior is inappropriate according to our guidelines. |
|
| 277 |
+ |
|
| 278 |
+2. Second occurrence: We will send you a private message with a warning that |
|
| 279 |
+ any additional violations will result in removal from the community. |
|
| 280 |
+ |
|
| 281 |
+3. Third occurrence: Depending on the violation, we may need to delete or ban |
|
| 282 |
+ your account. |
|
| 283 |
+ |
|
| 284 |
+**Notes:** |
|
| 285 |
+ |
|
| 286 |
+* Obvious spammers are banned on first occurrence. If we don't do this, we'll |
|
| 287 |
+ have spam all over the place. |
|
| 288 |
+ |
|
| 289 |
+* Violations are forgiven after 6 months of good behavior, and we won't |
|
| 290 |
+ hold a grudge. |
|
| 291 |
+ |
|
| 292 |
+* People who commit minor infractions will get some education, |
|
| 293 |
+ rather than hammering them in the 3 strikes process. |
|
| 294 |
+ |
|
| 295 |
+* The rules apply equally to everyone in the community, no matter how |
|
| 296 |
+ much you've contributed. |
|
| 297 |
+ |
|
| 298 |
+* Extreme violations of a threatening, abusive, destructive or illegal nature |
|
| 299 |
+ will be addressed immediately and are not subject to 3 strikes or |
|
| 300 |
+ forgiveness. |
|
| 301 |
+ |
|
| 302 |
+* Contact james@docker.com to report abuse or appeal violations. In the case of |
|
| 303 |
+ appeals, we know that mistakes happen, and we'll work with you to come up with |
|
| 304 |
+ a fair solution if there has been a misunderstanding. |
|
| 305 |
+ |