View source for Code of Conduct

<big><big>THIS IS AN UNDERGOING text</big></big>

= Communications rules =
Valid for all means of communications:
* Do not use foul language, and absolutely NO insults will be tolerated.
* Do not flame or troll; it is not funny anymore. And, you won't ever reach sam's troll level.
* Be careful with direct criticism:
** Focus on the possible improvements and do not make the issue a personal one.
** Provide criticism in a personal manner when it makes sense, since most of our communications are public and people can be sensitive about that.
* Send all of communication in English.
** Wiki translated pages and Forum specifics topics allow different languages, when clearly flagged.
* Do not send spam.
* Do not abuse administrative powers.
* Use common sense at all 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.
* 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).
* Do not top-post, unless it makes sense.
* Never send your messages in HTML-only; use plain text instead.
* Avoid sending large attachments. Attachments over 65k are usually moderated.
* 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.
* 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 ==
When using the VideoLAN IRC channels, please follow these rules:
* Never send your messages in colors; use plain text instead.
* 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 ==
* 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.

== Trac ==
* Do not change priority or importance lightly.

== Wiki ==
* Do not revert other people contribution without discussing it with them.

== Code repositories: Git / SVN / HG ==
* Do NOT engage in revert wars
* Do NOT delete someone else's commit without his/her approval by using push --force
* No insult in commits or commit messages
* Respect the correct commit log style

=  Disciplinary actions =

Violations of the code of conducts will be punished.

== Escalation ==

# The first violation will always get you just a simple warning, except if it is a grave or deliberate violation.
# The following violations will get the offender some of the disciplinary actions listed in the paragraphs below.
# 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 team member will send an email to the offender and copy the association mailing list.

== Disciplinary Actions ==

The following disciplinary actions may or may not be enforced when a direct CoC violation is reported.

'''NB:''' Before applying any of those following disciplinary policies, the VideoLAN 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 team to apply the penalty without discussions in severe CoC violations.

=== Mailing lists ===
* 24 hours ban from the offended mailing list.
* Every third violation, the developer will get a 7 days ban.
* As one cannot develop without the mailing-lists, ban from *-devel mailing list will get 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 one 24 hours ban from the IRC channel.
* Every third violation, the offender will have a 7 days ban.

=== Forum ===
* Direct ban and account deletion for spam.
* 24 hours ban from the forum website.
* Every third violation, the offender will have a 1 month ban.

=== Trac ===
* 24 hours 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 can lose the commit access for 7 days.

=== Wiki ===
* 24 hours ban from the wiki.
* Removal of developer or admin rights.
* Every third violation, the offender will be banned for 7 days.

=== Code repositories ===
* 24 hours ban from commit access.
* Removal of gitosis admin rights.
* Every third violation, the developer will lose the commit access for 7 days.

[[Category:About_VideoLAN]]