[FFmpeg-devel,RFC,Type,1] developers: Add a section on CoC enforcemnet

Submitted by Derek Buitenhuis on May 14, 2018, 4:50 p.m.

Details

Message ID 1526316627-25927-2-git-send-email-derek.buitenhuis@gmail.com
State New
Headers show

Commit Message

Derek Buitenhuis May 14, 2018, 4:50 p.m.
This is currently directly copied from the VideoLAN CoC[1] in
order to spur discussion.

[1] https://wiki.videolan.org/Code_of_Conduct/#Disciplinary_actions

Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
---
 doc/developer.texi | 83 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 83 insertions(+)

Patch hide | download patch | download mbox

diff --git a/doc/developer.texi b/doc/developer.texi
index a0eeefe..50b5153 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -421,6 +421,7 @@  We think our rules are not too hard. If you have comments, contact us.
 
 @chapter Code of conduct
 
+@section Code of conduct text
 Be friendly and respectful towards others and third parties.
 Treat others the way you yourself want to be treated.
 
@@ -448,6 +449,88 @@  instead and point them in the right direction.
 Finally, keep in mind the immortal words of Bill and Ted,
 "Be excellent to each other."
 
+@section Escalation
+@enumerate
+
+@item
+The first violation will always result in a simple warning, except if it is a grave or
+deliberate violation. 
+
+@item
+The following violations will result in some of the disciplinary actions listed in the
+paragraphs below.
+
+@item
+For repetitive violations, the case may be escalated to a vote for further disciplinary
+actions. 
+@end enumerate
+
+@section Disciplinary Actions 
+The following disciplinary actions may be enforced when a direct Code of Conduct violation
+is reported. 
+
+NB: Before applying any of the following disciplinary policies, the FFmpeg members will
+try to discuss the problem with the offender in order to solve it in a more peaceful way.
+However, it is possible for memberss to apply the penalty without discussions in severe
+Code of Conduct violations. 
+
+@subheading Mailing lists
+@itemize @bullet
+
+@item
+The netiquette violations will get only a warning. Repeated netiquette violations will be escalated.
+
+@item
+24-hour ban from the mailing list in question.
+
+@item
+Every third violation, the contributor will get a 7-day ban.
+
+@item
+As one cannot develop without the mailing lists, a ban from the ffmpeg-devel mailing list will result in
+a ban from commit access for one day on the related project. For spam violations, the first ban can be
+longer or infinite. 
+@end itemize
+
+@subheading IRC
+@itemize @bullet
+
+@item
+Direct kick for minor violations, enforced by channels ops.
+
+@item
+Other violations will get a 24-hour ban from the IRC channel.
+
+@item
+Every third violation, the offender will have a 7-day ban. 
+@end itemize
+
+@subheading Bugtracker
+@itemize @bullet
+
+@item
+24-hour ban from trac.
+
+@item
+Removal of developer or admin rights.
+
+@item
+Every third violation, the offender will be banned for 7 days.
+
+@item
+Every third violation, a developer may lose commit access for 7 days. 
+@end itemize
+
+@subheading Code Repository
+@itemize @bullet
+
+@item
+24-hour ban from commit access. 
+
+@item
+Every third violation, the developer will lose commit access for 7 days. 
+@end itemize
+
 @anchor{Submitting patches}
 @chapter Submitting patches