mirror of
https://codeberg.org/shufflecake/shufflecake-c.git
synced 2026-01-07 11:35:33 -05:00
docs: Minor edits in CONTRIBUTING.md
This commit is contained in:
parent
f9ffa2d0c7
commit
327ff6b672
1 changed files with 5 additions and 5 deletions
|
|
@ -34,18 +34,18 @@ Always keep in mind that this project embraces the principles of privacy, libre
|
|||
|
||||
Before submitting a contribution, please make sure to check:
|
||||
|
||||
- Is it an issue? Check if it is a known problem before, i.e., if a similar open issues already exists.
|
||||
- Is it a feature request? Consider whether it aligns with the goal of the project, or if an open issues about it already exists.
|
||||
- Is it an issue? Check if it is a known problem before, i.e., if a similar open issue already exists.
|
||||
- Is it a feature request? Consider whether it aligns with the goal of the project, or if an open issue about it already exists.
|
||||
- Is it a code contribution? Please read below for submission guidelines.
|
||||
- Did you find a security bug? Please follow the instructions in the SECURITY.md file in this directory.
|
||||
|
||||
In case of doubt, you are always welcome to reach out to our support channels (Jabber, Mastodon, etc) or by email.
|
||||
In case of doubt, you are always welcome to reach out to our support channels (XMPP, Mastodon, etc) or by email.
|
||||
|
||||
|
||||
|
||||
## Opening issues <a id="user-content-issues"></a>
|
||||
|
||||
We are pretty relaxed in the git issues requirements, but please make sure to include all the necessary information. We will assign appropriate labels or edit the issue when necessary.
|
||||
We are pretty relaxed in the git issues format requirements, but please make sure to include all the necessary information. We will assign appropriate labels if you forget to do it, or edit the issue when necessary.
|
||||
|
||||
|
||||
|
||||
|
|
@ -168,7 +168,7 @@ In practice:
|
|||
1. Make sure you have a SSH/PGP/AGE key to sign off your contributions.
|
||||
1. The key must be minimum 2048 bit RSA or equivalent/above security level.
|
||||
2. It must be publicly available (i.e., upload it on a public keyserver/keyoxide etc).
|
||||
3. It must be publicly traceable to your full legal name, i.e. you have published it on your personal website/blog, or it contains an identity with your full legal name, or it is signed by another key which does.
|
||||
3. It must be publicly traceable to your full legal name, i.e. you have published it on your personal website/blog, or it contains an identity with your full legal name.
|
||||
2. Configure the key to be used on our git platform (e.g., Codeberg).
|
||||
1. Import the public part of the key in your profile (e.g.: Settings -> SSH/OpenPGP Keys).
|
||||
2. Use the key to sign your commits.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue