Difference between revisions of "Code of Conduct"

From VideoLAN Wiki
Jump to navigation Jump to search
 
(82 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
<big><big>THIS IS AN UNDERGOING text</big></big>
+
{{DISPLAYTITLE:VideoLAN Code of Conduct}}
  
−
Cf https://openhatch.org/wiki/Project_codes_of_conduct
+
You should check out our [[VideoLAN_Values|shared values]].
  
−
= Values overview =
+
= Communications rules =
 +
The following rules apply to all means of communication, online and in real life.
 +
* Do not use foul language, and absolutely NO insults will be tolerated.
 +
* Be careful with direct criticism:
 +
** Focus on the possible improvements and do not make the issue a personal one.
 +
** You should, when possible, criticize in private, and praise publicly; since most of our communications are public and people can be sensitive about that.
 +
* ''Ad hominem'' attacks are not accepted.
 +
* Do not flame or troll; it is not funny.
 +
* Do not undo someone's else contribution (wiki edits, code reverts, etc...) without asking first.
 +
* Send all communication in English.
 +
** The ''videolan@'' mailing list, wiki translated pages, and forum-specific topics allow different languages, when clearly flagged.
 +
* Do not send spam.
 +
* Do not abuse administrative powers.
 +
* These Code of Conduct rules are not exhaustive; please use common sense, to infer other rules.
  
−
This Code of Conduct presents a vision of the shared values and thinking in the VideoLAN community.
+
== Mailing lists ==
 +
When using the VideoLAN mailing lists, please follow also these simple rules:
  
−
In short:
+
* The mailing lists exist to foster the development and use of VideoLAN. Unconstructive and off-topic messages, along with other abuse, are not welcome.
−
* '''Be considerate and respectful'''
+
* Make sure that you are using the proper list. In particular, don't send user-related questions to developer mailing lists.
−
* '''Be collaborative'''
+
* If you want to explain to someone how to use a mailing list, please do it privately.
−
* '''Be pragmatic and concise'''
+
* Do not quote messages that were sent to you by other people in private mail, unless agreed beforehand.
−
* '''Ask if you don't know, share if you know'''
+
* When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly requested to be copied. When replying on a private mailing list, this does not apply as the recipient would not be able to read the reply otherwise.
−
* '''Be inclusive'''
+
* If you send messages to lists to which you are not subscribed, always note that fact in the body of your message.
−
* '''Be patient'''
 
−
 
 
−
== Be considerate and respectful ==
 
−
VideoLAN has millions of users and hundreds of contributors. What you do and contribute will impact the life of others. Think about your actions.
 
−
 
 
−
There is absolutely no excuse for personal attacks, racism, sexism or any other form of discrimination based on religion, politics, Linux distribution, Operating System or else.<br />
 
−
Respect everyone, no matter what is their level of implication in VideoLAN.
 
−
 
 
−
In a disagreement, in the first instance assume that people mean well. A community where people feel comfortable is a productive one.
 
−
 
 
−
== Be collaborative ==
 
−
 
 
−
== Be pragmatic and concise ==
 
  
−
== Ask if you don't know, share if you know ==
+
=== Mailing list Etiquette ===
−
 
 
−
== Be inclusive ==
 
−
 
 
−
== Be patient ==
 
−
 
 
−
= Means of communications =
 
−
Valid for all means of communications:
 
−
* Do not use foul language.
 
−
* Try not to flame; it is not polite.
 
−
* Use common sense all the time.
 
−
 
 
−
== Mailing lists ==
 
−
When using the VideoLAN mailing lists, please follow these rules:
 
−
 
 
−
* The mailing lists exist to foster the development and use of VideoLAN. Non-constructive or off-topic messages, along with other abuses, are not welcome.
 
−
* Do not send spam.
 
−
* Send all of your e-mails in English. Only use other languages on mailing lists where that is explicitly allowed (e.g. French on debian-user-french).
 
−
* Make sure that you are using the proper list. In particular, don't send user-related questions to developer-related mailing lists.
 
 
* Wrap your lines at 80 characters or less for ordinary discussion. Lines longer than 80 characters are acceptable for computer-generated output (e.g., ls -l).
 
* Wrap your lines at 80 characters or less for ordinary discussion. Lines longer than 80 characters are acceptable for computer-generated output (e.g., ls -l).
−
* Do not top-post, unless it makes sense.
+
* Avoid top-posting in conversations.
−
* Never send your messages in HTML-only; use plain text instead.
+
* Avoid HTML-only messages; have a plain text version instead.
−
* Avoid sending large attachments. Attachments over 65k are usually moderated.
+
* Avoid sending large attachments; mails with attachments over 65kb will have to be moderated by administrators.
 
* Do not send automated "out-of-office" or "vacation" messages.
 
* Do not send automated "out-of-office" or "vacation" messages.
−
* Do not send "test" messages to determine whether your mail client is working. We have a test mailing list for that.
+
* Do not send "test" messages to determine whether your mail client is working. We have a [https://mailman.videolan.org/listinfo/test test mailing list] for that.
 
* Do not send subscription or unsubscription requests to the list address itself; use the respective -request address instead.
 
* Do not send subscription or unsubscription requests to the list address itself; use the respective -request address instead.
−
* Do not quote messages that were sent to you by other people in private mail, unless agreed beforehand.
 
−
* When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied.
 
−
* If you send messages to lists to which you are not subscribed, always note that fact in the body of your message.
 
−
* If you want to explain to someone how to use a mailing list, please do it privately.
 
  
 
== IRC ==
 
== IRC ==
 
When using the VideoLAN IRC channels, please follow these rules:
 
When using the VideoLAN IRC channels, please follow these rules:
−
* Speak in English.
+
* Do not quote messages that were sent to you by other people in private query, unless agreed beforehand.
−
* Never send your messages in colors; use plain text instead.
+
* If you want to explain to someone how to use IRC, do it privately.
−
* Do not send spam links.
+
* Never send messages with colours (i.e. colour codes); use plain text instead.
 
* Do not send "test" messages to determine whether your IRC client is working. We have a #test channel for that.
 
* Do not send "test" messages to determine whether your IRC client is working. We have a #test channel for that.
−
* If you want to explain to someone how to use IRC, do it privately.
 
−
* Do not quote messages that were sent to you by other people in private query, unless agreed beforehand.
 
  
 
== Forum ==
 
== Forum ==
−
* Do not send spam.
 
 
* Do not bump a topic several times per day.
 
* Do not bump a topic several times per day.
 
* Do not cross-post your question across sub-forums.
 
* Do not cross-post your question across sub-forums.
−
* Do not edit too often your past posts.
+
* Do not edit your past posts overly often.
−
 
 
−
== Trac ==
 
−
 
 
−
== Wiki ==
 
  
 +
== Bugtrackers ==
 +
* Do not change priority or importance lightly.
  
−
= Disciplinary action and resolution =
+
== Code repositories: Git / SVN / HG ==
 +
* Do NOT engage in revert wars.
 +
* Do NOT delete another developer's commit without approval by using push --force.
 +
* No insult in commits or commit messages.
 +
* Respect the correct [http://chris.beams.io/posts/git-commit/ commit log style].
  
−
== Disciplinary Actions for direct CoC violations ==
+
== Real life, Conferences, Meetings and Assemblies ==
 +
* Absolutely no violence will be tolerated,
 +
* "No" means "'''No'''",
 +
* You get one warning from the board first, and then you're out,
 +
* This also applies for the community day of [[VDD]].
  
−
The following disciplinary actions may or may not be enforced when a direct CoC violation is reported to Community Relations.
+
=  Disciplinary actions =
 +
Violations of the Code of Conduct will be punished.
  
−
Gentoo has a number of IRC channels. Each channel has a number of operators managing it and ensuring proper use of this media. Community Relations has faith that the current operators are capable to manage their channels so it will not interfere with them unless a conflict is escalated to Community Relations by the channel operators or a user. However, there are a few channels where all developers are operators such as ''#gentoo-dev''. In this case, Community Relations will actively enforce the CoC and impose the following list of possible penalties if necessary.
+
See the following guidelines for escalations steps and sanctions.
  
−
{{Important|Before applying any of the following disciplinary policies, the ComRel team will try to discuss the problem with the offender in order to solve it in a more peaceful way. However, it is possible for the ComRel team to apply the penalty without further discussions in severe CoC violations (direct attacks, insults, name-calling etc). }}
+
== Escalation ==
  
−
* 24 hour ban from the IRC channel.
+
# The first violation will always result in a simple warning, except if it is a grave or deliberate violation.
−
* Every third ban is followed by a 7 day ban.
+
# The following violations will result in some of the disciplinary actions listed in the paragraphs below.
−
* For repetitive violations, the case may be escalated to Community Relations for further disciplinary actions
+
# For repetitive violations, the case may be escalated to the VideoLAN board and general assembly for further disciplinary actions.
  
−
For CoC violations in bugzilla the following list of disciplinary actions may be followed.
+
In case of any disciplinary action, a VideoLAN board member will send an email to the offender and copy the association mailing list.
  
−
* 48 hour ban from bugzilla.
+
== Disciplinary Actions ==
−
* Every third violation, the developer will lose his/her cvs access for two days.
 
−
* For repetitive violations, the case may be escalated to Community Relations for further disciplinary actions.
 
  
−
For CoC violations in the mailing list, the following list of disciplinary actions may be followed.
+
The following disciplinary actions may be enforced when a direct Code of Conduct violation is reported.
  
−
* 7 days ban from the mailing list.
+
'''NB:''' Before applying any of those following disciplinary policies, the VideoLAN board will try to discuss the problem with the offender in order to solve it in a more peaceful way.<br />
−
* Every third violation is followed by a 30 days ban.
+
However, it is possible for the board to apply the penalty without discussions in severe Code of Conduct violations.
−
* For repetitive violations, the case may be escalated to Community Relations for further disciplinary actions.
 
  
−
{{Important|In order for the previous penalties to be applied, two or more Community Relations members have to agree with the proposed penalty. The majority of Commnity Relations members can render any decision void within 72 hours in order to prevents accumulative effects.}}
+
=== Mailing lists ===
 +
* The netiquette violations will get only a warning. Repeated netiquette violations will be escalated.
 +
* 24-hour ban from the mailing list in question.
 +
* Every third violation, the contributor will get a 7-day ban.
 +
* As one cannot develop without the mailing lists, a ban from a *-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.
  
−
In case a disciplinary action is applied, one of the ComRel members must e-mail the offender as soon as possible informing him of the situation and possible consequences for repetitive violations.
+
=== IRC ===
 +
* Direct kick for minor violations, enforced by channels ops.
 +
* Other violations will get a 24-hour ban from the IRC channel.
 +
* Every third violation, the offender will have a 7-day ban.
  
−
==== Disciplinary Actions for Escalated Conflicts ====
+
=== Forum ===
 +
* Direct ban and account deletion for spam.
 +
* 24-hour ban from the forum website.
 +
* Every third violation, the offender will have a 1-month ban.
  
−
For escalated conflicts, disciplinary action must be decided on a case-by-case basis by Community Relations. For the majority of situations requiring disciplinary action, a warning is enough to correct future behavior. If behavior does not improve, a probationary period with revoked access to Gentoo infrastructure of two weeks to one month is appropriate. If upon restoration of access negative behavior re-occurs, removal from the project will be necessary. In extreme cases, suspension or removal may be necessary upon a single offense. Except in critical situations where immediate action is required, such disciplinary action is determined by members of the Community Relations project. If the issue is deemed critical, the developer in question may have his or her access suspended while a vote takes place. In such situations, the Community Relations lead may act without a vote of the remaining Community Relations team; this power is granted by Council. In the event of such a case, process for the resolution of the conflict may be bypassed altogether, a decision may be made, and any disputes would then be raised to Council per the below appeal process. The critical nature of an escalation may be determined by the Community Relations Lead or Infrastructure, for security-related issues, that which would endanger Gentoo, or our reputation. An issue that is deemed critical does not need further justification in addition to stating which of the above situations it falls under.
+
=== Bugtracker ===
 +
* 24-hour ban from trac.
 +
* Removal of developer or admin rights.
 +
* Every third violation, the offender will be banned for 7 days.
 +
* Every third violation, a developer may lose commit access for 7 days.
  
−
Upon removing a developer, the gentoo-core mailing list should be notified. Additionally, the entire Community Relations team is informed via email of the issues that led to removing or suspending a developer, and this information is stored on the bug. Developers who are removed from the project may not reapply for developer status without the approval of the Community Relations lead(s).
+
=== Wiki ===
 +
* 24-hour ban from the wiki.
 +
* Removal of developer or admin rights.
 +
* Every third violation, the offender will be banned for 7 days.
  
 +
=== Code repositories ===
 +
* 24-hour ban from commit access.
 +
* Removal of gitosis admin rights.
 +
* Every third violation, the developer will lose commit access for 7 days.
  
−
[[Category:About_VideoLAN]]
+
[[Category:About VideoLAN]]
 +
[[Category:Events|*]]

Latest revision as of 05:20, 11 February 2019


You should check out our shared values.

Communications rules

The following rules apply to all means of communication, online and in real life.

  • Do not use foul language, and absolutely NO insults will be tolerated.
  • Be careful with direct criticism:
    • Focus on the possible improvements and do not make the issue a personal one.
    • You should, when possible, criticize in private, and praise publicly; since most of our communications are public and people can be sensitive about that.
  • Ad hominem attacks are not accepted.
  • Do not flame or troll; it is not funny.
  • Do not undo someone's else contribution (wiki edits, code reverts, etc...) without asking first.
  • Send all communication in English.
    • The videolan@ mailing list, wiki translated pages, and forum-specific topics allow different languages, when clearly flagged.
  • Do not send spam.
  • Do not abuse administrative powers.
  • These Code of Conduct rules are not exhaustive; please use common sense, to infer other rules.

Mailing lists

When using the VideoLAN mailing lists, please follow also these simple rules:

  • The mailing lists exist to foster the development and use of VideoLAN. Unconstructive and off-topic messages, along with other abuse, are not welcome.
  • Make sure that you are using the proper list. In particular, don't send user-related questions to developer mailing lists.
  • If you want to explain to someone how to use a mailing list, please do it privately.
  • Do not quote messages that were sent to you by other people in private mail, unless agreed beforehand.
  • When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly requested to be copied. When replying on a private mailing list, this does not apply as the recipient would not be able to read the reply otherwise.
  • If you send messages to lists to which you are not subscribed, always note that fact in the body of your message.

Mailing list Etiquette

  • Wrap your lines at 80 characters or less for ordinary discussion. Lines longer than 80 characters are acceptable for computer-generated output (e.g., ls -l).
  • Avoid top-posting in conversations.
  • Avoid HTML-only messages; have a plain text version instead.
  • Avoid sending large attachments; mails with attachments over 65kb will have to be moderated by administrators.
  • Do not send automated "out-of-office" or "vacation" messages.
  • Do not send "test" messages to determine whether your mail client is working. We have a test mailing list for that.
  • Do not send subscription or unsubscription requests to the list address itself; use the respective -request address instead.

IRC

When using the VideoLAN IRC channels, please follow these rules:

  • Do not quote messages that were sent to you by other people in private query, unless agreed beforehand.
  • If you want to explain to someone how to use IRC, do it privately.
  • Never send messages with colours (i.e. colour codes); use plain text instead.
  • Do not send "test" messages to determine whether your IRC client is working. We have a #test channel for that.

Forum

  • Do not bump a topic several times per day.
  • Do not cross-post your question across sub-forums.
  • Do not edit your past posts overly often.

Bugtrackers

  • Do not change priority or importance lightly.

Code repositories: Git / SVN / HG

  • Do NOT engage in revert wars.
  • Do NOT delete another developer's commit without approval by using push --force.
  • No insult in commits or commit messages.
  • Respect the correct commit log style.

Real life, Conferences, Meetings and Assemblies

  • Absolutely no violence will be tolerated,
  • "No" means "No",
  • You get one warning from the board first, and then you're out,
  • This also applies for the community day of VDD.

Disciplinary actions

Violations of the Code of Conduct will be punished.

See the following guidelines for escalations steps and sanctions.

Escalation

  1. The first violation will always result in a simple warning, except if it is a grave or deliberate violation.
  2. The following violations will result in some of the disciplinary actions listed in the paragraphs below.
  3. For repetitive violations, the case may be escalated to the VideoLAN board and general assembly for further disciplinary actions.

In case of any disciplinary action, a VideoLAN board member will send an email to the offender and copy the association mailing list.

Disciplinary Actions

The following disciplinary actions may be enforced when a direct Code of Conduct violation is reported.

NB: Before applying any of those following disciplinary policies, the VideoLAN board will try to discuss the problem with the offender in order to solve it in a more peaceful way.
However, it is possible for the board to apply the penalty without discussions in severe Code of Conduct violations.

Mailing lists

  • The netiquette violations will get only a warning. Repeated netiquette violations will be escalated.
  • 24-hour ban from the mailing list in question.
  • Every third violation, the contributor will get a 7-day ban.
  • As one cannot develop without the mailing lists, a ban from a *-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.

IRC

  • Direct kick for minor violations, enforced by channels ops.
  • Other violations will get a 24-hour ban from the IRC channel.
  • Every third violation, the offender will have a 7-day ban.

Forum

  • Direct ban and account deletion for spam.
  • 24-hour ban from the forum website.
  • Every third violation, the offender will have a 1-month ban.

Bugtracker

  • 24-hour ban from trac.
  • Removal of developer or admin rights.
  • Every third violation, the offender will be banned for 7 days.
  • Every third violation, a developer may lose commit access for 7 days.

Wiki

  • 24-hour ban from the wiki.
  • Removal of developer or admin rights.
  • Every third violation, the offender will be banned for 7 days.

Code repositories

  • 24-hour ban from commit access.
  • Removal of gitosis admin rights.
  • Every third violation, the developer will lose commit access for 7 days.
Retrieved from "https://wiki.videolan.org/index.php?title=Code_of_Conduct&oldid=57900"