From: Tonton <tonton@riseup.net>
To: 31480@debbugs.gnu.org
Cc: Tonton <tonton@riseup.net>
Subject: [bug#31480] [PATCH 1/2] documentation: Add Code of Conduct section.
Date: Thu, 17 May 2018 01:26:09 +0200 [thread overview]
Message-ID: <20180516232610.9703-1-tonton@riseup.net> (raw)
* doc/contributing.texi: Add Code of Conduct section.
---
doc/contributing.texi | 110 +++++++++++++++++++++++++++++++++++++++++-
1 file changed, 109 insertions(+), 1 deletion(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 2792fe2b2..8ea9c85e0 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -13,13 +13,15 @@ We want to provide a warm, friendly, and harassment-free environment, so
that anyone can contribute to the best of their abilities. To this end
our project uses a ``Contributor Covenant'', which was adapted from
@url{http://contributor-covenant.org/}. You can find a local version in
-the @file{CODE-OF-CONDUCT} file in the source tree.
+the @file{CODE-OF-CONDUCT} file in the source tree or in the following
+(@pxref{Code of Conduct}).
Contributors are not required to use their legal name in patches and
on-line communication; they can use any name or pseudonym of their
choice.
@menu
+* Code of Conduct:: Our pledge to foster a friendly environment.
* Building from Git:: The latest and greatest.
* Running Guix Before It Is Installed:: Hacker tricks.
* The Perfect Setup:: The right tools.
@@ -27,6 +29,112 @@ choice.
* Submitting Patches:: Share your work.
@end menu
+@node Code of Conduct
+@section Code of Conduct
+@anchor{#Code-of-Conduct}
+
+@quotation Note
+Here, "project" refers to GNU Guix, and "project maintainer(s)"
+refers to maintainer(s) of GNU Guix.
+@end quotation
+
+@subsection Our Pledge
+@anchor{#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, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+@subsection Our Standards
+@anchor{#Our-Standards}
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+@itemize
+@item
+Using welcoming and inclusive language
+@item
+Being respectful of differing viewpoints and experiences
+@item
+Gracefully accepting constructive criticism
+@item
+Focusing on what is best for the community
+@item
+Showing empathy towards other community members
+@end itemize
+
+Examples of unacceptable behavior by participants include:
+
+@itemize
+@item
+The use of sexualized language or imagery and unwelcome sexual attention
+or advances
+@item
+Trolling, insulting/derogatory comments, and personal or political
+attacks
+@item
+Public or private harassment
+@item
+Publishing others' private information, such as a physical or electronic
+address, without explicit permission
+@item
+Other conduct which could reasonably be considered inappropriate in a
+professional setting
+@end itemize
+
+@subsection Our Responsibilities
+@anchor{#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.
+
+@subsection Scope
+@anchor{#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.
+
+@subsection Enforcement
+@anchor{#Enforcement}
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may
+be reported by contacting the project team at
+@email{guix-maintainers@@gnu.org}. 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.
+
+@subsection Attribution
+@anchor{#Attribution}
+This Code of Conduct is adapted from the
+@uref{https://www.contributor-covenant.org,Contributor Covenant},
+version 1.4, available at
+@uref{https://www.contributor-covenant.org/version/1/4/code-of-conduct.html}
+
+
@node Building from Git
@section Building from Git
--
2.17.0
next reply other threads:[~2018-05-16 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 23:26 Tonton [this message]
2018-05-16 23:26 ` [bug#31481] [PATCH 2/2] documentation: Update CODE-OF-CONDUCT Tonton
2018-05-29 16:33 ` bug#31481: " Ludovic Courtès
2018-05-16 23:42 ` [bug#31480] Related bugs Tonton
2018-06-21 19:26 ` bug#31480: documentation: Add code of conduct section Gábor Boskovits
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180516232610.9703-1-tonton@riseup.net \
--to=tonton@riseup.net \
--cc=31480@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.