Repository: logging-log4net
Updated Branches:
  refs/heads/develop fe147ac77 -> 0d9a219d6


(doc) Contributing: added a code of conduct section


Project: http://git-wip-us.apache.org/repos/asf/logging-log4net/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4net/commit/0d9a219d
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4net/tree/0d9a219d
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4net/diff/0d9a219d

Branch: refs/heads/develop
Commit: 0d9a219d6744efca6e056ee1a7e13b5629f9e5f9
Parents: fe147ac
Author: Dominik Psenner <dpsen...@apache.org>
Authored: Thu Jul 20 14:02:36 2017 +0200
Committer: Dominik Psenner <dpsen...@apache.org>
Committed: Thu Jul 20 14:02:36 2017 +0200

----------------------------------------------------------------------
 CONTRIBUTING.md | 40 +++++++++++++++++++++++++++++++++++++++-
 1 file changed, 39 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/logging-log4net/blob/0d9a219d/CONTRIBUTING.md
----------------------------------------------------------------------
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index faa6e49..bd6931e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,7 +1,45 @@
-# Contributing to Apache log4net
+# Contributing
 
 You have found a bug or you have an idea for a cool new feature? Contributing 
code is a great way to give something back to the open source community. Before 
you dig right into the code there are a few guidelines that we need 
contributors to follow so that we can have a chance of keeping on top of things.
 
+## 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 each other
+
+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 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.
+
+### Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 1.4, 
available [here](http://contributor-covenant.org/version/1/4).
+
 # Getting started
 
 * Make sure you have a [JIRA account](https://issues.apache.org/jira/).

Reply via email to