Skip to content

Commit c6df79a

Browse files
stschiffstschiff
committed
added contributing guide and Code of Conduct
1 parent ff8b85e commit c6df79a

2 files changed

Lines changed: 186 additions & 0 deletions

File tree

‎CODE_OF_CONDUCT.md‎

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
# Code of Conduct - sequencetools
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to make participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behaviour that contributes to a positive environment for our
15+
community include:
16+
17+
* Demonstrating empathy and kindness toward other people
18+
* Being respectful of differing opinions, viewpoints, and experiences
19+
* Giving and gracefully accepting constructive feedback
20+
* Accepting responsibility and apologising to those affected by our mistakes,
21+
and learning from the experience
22+
* Focusing on what is best not just for us as individuals, but for the
23+
overall community
24+
25+
Examples of unacceptable behaviour include:
26+
27+
* The use of sexualised language or imagery, and sexual attention or advances
28+
* Trolling, insulting or derogatory comments, and personal or political attacks
29+
* Public or private harassment
30+
* Publishing others' private information, such as a physical or email
31+
address, without their explicit permission
32+
* Other conduct which could reasonably be considered inappropriate in a
33+
professional setting
34+
35+
## Our Responsibilities
36+
37+
Project maintainers are responsible for clarifying and enforcing our standards of
38+
acceptable behaviour and will take appropriate and fair corrective action in
39+
response to any instances of unacceptable behaviour.
40+
41+
Project maintainers have the right and responsibility to remove, edit, or reject
42+
comments, commits, code, wiki edits, issues, and other contributions that are
43+
not aligned to this Code of Conduct, or to ban
44+
temporarily or permanently any contributor for other behaviours that they deem
45+
inappropriate, threatening, offensive, or harmful.
46+
47+
## Scope
48+
49+
This Code of Conduct applies within all community spaces, and also applies when
50+
an individual is officially representing the community in public spaces.
51+
Examples of representing our community include using an official e-mail address,
52+
posting via an official social media account, or acting as an appointed
53+
representative at an online or offline event.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behaviour may be
58+
reported to the community leaders responsible for enforcement at <stephan_schiffels@eva.mpg.de>.
59+
All complaints will be reviewed and investigated promptly and fairly.
60+
61+
All community leaders are obligated to respect the privacy and security of the
62+
reporter of any incident.
63+
64+
## Attribution
65+
66+
This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org/), version
67+
[1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct/code_of_conduct.md) and
68+
[2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md),
69+
and was generated by [contributing.md](https://contributing.md/generator).

‎CONTRIBUTING.md‎

Lines changed: 117 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,117 @@
1+
<!-- omit in toc -->
2+
# Contributing to sequencetools
3+
4+
First off, thanks for taking the time to contribute! ❤️
5+
6+
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
7+
8+
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
9+
> - Star the project
10+
> - Tweet about it
11+
> - Refer this project in your project's readme
12+
> - Mention the project at local meetups and tell your friends/colleagues
13+
14+
<!-- omit in toc -->
15+
## Table of Contents
16+
17+
- [Code of Conduct](#code-of-conduct)
18+
- [I Have a Question](#i-have-a-question)
19+
- [I Want To Contribute](#i-want-to-contribute)
20+
- [Reporting Bugs](#reporting-bugs)
21+
- [Suggesting Enhancements](#suggesting-enhancements)
22+
- [Your First Code Contribution](#your-first-code-contribution)
23+
- [Improving The Documentation](#improving-the-documentation)
24+
- [Styleguides](#styleguides)
25+
- [Commit Messages](#commit-messages)
26+
- [Join The Project Team](#join-the-project-team)
27+
28+
29+
## Code of Conduct
30+
31+
This project and everyone participating in it is governed by the
32+
[sequencetools Code of Conduct](https://github.com/stschiff/sequenceTools/blob/master/CODE_OF_CONDUCT.md).
33+
By participating, you are expected to uphold this code. Please report unacceptable behavior
34+
to <stephan_schiffels@eva.mpg.de>.
35+
36+
37+
## I Have a Question
38+
39+
> If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/stschiff/sequenceTools/blob/master/README.md).
40+
41+
Before you ask a question, it is best to search for existing [Issues](https://github.com/stschiff/sequenceTools/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
42+
43+
If you then still feel the need to ask a question and need clarification, we recommend the following:
44+
45+
- Open an [Issue](https://github.com/stschiff/sequenceTools/issues/new).
46+
- Provide as much context as you can about what you're running into.
47+
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
48+
49+
We will then take care of the issue as soon as possible.
50+
51+
## I Want To Contribute
52+
53+
> ### Legal Notice <!-- omit in toc -->
54+
> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project licence.
55+
56+
### Reporting Bugs
57+
58+
<!-- omit in toc -->
59+
#### Before Submitting a Bug Report
60+
61+
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
62+
63+
- Make sure that you are using the latest version.
64+
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/stschiff/sequenceTools/blob/master/README.md). If you are looking for support, you might want to check [this section](#i-have-a-question)).
65+
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/stschiff/sequenceTools/issues?q=label%3Abug).
66+
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
67+
- Collect information about the bug:
68+
- Stack trace (Traceback)
69+
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
70+
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
71+
- Possibly your input and the output
72+
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
73+
74+
<!-- omit in toc -->
75+
#### How Do I Submit a Good Bug Report?
76+
77+
> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <stephan_schiffels@eva.mpg.de>.
78+
79+
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
80+
81+
- Open an [Issue](https://github.com/stschiff/sequenceTools/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
82+
- Explain the behavior you would expect and the actual behavior.
83+
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
84+
- Provide the information you collected in the previous section.
85+
86+
Once it's filed:
87+
88+
- The project team will label the issue accordingly.
89+
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
90+
- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
91+
92+
### Suggesting Enhancements
93+
94+
This section guides you through submitting an enhancement suggestion for sequencetools, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
95+
96+
<!-- omit in toc -->
97+
#### Before Submitting an Enhancement
98+
99+
- Make sure that you are using the latest version.
100+
- Read the [documentation](https://github.com/stschiff/sequenceTools/blob/master/README.md) carefully and find out if the functionality is already covered, maybe by an individual configuration.
101+
- Perform a [search](https://github.com/stschiff/sequenceTools/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
102+
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
103+
104+
<!-- omit in toc -->
105+
#### How Do I Submit a Good Enhancement Suggestion?
106+
107+
Enhancement suggestions are tracked as [GitHub issues](https://github.com/stschiff/sequenceTools/issues).
108+
109+
- Use a **clear and descriptive title** for the issue to identify the suggestion.
110+
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
111+
- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
112+
- You may want to **include screenshots or screen recordings** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [LICEcap](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and the built-in [screen recorder in GNOME](https://help.gnome.org/users/gnome-help/stable/screen-shot-record.html.en) or [SimpleScreenRecorder](https://github.com/MaartenBaert/ssr) on Linux. <!-- this should only be included if the project has a GUI -->
113+
- **Explain why this enhancement would be useful** to most sequencetools users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
114+
115+
<!-- omit in toc -->
116+
## Attribution
117+
This guide is based on the [contributing.md](https://contributing.md/generator)!

0 commit comments

Comments
 (0)