Project Structure Rework (documentation, commits, branching, versioning)

[PrivatePuffin]

Motivation, Context and Description

There are a lot of legacy inefficiencies in the current OpenZFS project structure.

In the past weeks i've submitted a number of automation reworks, but working on those a lot more came to light and it isn't feasable to create seperate PR's for every little change. I also came to the conclusion that some of the changes that are required are only relevant if seen in the context of a bigger picture, which was often lacking.

This PR is focussed on documenting and restructuringa lot of these issues.
It has not been squashed on purpose, to clearly seperate commits by purpose.

One of the side goals is to not increase the amount of effort or rules for users and maintainers significantly

Change shortlist:

• Remove OpenZFS Ports section from Contribution Guidelines
• Remove OpenZFS Ports section from stylechecks
• Redesign repo branching guidelines (Change main branch name and document branching structure #10849)
• Document branching structure in contribution guidelines (Change main branch name and document branching structure #10849)
• Add Mailinglist and IRQ links to issues creator
• Disable link to blank-issue creation on issue creator
• Make the Contribution Guidelines compatible with Conventional Commits (Fully embrace the Conventional Commits #10852)
• Add commit types to Contribution Guidelines (Fully embrace the Conventional Commits #10852)
• Have stylechecks utilise types from Conventional Commits
• Adapt Coverity Fixes guidelines to comply with Conventional Commits
• Link commit types to semantic versioning (meta: move to or explicitly endorse semantic versioning for release versions #10334)
• Describe versioning procedure (meta: move to or explicitly endorse semantic versioning for release versions #10334)
• Describe backport procedure and limits (meta: move to or explicitly endorse semantic versioning for release versions #10334)

Pre-merge requirements from maintainers:

This section lists things the maintainers need to add/change before this should be merged. Those aren't supposed to be big changes, but just things we can't fix with a PR.

• Requires the main branch to be renamed to dev (Change main branch name and document branching structure #10849)
• Requires a release branch to be created based on last release (Change main branch name and document branching structure #10849)
• Requires a staging branch to be created based on 2.0 RC1 (Change main branch name and document branching structure #10849)
• Requires opening a OpenZFS discuss mailinglist (Add OpenZFS discuss mailinglist #10845)

How Has This Been Tested?

• The stylecheck changes has been tested by the CI
• The issue creator changes have been tested in a seperate repo

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the ZFS on Linux code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.

Closes #10845
Closes #10849
Closes #10852
Closes #10334
Signed-off-by: Kjeld Schouten-Lebbing [email protected]
Requires-builders: style

[PrivatePuffin]

Scope decreased:
Removed automation from this PR, release/changelog automation can only be merged right after OpenZFS2.0 release, or it would start messing with the release (because that release would be filled with commits missing any type tags etc.)

[codecov]

Codecov Report

Merging #10853 into master will decrease coverage by 0.44%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10853      +/-   ##
==========================================
- Coverage   80.37%   79.93%   -0.45%     
==========================================
  Files         293      395     +102     
  Lines       84962   125066   +40104     
==========================================
+ Hits        68289    99972   +31683     
- Misses      16673    25094    +8421     

Flag	Coverage Δ
#kernel	80.43% <ø> (+0.05%)	⬆️
#user	66.15% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
module/zfs/zcp_set.c	87.09% <0.00%> (-12.91%)	⬇️
module/zfs/zfs_ratelimit.c	90.47% <0.00%> (-9.53%)	⬇️
module/zfs/zfs_byteswap.c	79.45% <0.00%> (-5.85%)	⬇️
module/zfs/dmu_redact.c	82.15% <0.00%> (-5.70%)	⬇️
module/zcommon/zfs_deleg.c	92.45% <0.00%> (-5.55%)	⬇️
module/zfs/dsl_deleg.c	89.70% <0.00%> (-4.46%)	⬇️
module/zfs/vdev_rebuild.c	93.69% <0.00%> (-4.44%)	⬇️
module/zfs/zio_inject.c	75.80% <0.00%> (-4.41%)	⬇️
module/zfs/fm.c	36.77% <0.00%> (-4.41%)	⬇️
module/zfs/spa_checkpoint.c	93.78% <0.00%> (-4.26%)	⬇️
... and 291 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7b8363d...a56c29f. Read the comment docs.

[PrivatePuffin]

Converted to draft due to #10965

[PrivatePuffin]

Closing this in favor of all the previous and up-comming seperate patches.