Sponsored Packages Infrastructure

[Cadair]

Having now setup the formal affiliated package process we have quite a few "sponsored" packages which the project maintains. We really need to improve our infrastructure around these to ease the maintenance burden. This could include things such as:

- [x] Improvements to the package-template to allow (semi-)automatic re-templating of repos.
- [ ] Some kind of monitoring bot for CI runs to make sure packages still work with new dependencies.
- [ ] A release prompter bot for when changes have happened but are unreleased.
- [ ] Standard issue set across the org and Issue label syncing
-  [x] Backport bot
- [ ] A bot which listens to command in PR comments to perform actions such as: Add a changelog entry
-  [ ] A newcomers bot which checks author info in commit messages and asks people to put their info in the zenodo file.
- [ ] A milestone bot which milestones PRs merged to a branch based on the last tag on that branch. i.e. PRs to main get the next major version and PRs to bugfix branches get the next bugfix milestone. This should also create new milestones on a release.
- [ ] conda-forge version monitoring for updates / existence of feedstocks.
- [ ] ASV on core PRs
- [ ] A what's new sphinx plugin to make what's new out of a directory.
- [ ] Standardise permissions and git flow settings across all the org (and document them somewhere).
- [ ] A script which after a release opens an issue with links to all the expired deprecations would be a tractable problem
- [ ] A what's new check which fails unless a "no what's new" or "Backport x.x" label is present.
- [ ] Create a install page on the main website repo that uses something like ?packages=sunpy and then have a tiny bit of js which injects the package names to avoid repeating install docs for each package.

[Cadair]

@nabobalis @wtbarnes any suggestions on other things which would be useful?

[nabobalis]

Labeling sync and backport bots?

[Cadair]

I spent a little while poking at the azure pipelines API to see what would be needed to generate a CI status dashboard. From discussions in the sunpy chat a first version of this dashboard would:

• Provide a summary of all sponsored packages and their last build status on all branches
• All sponsored packages should have a nightly cron, so show if a build is >24 hours old
• Send chat alerts under some conditions, tbd.

I found the following request to the Azure API for listing the last build on the master branch:

http GET "https://dev.azure.com/sunpy/sunpy/_apis/build/builds?api-version=6&branchName=refs/heads/master&$top=1"

[Cadair]

First version of the CI dashboard is here: https://sunpy-dashboard.cadair.dev/dashboard still need to add a bunch of things to it.

[Cadair]

Also we need to factor out the matrix notification thing so we can get more detailed failure notifs. I.e. "the online builds failed but the cron ones passed"

[wtbarnes]

Once we figure which of these tasks are going to be prioritized, we should break them out into separate issues and add them to the OSTFL project board

[dstansby]

re. synicing github tags:

• https://twitter.com/choldgraf/status/1563105398604701697
• https://github.com/Financial-Times/github-label-sync