Review our OSS contribution doc

[GuySartorelli]

This issue used to be https://github.com/silverstripeltd/product-issues/issues/783 but there was no need for it to be private.

At Stripecon 2023 we're giving a talk that aims to promote contributions to Silverstripe CMS open source. We should make sure our documentation is up to date so that people can contribute confidently and effectively.

Acceptance criteria

• Review and streamline our contribution doc
• Validate the doc and the doc update with our bespoke teams

Notes

• Symfony has some great examples on this front:
  • https://symfonycasts.com/screencast/contributing
  • https://symfony.com/doc/current/contributing/index.html
• Ignore the release process doc which will be handled in https://github.com/silverstripeltd/product-issues/issues/815
• Ignore the coding conventions doc which will be handled in Review best practice docs #323

PRs

IMPORTANT These are likely to have significant merge conflicts with CMS 5 docs. When you have merged all the PRs, reassign to Guy so they can merge up and resolve the conflicts.

Just content changes

Just updating content - not moving anything, ideally

• DOC Update bug reports page #357
• DOC Update contributing code page #358
• DOC Move labels into issues page #359
• DOC Update build tooling docs #361
• DOC Remove doc about how to make a release #362
• DOC Update contributing docs page #367
• DOC Remove references to quarterly releases. #368
• DOC Update translation docs #369
• DOC Update triage and review docs #370
• DOC Update security issues docs #371
• DOC Update index for contributing docs #372

Content and some structural changes

Updates to content, and moving content around between pages

• DOC Update issues/bugs page #378
• DOC Update contributing code docs #379
• DOC Update documentation about documenation #380
• DOC Update translation doc #381
• DOC Update triage resources #382
• DOC Update maintainer guidelines #383
• DOC Specify what makes a "core" module different #384

Pure structural changes

Reordering pages altogether

• DOC Restructure the contributing docs #385

[GuySartorelli]

@emteknetnz Looks like you've approved a lot of PRs but not merged anything?

[emteknetnz]

Assigned back to @GuySartorelli for Steps required after merging the below PRs

[GuySartorelli]

Reopening for the remaining todo stuff

[emteknetnz]

@GuySartorelli have merged the new PR - is there anything left? You can probably re-close?

[GuySartorelli]

That's all this time