Commit 96d834c9 authored by Lukas Riedel's avatar Lukas Riedel

Merge branch '58-add-contributing-guide' into 'master'

Resolve "Add contributing guide"

Closes #58

See merge request !39
parents a945fec1 4556a79a
# 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,
education, socio-economic status, 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.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at
[dorieteam@iup.uni-heidelberg.de](mailto:dorieteam@iup.uni-heidelberg.de). 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][homepage], version 1.4,
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[homepage]: https://www.contributor-covenant.org
# Contribution Guide
We encourage everyone to contribute to the development and improvement of DORIE.
Please notice our included [Code of Conduct](CODE_OF_CONDUCT.md).
### Restricted Access to Repository
Free access to the [GitLab instance](https://ts-gitlab.iup.uni-heidelberg.de) of
the [TS-CCEES group](http://ts.iup.uni-heidelberg.de/) at the
[Institute of Environmental Physics](http://www.iup.uni-heidelberg.de/) is
restricted to members of said group.
Non-members are left with read-only access to public repositories.
### How to Contribute
If you would like to _actively contribute_ to DORiE, and you are affiliated
with [Heidelberg University](http://www.uni-heidelberg.de/) or an associated
research institute, you can become a member of the DORiE development team.
Otherwise, we encourage you to contribute bug reports, feature requests, or
improvement suggestions by contacting the development team
[via mail](mailto:dorieteam@iup.uni-heidelberg.de).
Notice, however, that resources for development and support are streched thin:
_Your mileage may vary._
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment