Hello, Am I correct to interpret that non-plugin repositories are NOT included by default? For example, Jenkinsfile Runner or Custom War Packager from what I see on my list in https://github.com/jenkins-infra/repository-permissions-updater
P.S: Just in case, +1 for Community Plugin Maintainers working on plugins where I am listed as a maintainer. I have not returned from sabbatical yet, and not all "my" plugins put for adoption have been adopted yet. Best regards, Oleg On Monday, August 11, 2025 at 5:31:39 PM UTC+2 Mark Waite wrote: > In February, I sent a message > <https://groups.google.com/g/jenkinsci-dev/c/Me9Swhh-Mgc/m/0OvM7ymrAQAJ> > proposing > the community plugin maintainers initiative > <https://docs.google.com/document/d/1GEI7tQp3UxGCbQQyF1JdujgwkoWcMluvUMFanV2nDGo/edit?usp=sharing> > > as a way to accelerate larger improvements within the Jenkins project. > Thanks to all those who have provided feedback and comments. > > We plan to use the September 16, 2025 release of Java 25 as the first > project in the community plugin maintainers initiative. The Jenkins > project wants to support Java 25 soon after its release and that is > expected to require improvements to Jenkins core, Jenkins plugins, and > Jenkins development tooling. > > Plugins are included in the community plugin maintainer initiative by > default. Plugin maintainers may choose to not participate in the community > plugin maintainers initiative. Community plugin maintainers will honor > that choice. Plugins that are not participating in the initiative will > rely on plugin maintainers to merge pull requests that are part of a plugin > maintenance project. > > Plugin maintainers opt out of this initiative by making a repository > permissions updater entry for their plugin. The entry looks like this: > > communityPluginMaintainers: false > > When a plugin maintainer opts out of the initiative, the community plugin > maintainers will still provide pull requests to complete the plugin > maintenance project. They will expect that the plugin maintainer will > review the pull request, merge it, and release it. > > A pull request > <https://github.com/jenkins-infra/repository-permissions-updater/pull/4579> > to the repository permissions updater has been submitted to show the > technique > > Thanks, > Mark Waite > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/8121f3ec-2dbf-4f8e-9244-68977aa738cfn%40googlegroups.com.
