quality-standards: Potential new rules

[leplatrem]

In the original document we had a few ideas of potential new rules.

This issues brings them here for comment/discussion.

• Require signed commits
• Github Community Standards: Open Source Guides
• Auto-close old issues (not very popular)
• Force pull-request title format? eg. consistent commit history https://www.conventionalcommits.org/en/v1.0.0/
• Monitor cost?
• Sentry creates Github issues?
• Should the application run with production settings by default?
• If version from Git tag, usegit describe --tags --abbrev=4
• Combine Github Actions into one workflow (example)
• Github Actions versions is part of Dependabot (example)
• quality-standards: include a rule for CI system #20
• MozLog request.summary

[leplatrem]

From https://github.com/mozilla-releng/reps/blob/main/STANDARD.md

Anything that is not related to Python precisely:

• details of branch protection
• CodeQL enabled
• documentation should try to follow the Diátaxis technical documentation framework
• yamllint to catch issues in task configuration or dot-files
• rstcheck to catch issues in documentation
• codespell to catch spelling mistakes in comments