Ideas for improving our processes

changelogs, commit messages, etc

• eliminate names.inc and just link to everyone's GH page
• https://www.conventionalcommits.org/en/v1.0.0/
• https://commitizen-tools.github.io/commitizen/
• https://github.com/github-changelog-generator/github-changelog-generator
• https://conventionalcomments.org/

pre-commit alternative

• https://prek.j178.dev/

MyPy alternative

• https://docs.astral.sh/ty/

monitoring & reporting

• https://github-activity.readthedocs.io/ (uses GH API to generate a date-limited dataframe of issues/PRs)
• https://github.com/github/issue-metrics (Gather metrics on issues/prs/discussions such as time to first response, count of issues opened, closed, etc)
• https://zenodo.org/records/15149379 (huge DB of software mentions in published papers)

ecosystem health

• https://chaoss.community/about-chaoss/
• https://github.com/oss-aspen/8Knot

PRs and merges

• https://github.blog/changelog/2023-02-08-pull-request-merge-queue-public-beta/ (merge queue)

Dependencies

• https://docs.renovatebot.com/ (auto-updating of deps/lockfiles via PR; ability to set minimum age of dep. version before adopting)

testing

• https://testmon.org/ (selects tests affected by changed files and methods)
• https://github.com/moser/pytest-run-changed (ditto)
• https://github.com/scikit-image/scikit-image/pull/7749 (similar idea, coarser approach)

releases

• immutable releases (https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/preventing-changes-to-your-releases)
• https://jacobtomlinson.dev/effver/

refactors

• https://github.com/gauge-sh/tach/tree/main (unmaintained but maybe still useful?)