mirror/nlnetlabs-routinator
1
0
Fork 0
mirror of https://github.com/NLnetLabs/routinator.git synced 2024-05-19 06:50:04 +00:00
Code Issues Releases Activity

Style tweaks

Browse Source
This commit is contained in:
Alex Band
2021-10-14 12:17:10 +02:00
parent 337a31b3a2
commit da1adac79e
1 changed files with 12 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
CONTRIBUTING.md
View File

@ -1,8 +1,16 @@
# Contributing to Routinator
This document is offers guidelines on how to best contribute to the Routinator,
First off, thanks for taking the time to contribute! 🚀
This document is offers guidelines on how to best contribute to Routinator,
whether it being new features or correcting flaws or bugs.
## Code of Conduct
This project and everyone participating in it is governed by the [NLnet Labs
Code of Conduct](https://www.nlnetlabs.nl/conduct/). By participating, you are
expected to uphold this code.
## Learning RPKI
Routinator is Relying Party software for the Resource Public Key Infrastructure
@ -26,12 +34,6 @@ the relevant RFCs, and how they are related.
## Learning Routinator
## Code of Conduct
This project and everyone participating in it is governed by the [NLnet Labs
Code of Conduct](https://www.nlnetlabs.nl/conduct/). By participating, you are
expected to uphold this code.
### Join the Community
We invite you to join the [RPKI mailing
@ -41,15 +43,10 @@ question. Instead, follow the discussion on the mailing list and Discord and ask
questions there before you start sending patches. We prefer public discussions
over private ones, so everyone in the community can participate and learn.
If you're interested in the code side of things, consider clicking 'Watch' on
the [Routinator repo on GitHub](https://github.com/NLnetLabs/routinator) to be
notified of pull requests and new issues posted there.
### License and copyright
When contributing with code, you agree to put your changes and new code under
the same license Routinator and its associated libraries is already using.
When changing existing source code, do not alter the copyright of the original
file(s). The copyright will still be owned by the original creator(s) or those
who have been assigned copyright by the original author(s).
@ -57,11 +54,11 @@ who have been assigned copyright by the original author(s).
By submitting a patch to the Routinator project, you are assumed to have the
right to the code and to be allowed by your employer or whatever to hand over
that patch/code to us. We will credit you for your changes as far as possible,
to give credit but also to keep a trace back to who made what changes.
to give credit but also to keep a trace back to who made what changes.
### What To Read
The source code, documentation, man pages, [change
The source code, documentation, man page, [change
log](https://github.com/NLnetLabs/routinator/blob/main/Changelog.md) and the
[most recent changes](https://github.com/NLnetLabs/routinator/commits/main) in
git.
@ -92,6 +89,4 @@ but still share it with the maintainers to get some early feedback.
Once final, your change will be reviewed and discussed on GitHub. You will be
expected to correct flaws pointed out and update accordingly. As a submitter of
a change, you are the owner of that change until it has been merged. Please
respond on GitHub about the change, answer questions and/or fix nits/flaws.
a change, you are the owner of that change until it has been merged.