shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-23 21:35:11 +03:00
Code
5bab5e4ac3
systemd/docs/CODE_OF_CONDUCT.md

26 lines
1.6 KiB
Markdown
Raw Normal View History

docs: add a "front matter" snippet to our markdown pages It turns out Jekyll (the engine behind GitHub Pages) requires that pages include a "Front Matter" snippet of YAML at the top for proper rendering. Omitting it will still render the pages, but including it opens up new possibilities, such as using a {% for %} loop to generate index.md instead of requiring a separate script. I'm hoping this will also fix the issue with some of the pages (notably CODE_OF_CONDUCT.html) not being available under systemd.io Tested locally by rendering the website with Jekyll. Before this change, the *.md files were kept unchanged (so not sure how that even works?!), after this commit, proper *.html files were generated from it.
2019-01-03 01:16:34 +03:00
---
docs: drop "The" in categorization titles of Markdown documentation I think it makes sense to keep the "The" in place for the actual page's title, but let's drop it from the categorization header, to make it easier to find stuff, as the "The" isn't helpful to that. In particular as we sometimes do it this and sometimes the other way so far, hence let's stick to one common rule.
2020-01-14 12:11:19 +03:00
title: systemd Community Conduct Guidelines
docs: place all our markdown docs in rough categories
2019-12-11 12:49:28 +03:00
category: Contributing
docs: make it pretty Add custom Jekyll theme, logo, webfont and .gitignore FIXME: the markdown files have some H1 headers which need to be replaced with H2
2019-12-11 19:01:46 +03:00
layout: default
docs: add spdx tags to all .md files I have no idea if this is going to cause rendering problems, and it is fairly hard to check. So let's just merge this, and if it github markdown processor doesn't like it, revert.
2021-09-14 17:05:21 +03:00
SPDX-License-Identifier: LGPL-2.1-or-later
docs: add a "front matter" snippet to our markdown pages It turns out Jekyll (the engine behind GitHub Pages) requires that pages include a "Front Matter" snippet of YAML at the top for proper rendering. Omitting it will still render the pages, but including it opens up new possibilities, such as using a {% for %} loop to generate index.md instead of requiring a separate script. I'm hoping this will also fix the issue with some of the pages (notably CODE_OF_CONDUCT.html) not being available under systemd.io Tested locally by rendering the website with Jekyll. Before this change, the *.md files were kept unchanged (so not sure how that even works?!), after this commit, proper *.html files were generated from it.
2019-01-03 01:16:34 +03:00
---
coc: spell systemd in the one-and-only correct way
2018-10-02 10:34:01 +03:00
# The systemd Community Conduct Guidelines
Add a simple code of conduct based on ruby community guidelines This was discussed at the systemd hackfest during ASG2018, and we agreed to use the Ruby text [1] with the enforcement clause based on the "contributor covenant". I obviously modified the text where applicable to refer to systemd. [1] https://www.ruby-lang.org/en/conduct/ Fixes 10148.
2018-09-30 20:18:07 +03:00
docs/CODE_OF_CONDUCT: format text
2024-02-26 15:51:12 +03:00
This document provides community guidelines for a safe, respectful, productive, and collaborative place for any person who is willing to contribute to systemd.
It applies to all “collaborative spaces”, which is defined as community communications channels (such as mailing lists, submitted patches, commit comments, etc.).
Add a simple code of conduct based on ruby community guidelines This was discussed at the systemd hackfest during ASG2018, and we agreed to use the Ruby text [1] with the enforcement clause based on the "contributor covenant". I obviously modified the text where applicable to refer to systemd. [1] https://www.ruby-lang.org/en/conduct/ Fixes 10148.
2018-09-30 20:18:07 +03:00
- Participants will be tolerant of opposing views.
- Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
- When interpreting the words and actions of others, participants should always assume good intentions.
- Behaviour which can be reasonably considered harassment will not be tolerated.
## Enforcement
docs/CODE_OF_CONDUCT: format text
2024-02-26 15:51:12 +03:00
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at systemd-conduct@googlegroups.com.
This team currently consists of David Strauss <<systemd-conduct@davidstrauss.net>>, Ekaterina Gerasimova (Kat) <<Kittykat3756@gmail.com>>, and Zbigniew Jędrzejewski-Szmek <<zbyszek@in.waw.pl>>.
In the unfortunate event that you wish to make a complaint against one of the members, you may instead contact any of the other members individually.
Add a simple code of conduct based on ruby community guidelines This was discussed at the systemd hackfest during ASG2018, and we agreed to use the Ruby text [1] with the enforcement clause based on the "contributor covenant". I obviously modified the text where applicable to refer to systemd. [1] https://www.ruby-lang.org/en/conduct/ Fixes 10148.
2018-09-30 20:18:07 +03:00
docs/CODE_OF_CONDUCT: format text
2024-02-26 15:51:12 +03:00
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.
Copy Permalink