public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
* [PATCH] Update code of conduct
@ 2024-05-28 19:33 Aaron Merey
  2024-06-07 18:10 ` Aaron Merey
  0 siblings, 1 reply; 2+ messages in thread
From: Aaron Merey @ 2024-05-28 19:33 UTC (permalink / raw)
  To: elfutils-devel; +Cc: Aaron Merey

Adopt a new code of conduct based on the Contributor's Covenant.

See the new CONDUCT file for more information.

Signed-off-by: Aaron Merey <amerey@redhat.com>
---
 CONDUCT                 | 134 ++++++++++++++++++++++++++++++++++++++++
 CONTRIBUTING            |   3 +-
 Makefile.am             |   2 +-
 NEWS                    |   3 +
 config/elfutils.spec.in |   2 +-
 5 files changed, 141 insertions(+), 3 deletions(-)
 create mode 100644 CONDUCT

diff --git a/CONDUCT b/CONDUCT
new file mode 100644
index 00000000..2d0b8589
--- /dev/null
+++ b/CONDUCT
@@ -0,0 +1,134 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in
+our community a harassment-free experience for everyone, regardless of
+age, body size, visible or invisible disability, ethnicity, sex
+characteristics, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance,
+race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political
+  attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders (i.e. regular contributors and/or those with elfutils
+git commit access) are responsible for clarifying and enforcing our standards
+of acceptable behavior and will take appropriate and fair corrective action
+in response to any behavior that they deem inappropriate, threatening,
+offensive, or harmful.
+
+Community leaders 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, and will communicate reasons
+for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, such as the
+elfutils IRC channel, website, mailing list and bug reports. It also
+applies when an individual is officially representing the community
+in public spaces. Examples of representing our community include acting
+as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may
+be reported to the elfutils code of conduct committee at
+elfutils-conduct@sourceware.org.
+
+The current members of the elfutils code of conduct committee are:
+Mark Wielaard
+Aaron Merey
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security
+of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in
+determining the consequences for any action they deem in violation of
+this Code of Conduct:
+
+### 1. Correction
+
+Community Impact: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+Consequence: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+Community Impact: A violation through a single incident or series of
+actions.
+
+Consequence: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, for a specified period of time.
+This includes avoiding interactions in community spaces as well as external
+channels like social media. Violating these terms may lead to a temporary
+or permanent ban.
+
+### 3. Temporary Ban
+
+Community Impact: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+Consequence: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public
+or private interaction with the people involved, including unsolicited
+interaction with those enforcing the Code of Conduct, is allowed during
+this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+Community Impact: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+Consequence: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version
+2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by Mozilla’s code of conduct
+enforcement ladder.
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.
diff --git a/CONTRIBUTING b/CONTRIBUTING
index 5614728e..27907652 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -139,4 +139,5 @@ https://builder.sourceware.org/buildbot/#/builders?tags=elfutils-try
 committers/maintainers who repeatedly ignore the above guidelines,
 are hostile or offensive towards other committers or contributors,
 and don't correct their behavior after being asked by other committers
-will be removed as maintainer/committer.
+will be removed as maintainer/committer.  See the CONDUCT file for more
+information regarding the elfutils code of conduct.
diff --git a/Makefile.am b/Makefile.am
index 69af63ac..92130b57 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -30,7 +30,7 @@ SUBDIRS = config lib libelf libcpu backends libebl libdwelf libdwfl libdw \
 	  libasm debuginfod src po doc tests
 
 EXTRA_DIST = elfutils.spec GPG-KEY NOTES CONTRIBUTING SECURITY \
-	     COPYING COPYING-GPLV2 COPYING-LGPLV3
+	     COPYING COPYING-GPLV2 COPYING-LGPLV3 CONDUCT
 
 # Make sure the test install uses lib64 when $LIB will yield lib64.
 # Make sure the test build uses the same compiler, which on e.g. ppc64
diff --git a/NEWS b/NEWS
index 6f931bb5..f70e78a5 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,8 @@
 Version 0.192 (one after 0.191)
 
+CONDUCT: A new code of conduct has been adopted.  See the
+	 CONDUCT file for more information.
+
 debuginfod: Add per-file signature verification for integrity
             checking, using RPM IMA scheme from Fedora/RHEL.
 
diff --git a/config/elfutils.spec.in b/config/elfutils.spec.in
index 46072997..942bcacb 100644
--- a/config/elfutils.spec.in
+++ b/config/elfutils.spec.in
@@ -239,7 +239,7 @@ fi
 
 %files
 %license COPYING COPYING-GPLV2 COPYING-LGPLV3 doc/COPYING-GFDL
-%doc README TODO CONTRIBUTING SECURITY
+%doc README TODO CONTRIBUTING SECURITY CONDUCT
 %{_bindir}/eu-addr2line
 %{_bindir}/eu-ar
 %{_bindir}/eu-elfclassify
-- 
2.43.0


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] Update code of conduct
  2024-05-28 19:33 [PATCH] Update code of conduct Aaron Merey
@ 2024-06-07 18:10 ` Aaron Merey
  0 siblings, 0 replies; 2+ messages in thread
From: Aaron Merey @ 2024-06-07 18:10 UTC (permalink / raw)
  To: elfutils-devel

Pushed as commit e2a3e51ab54c4698fe09

Aaron

On Tue, May 28, 2024 at 3:34 PM Aaron Merey <amerey@redhat.com> wrote:
>
> Adopt a new code of conduct based on the Contributor's Covenant.
>
> See the new CONDUCT file for more information.
>
> Signed-off-by: Aaron Merey <amerey@redhat.com>
> ---
>  CONDUCT                 | 134 ++++++++++++++++++++++++++++++++++++++++
>  CONTRIBUTING            |   3 +-
>  Makefile.am             |   2 +-
>  NEWS                    |   3 +
>  config/elfutils.spec.in |   2 +-
>  5 files changed, 141 insertions(+), 3 deletions(-)
>  create mode 100644 CONDUCT
>
> diff --git a/CONDUCT b/CONDUCT
> new file mode 100644
> index 00000000..2d0b8589
> --- /dev/null
> +++ b/CONDUCT
> @@ -0,0 +1,134 @@
> +# Contributor Covenant Code of Conduct
> +
> +## Our Pledge
> +
> +We as members, contributors, and leaders pledge to make participation in
> +our community a harassment-free experience for everyone, regardless of
> +age, body size, visible or invisible disability, ethnicity, sex
> +characteristics, gender identity and expression, level of experience,
> +education, socio-economic status, nationality, personal appearance,
> +race, caste, color, religion, or sexual identity and orientation.
> +
> +We pledge to act and interact in ways that contribute to an open, welcoming,
> +diverse, inclusive, and healthy community.
> +
> +## Our Standards
> +
> +Examples of behavior that contributes to a positive environment for our
> +community include:
> +
> +* Demonstrating empathy and kindness toward other people
> +* Being respectful of differing opinions, viewpoints, and experiences
> +* Giving and gracefully accepting constructive feedback
> +* Accepting responsibility and apologizing to those affected by our mistakes,
> +  and learning from the experience
> +* Focusing on what is best not just for us as individuals, but for the
> +  overall community
> +
> +Examples of unacceptable behavior include:
> +
> +* The use of sexualized language or imagery, and sexual attention or
> +  advances of any kind
> +* Trolling, insulting or derogatory comments, and personal or political
> +  attacks
> +* Public or private harassment
> +* Publishing others' private information, such as a physical or email
> +  address, without their explicit permission
> +* Other conduct which could reasonably be considered inappropriate in a
> +  professional setting
> +
> +## Enforcement Responsibilities
> +
> +Community leaders (i.e. regular contributors and/or those with elfutils
> +git commit access) are responsible for clarifying and enforcing our standards
> +of acceptable behavior and will take appropriate and fair corrective action
> +in response to any behavior that they deem inappropriate, threatening,
> +offensive, or harmful.
> +
> +Community leaders 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, and will communicate reasons
> +for moderation decisions when appropriate.
> +
> +## Scope
> +
> +This Code of Conduct applies within all community spaces, such as the
> +elfutils IRC channel, website, mailing list and bug reports. It also
> +applies when an individual is officially representing the community
> +in public spaces. Examples of representing our community include acting
> +as an appointed representative at an online or offline event.
> +
> +## Enforcement
> +
> +Instances of abusive, harassing, or otherwise unacceptable behavior may
> +be reported to the elfutils code of conduct committee at
> +elfutils-conduct@sourceware.org.
> +
> +The current members of the elfutils code of conduct committee are:
> +Mark Wielaard
> +Aaron Merey
> +
> +All complaints will be reviewed and investigated promptly and fairly.
> +
> +All community leaders are obligated to respect the privacy and security
> +of the reporter of any incident.
> +
> +## Enforcement Guidelines
> +
> +Community leaders will follow these Community Impact Guidelines in
> +determining the consequences for any action they deem in violation of
> +this Code of Conduct:
> +
> +### 1. Correction
> +
> +Community Impact: Use of inappropriate language or other behavior deemed
> +unprofessional or unwelcome in the community.
> +
> +Consequence: A private, written warning from community leaders, providing
> +clarity around the nature of the violation and an explanation of why the
> +behavior was inappropriate. A public apology may be requested.
> +
> +### 2. Warning
> +
> +Community Impact: A violation through a single incident or series of
> +actions.
> +
> +Consequence: A warning with consequences for continued behavior. No
> +interaction with the people involved, including unsolicited interaction
> +with those enforcing the Code of Conduct, for a specified period of time.
> +This includes avoiding interactions in community spaces as well as external
> +channels like social media. Violating these terms may lead to a temporary
> +or permanent ban.
> +
> +### 3. Temporary Ban
> +
> +Community Impact: A serious violation of community standards, including
> +sustained inappropriate behavior.
> +
> +Consequence: A temporary ban from any sort of interaction or public
> +communication with the community for a specified period of time. No public
> +or private interaction with the people involved, including unsolicited
> +interaction with those enforcing the Code of Conduct, is allowed during
> +this period. Violating these terms may lead to a permanent ban.
> +
> +### 4. Permanent Ban
> +
> +Community Impact: Demonstrating a pattern of violation of community
> +standards, including sustained inappropriate behavior, harassment of an
> +individual, or aggression toward or disparagement of classes of individuals.
> +
> +Consequence: A permanent ban from any sort of public interaction within the
> +community.
> +
> +## Attribution
> +
> +This Code of Conduct is adapted from the Contributor Covenant, version
> +2.1, available at
> +https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
> +
> +Community Impact Guidelines were inspired by Mozilla’s code of conduct
> +enforcement ladder.
> +
> +For answers to common questions about this code of conduct, see the FAQ at
> +https://www.contributor-covenant.org/faq. Translations are available at
> +https://www.contributor-covenant.org/translations.
> diff --git a/CONTRIBUTING b/CONTRIBUTING
> index 5614728e..27907652 100644
> --- a/CONTRIBUTING
> +++ b/CONTRIBUTING
> @@ -139,4 +139,5 @@ https://builder.sourceware.org/buildbot/#/builders?tags=elfutils-try
>  committers/maintainers who repeatedly ignore the above guidelines,
>  are hostile or offensive towards other committers or contributors,
>  and don't correct their behavior after being asked by other committers
> -will be removed as maintainer/committer.
> +will be removed as maintainer/committer.  See the CONDUCT file for more
> +information regarding the elfutils code of conduct.
> diff --git a/Makefile.am b/Makefile.am
> index 69af63ac..92130b57 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -30,7 +30,7 @@ SUBDIRS = config lib libelf libcpu backends libebl libdwelf libdwfl libdw \
>           libasm debuginfod src po doc tests
>
>  EXTRA_DIST = elfutils.spec GPG-KEY NOTES CONTRIBUTING SECURITY \
> -            COPYING COPYING-GPLV2 COPYING-LGPLV3
> +            COPYING COPYING-GPLV2 COPYING-LGPLV3 CONDUCT
>
>  # Make sure the test install uses lib64 when $LIB will yield lib64.
>  # Make sure the test build uses the same compiler, which on e.g. ppc64
> diff --git a/NEWS b/NEWS
> index 6f931bb5..f70e78a5 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -1,5 +1,8 @@
>  Version 0.192 (one after 0.191)
>
> +CONDUCT: A new code of conduct has been adopted.  See the
> +        CONDUCT file for more information.
> +
>  debuginfod: Add per-file signature verification for integrity
>              checking, using RPM IMA scheme from Fedora/RHEL.
>
> diff --git a/config/elfutils.spec.in b/config/elfutils.spec.in
> index 46072997..942bcacb 100644
> --- a/config/elfutils.spec.in
> +++ b/config/elfutils.spec.in
> @@ -239,7 +239,7 @@ fi
>
>  %files
>  %license COPYING COPYING-GPLV2 COPYING-LGPLV3 doc/COPYING-GFDL
> -%doc README TODO CONTRIBUTING SECURITY
> +%doc README TODO CONTRIBUTING SECURITY CONDUCT
>  %{_bindir}/eu-addr2line
>  %{_bindir}/eu-ar
>  %{_bindir}/eu-elfclassify
> --
> 2.43.0
>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-06-07 20:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-28 19:33 [PATCH] Update code of conduct Aaron Merey
2024-06-07 18:10 ` Aaron Merey

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).