Here is some general feedback:
- On the sync mechanisms between Trac and GitHub, I think I would want you to decide where is the “source of truth” and which is the replica, bi-directional updates could be very confusing. I would also look into improving the API for Trac on djangoproject.com (see Read-only API for retrieving Trac data · Issue #1657 · django/djangoproject.com · GitHub).
- On labeling stale PRs, instead I think PRs which have received a review and their related ticket is updated so that it is no longer in the review queue could get a message of “are you still planning on working on this?” if there is no further activity after 3 months. Then after 1 more month of that PR not being worked on, the PR could be closed. This is something that is done occasionally and manually. Even this needs thought as to whether a bot doing this instead of a human is “wanted” or just rude
- On automated releases, this doesn’t really show much understanding of the current process unfortunately. Instead, I would recommend you look into Natalia’s checklist generator which aims to create checklists of tasks per release: GitHub - nessita/checklist-generator. There is a goal to slowly merge this (with tests) into djangoproject.com and to build this out further. I think if you can run this locally and play around and show that you understand this project, that would be a good first step in this “area”
One area I would love to see more on is around reviewing PRs or giving more feedback to contributors early. Things like: checking test the coverage of new/updated code, if code has changed there is at least some tests written, versionchanged/versionadded notes checked, release notes checked, line length of the docs checked. I would love to see that you have gone through PRs that have been reviewed and our contribution guidelines to show that you have a strong knowledge of Django’s specific processes and where we can make improvements
It’s also worth you showing who the key stakeholders are and how you are going to work with them and bring them onboard to the changes. Django is a community run project and if there are members of the community strongly against these changes, nothing will happen.