+1 to both, although not planning on it being a primary focus, I'll help out where and when I can
Thanks Tim On Wed, 29 Apr 2020 at 13:02, Marky Jackson <marky.r.jack...@gmail.com> wrote: > For me it is both. +1 for the proposal and +1 to join > > On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > > Hi all. Just to make sure, +1 for the proposal or +1 for joining the > teams? :) > > On Wed, Apr 29, 2020, 13:58 Marky Jackson <marky.r.jack...@gmail.com> > wrote: > >> This is a great idea and I am a +1 >> >> On Wednesday, April 29, 2020 at 2:09:27 AM UTC-7, Oleg Nenashev wrote: >>> >>> Hi all, >>> >>> >>> In the Jenkins community we have an unofficial Hosting team which >>> handles various requests related to plugin hosting (forking/transferring >>> plugins, managing permissions and update center blacklists, etc.) There are >>> multiple contributors involved in this activity on a regular basis, and it >>> would be great to document these processes so that we could use these docs >>> as a reference and as guidelines for onboarding new contributors to help >>> with the hosting process. I would propose to create an official team and to >>> introduce an onboarding process: >>> >>> Proposal >>> >>> - Make the "Hosting Team" official, document its roles somewhere on >>> jenkins.io. Scope: plugin and component hosting on Jenkins resources >>> (GitHub, Update Centers, etc.) >>> - Grant permissions to active contributors who are interested and >>> who already have experience with the hosting process (e.g. Tim Jacomb, >>> Wadeck Follonier) >>> - Create new HOSTING/Mailing list triage guidelines >>> - Invite interested contributors to help with triage of hosting >>> requests as a first onboarding step to get permissions needed for GitHub >>> / >>> Update Site and Repository Permission Updater management >>> >>> Team Responsibilities. Below there are some current responsibilities >>> related to the hosting process. This list is likely incomplete, please feel >>> free to add more items. >>> >>> - Triage and processing of new plugin HOSTING requests in Jenkins >>> Jira. Currently Alex Earl champions it, and there are only a few >>> contributors who help with the requests triage. Such triage is >>> instrumental >>> to... >>> - Ensuring hosted plugins have proper artifactIds. We cannot >>> easily change them later... >>> - Do sanity check of plugins for security issues. Thanks to Alex >>> Earl and the security team for handling it >>> - Checking for duplication with existing plugins >>> >>> <https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins> >>> and offering to contribute there instead of hosting a new plugin >>> (but not blocking hosting) >>> - Plugin licenses (see this thread >>> <https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ> >>> ) >>> - Processing plugin release permissions in Repository Permission >>> Updater >>> <https://github.com/jenkins-infra/repository-permissions-updater>. >>> There is a @jenkins-infra/hosting >>> <https://github.com/orgs/jenkins-infra/teams/hosting> team handling >>> it (Alex Earl, Baptiste Mathus and me) >>> - Processing GitHub permission and Plugin adoption >>> <https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/> >>> requests in the developer mailing list. There is a number of >>> contributors replying to these requests, most of operations can be done >>> via >>> Jenkins IRC bot >>> <https://www.jenkins.io/projects/infrastructure/ircbot/> >>> - Manual changes in GitHub repositories for some requests, e.g. >>> plugin renaming. There is a @jenkinsci/github-admins >>> <https://github.com/orgs/jenkinsci/teams/github-admins> team which >>> manages such requests >>> - Processing repo transfer requests (when maintainers want to >>> transfer plugins instead of forking), via jenkinsci-transfer org or >>> directly. There is a @jenkinsci/github-admins >>> <https://github.com/orgs/jenkinsci/teams/github-admins> team which >>> manages it >>> - Processing blacklisting and plugin tagging/doc URL requests in >>> /update-center2 <https://github.com/jenkins-infra/update-center2> for >>> non-security reasons. It is currently handled by Daniel Beck and a number >>> of other contributors >>> - Maintaining the Plugin hosting, publishing and governance >>> documentation in https://www.jenkins.io/doc/developer. Docs SIG is >>> doing some cleanup >>> >>> If we agree that we want to have a more official team, I will create a >>> new page on jenkins.io for it, similar to the Core Maintainers Guide >>> <https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc> >>> . >>> >>> Also, looking for new contributors who would like to join the Hosting >>> and the triage sub-team! >>> >>> Thanks for your feedback, >>> Oleg >>> >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > -- > 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 on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > -- > 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 on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BickfWcaSjtK8tda02WSoRd6PU2uuYLm%2Brii91%2BDY6j4_Q%40mail.gmail.com.
