Tim Jacomb

I used the virtual assistant recently for one, plugin-pom I think. It was done fairly quickly

see https://github.com/jenkins-infra/repository-permissions-updater/issues/2679#issuecomment-1206357817 (wording could probably be updated as there's now an official process from GitHub side on it)

There's a report here that has all plugins in this situation: https://reports.jenkins.io/github-jenkinsci-fork-report.json

I've created a request for the snakeyaml one

One of the questions is 'have you committed to the repository' I don't think one person will meet that criteria, although possibly they would let an organisation owner do it.

Should be fine to do that, cc @daniel-beck

We could delete those forks? I don't think any of them are used now

can we just block it at artifactory / get jfrog to block it?

For the latest links to work you need to use the update center which has logic for that. Weekly: https://updates.jenkins.io/latest/jenkins.war Not sure exactly what the LTS url is, the script...

This does raise though that ATH is pointing to get.Jenkins.io in run.sh and if that that’s not working we should swap to the update center, let’s keep it open to...