Not used anymore after b3fa79b

No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.

No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.

No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.

Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.

… files

Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.

Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.

No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.

Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.

No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.

Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.

No content was changed, new titles are wrapped with () to signal that
they will need to be decided on in a future commit.

Section in the manual have been preserved with a simple redirect to
GitHub, the proper anchors should be filled out in a future commit once
the new section names are decided.

This isn't relevant to contributors specifically, it applies to all
users

So that the CONTRIBUTING-new.md can take its place and Git detect the
rename

The -new version was assembled in the previous commits

…tion

It's not conventions about how to do coding, it's about what the code
should look like

Removing paragraphs from the other sections that aren't necessary anymore

Moving and collecting bits into the appropriate places, also writing
some new sentences

Can't be rendered in GitHub markdown, replacing it with a Git branch diagram using mermaid

Will be cleaned up in the next commit

How to force push to PR's is already explained in the
"How to propose a change" section at the beginning

Right into the "How to propose a change" section, because that's where
it's relevant

Yeah I'm totally getting lazy with the commits, but it's really hard and
takes a long time..

Also mainly covered in the section below

- Contributing without a GitHub account
- Mention OfBorg
- nix.useSandbox -> nix.settings.sandbox
- nixpkgs-review is good for not just version updates

Co-authored-by: Rémi NICOLE <minijackson@users.noreply.github.com>

- Fix sentence about meeting contributing standards
- pkgs -> packages
- Use emoji's because GitHub renders the :*: things weird sometimes
- Move a dot

Co-authored-by: Rémi NICOLE <minijackson@users.noreply.github.com>

This needs a rewrite at some point..