www/ CodeOfConduct

Contributor Covenant Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community
  • Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

  • The use of sexualized language or imagery and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others' private information, such as a physical or electronic address, without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Guidelines for Project Maintainer moderation

Remember these aren't rules, there's simply suggestions project maintainers are free to use when moderating projects on Freedesktop - especially when using Gitlab.

Dealing with Spam

If possible or unless told otherwise, don't report spam through Gitlab's reporting system. Because of how much spam we get, we've setup a spam bot that project maintainers can use instead to prevent the pipes from getting clogged up - and get a much faster response. When you see spam:

  • If it's an issue or a merge requeest, add the "spam" label to a on Gitlab. This will hide the comment immediately
  • If it's a comment, respond with the do not litter emoji 🚯 and the bot will do its civic duty

Note that the bot isn't setup by default, but can be setup for any project on freedesktop's gitlab. See https://gitlab.freedesktop.org/freedesktop/damspam for information on how to do this

Documenting incidences

Document things first and foremost, such as with screenshots

The biggest reason for this: Gitlab does not keep an edit history for comments, nor does it keep track of deleted comments. Once something has been removed or edited it's gone. Taking record of incidents can help the CoC team act on them when/if you reach out to them - as it makes it much easier to spot repeated patterns of behavior.

Inappropriate comments

If you come across a comment that feels inappropriate or hinders a healthy discussion, consider one of the following actions:

  • Editing the comment with a canned response such as:
    • "This comment has been removed as discussion about Foo support is off-topic, and should be discussed in its own issue"
    • "This comment has been hidden due to inflammatory language, please assume good faith when participating in discussions."
  • You can also delete the comment
  • You can also add a spoiler tag when editing the comment, to keep the body of the comment intact - but collapse it by default.

Limit engagement with problematic comments to moderating them

Trying to argue with someone or accuse them of wrongdoing will many times make a situation worse, and can also complicate things from the perspective of the CoC team. When problematic behavior occurs, it's recommended to keep responses brief and to the point - and to reach out to the code of conduct team if moderating the discussion fails.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at conduct@lists.freedesktop.org or to any of the members of that list:

All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4