Proposal: Making the Hosting team official (and onboarding new members)

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

Proposal: Making the Hosting team official (and onboarding new members)

Oleg Nenashev
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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c38f37ee-3834-4163-bd0b-69bccfb60c39%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Richard Bywater-3
I think its a good idea to make as many of the teams as possible that are needed to keep Jenkins trucking along official & documented so the proposal makes sense to me.

I'm also interested in helping out the team to help spread the load around a bit.

Richard.

On Wed, 29 Apr 2020 at 21:09, Oleg Nenashev <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c38f37ee-3834-4163-bd0b-69bccfb60c39%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hweqVByGPxciBJLg_yO9VbmGL09LncN9ghmUV-UqBefKFQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Tim Jacomb
+1

On Wed, 29 Apr 2020 at 10:51, Richard Bywater <[hidden email]> wrote:
I think its a good idea to make as many of the teams as possible that are needed to keep Jenkins trucking along official & documented so the proposal makes sense to me.

I'm also interested in helping out the team to help spread the load around a bit.

Richard.

On Wed, 29 Apr 2020 at 21:09, Oleg Nenashev <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c38f37ee-3834-4163-bd0b-69bccfb60c39%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hweqVByGPxciBJLg_yO9VbmGL09LncN9ghmUV-UqBefKFQ%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieV%2B%2BTQSGw4a0h2Sn-Hn_h8894kVpRe52yMktxMUfDUKw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Marky Jackson
In reply to this post by Oleg Nenashev
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 <a href="http://jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">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 <a href="https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;">duplication with existing plugins and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see<a href="https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;"> this thread)
  • Processing plugin release permissions in<a href="https://github.com/jenkins-infra/repository-permissions-updater" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;"> Repository Permission Updater. There is a <a href="https://github.com/orgs/jenkins-infra/teams/hosting" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;">@jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and<a href="https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;"> Plugin adoption requests in the developer mailing list. There is a number of contributors replying to these requests, most of operations can be done via Jenkins<a href="https://www.jenkins.io/projects/infrastructure/ircbot/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;"> IRC bot
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a <a href="https://github.com/orgs/jenkinsci/teams/github-admins" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/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 <a href="https://github.com/orgs/jenkinsci/teams/github-admins" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/github-admins team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in <a href="https://github.com/jenkins-infra/update-center2" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">/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 <a href="https://www.jenkins.io/doc/developer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;">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 <a href="http://jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">jenkins.io for it, similar to the <a href="https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;">Core Maintainers Guide.

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 the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Oleg Nenashev
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 <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Marky Jackson
For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <[hidden email]> 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 <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Tim Jacomb
+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 <[hidden email]> wrote:
For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <[hidden email]> 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 <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BickfWcaSjtK8tda02WSoRd6PU2uuYLm%2Brii91%2BDY6j4_Q%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Oleg Nenashev
Thanks Tim and Marky,

Any help there will be appreciated, any bandwidth improvements and higher bus factor would be great.
Will wait for feedback from Alex Earl and other contributors before touching permissions, working on guidelines.

Everyone is welcome to subscribe to channels (dev mailing list, HOSTING project in Jira, reporsitory-permission-updater).
No special permissions needed to do that and to start contributing and helping users there.

BR, Oleg

On Wednesday, April 29, 2020 at 2:06:25 PM UTC+2, Tim Jacomb wrote:
+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 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="5h3e-4eTBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marky....@...> wrote:
For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="5h3e-4eTBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> 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 <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="5h3e-4eTBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marky....@...> 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 <a href="http://jenkins.io/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;">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 <a href="https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;">duplication with existing plugins and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see<a href="https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;"> this thread)
  • Processing plugin release permissions in<a href="https://github.com/jenkins-infra/repository-permissions-updater" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;"> Repository Permission Updater. There is a <a href="https://github.com/orgs/jenkins-infra/teams/hosting" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;">@jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and<a href="https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;"> Plugin adoption requests in the developer mailing list. There is a number of contributors replying to these requests, most of operations can be done via Jenkins<a href="https://www.jenkins.io/projects/infrastructure/ircbot/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;"> IRC bot
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/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 <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/github-admins team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in <a href="https://github.com/jenkins-infra/update-center2" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">/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 <a href="https://www.jenkins.io/doc/developer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;">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 <a href="http://jenkins.io/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;">jenkins.io for it, similar to the <a href="https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;">Core Maintainers Guide.

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 <a href="https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;">https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to <a href="javascript:" rel="nofollow" target="_blank" gdf-obfuscated-mailto="5h3e-4eTBQAJ" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 <a href="javascript:" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" gdf-obfuscated-mailto="5h3e-4eTBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="5h3e-4eTBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/fc1265ba-389c-436f-85dc-a2ae92b91b4e%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Oleg Nenashev
And thanks to Richard! Much appreciated


On Wednesday, April 29, 2020 at 2:38:24 PM UTC+2, Oleg Nenashev wrote:
Thanks Tim and Marky,

Any help there will be appreciated, any bandwidth improvements and higher bus factor would be great.
Will wait for feedback from Alex Earl and other contributors before touching permissions, working on guidelines.

Everyone is welcome to subscribe to channels (dev mailing list, HOSTING project in Jira, reporsitory-permission-updater).
No special permissions needed to do that and to start contributing and helping users there.

BR, Oleg

On Wednesday, April 29, 2020 at 2:06:25 PM UTC+2, Tim Jacomb wrote:
+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 <[hidden email]> wrote:
For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <[hidden email]> 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 <[hidden email]> 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 <a href="http://jenkins.io/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;">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 <a href="https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;">duplication with existing plugins and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see<a href="https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;"> this thread)
  • Processing plugin release permissions in<a href="https://github.com/jenkins-infra/repository-permissions-updater" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;"> Repository Permission Updater. There is a <a href="https://github.com/orgs/jenkins-infra/teams/hosting" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;">@jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and<a href="https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;"> Plugin adoption requests in the developer mailing list. There is a number of contributors replying to these requests, most of operations can be done via Jenkins<a href="https://www.jenkins.io/projects/infrastructure/ircbot/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;"> IRC bot
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/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 <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/github-admins team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in <a href="https://github.com/jenkins-infra/update-center2" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">/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 <a href="https://www.jenkins.io/doc/developer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;">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 <a href="http://jenkins.io/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;">jenkins.io for it, similar to the <a href="https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;">Core Maintainers Guide.

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 <a href="https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;">https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/43cac1f0-70fa-4e3a-bb07-0e2ad62fea40%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

slide
In reply to this post by Oleg Nenashev
I'm a definite +1 on this. More people looking at the requests and such would definitely be helpful and more people means more ideas on how to streamline and improve the process. 

On Wed, Apr 29, 2020 at 5:38 AM Oleg Nenashev <[hidden email]> wrote:
Thanks Tim and Marky,

Any help there will be appreciated, any bandwidth improvements and higher bus factor would be great.
Will wait for feedback from Alex Earl and other contributors before touching permissions, working on guidelines.

Everyone is welcome to subscribe to channels (dev mailing list, HOSTING project in Jira, reporsitory-permission-updater).
No special permissions needed to do that and to start contributing and helping users there.

BR, Oleg

On Wednesday, April 29, 2020 at 2:06:25 PM UTC+2, Tim Jacomb wrote:
+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 <[hidden email]> wrote:
For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <[hidden email]> 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 <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/fc1265ba-389c-436f-85dc-a2ae92b91b4e%40googlegroups.com.


--

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcMkk3Ah6gujUeb0B_n_eR%2BxP8amr%3D9CbZMdZkuJDtr0Q%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Oleg Nenashev
I created a pull request to jenkins.io with the page for the Hosting team: https://github.com/jenkins-infra/jenkins.io/pull/3142

On Wednesday, April 29, 2020 at 4:59:20 PM UTC+2, slide wrote:
I'm a definite +1 on this. More people looking at the requests and such would definitely be helpful and more people means more ideas on how to streamline and improve the process. 

On Wed, Apr 29, 2020 at 5:38 AM Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="8jnZoPecBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> wrote:
Thanks Tim and Marky,

Any help there will be appreciated, any bandwidth improvements and higher bus factor would be great.
Will wait for feedback from Alex Earl and other contributors before touching permissions, working on guidelines.

Everyone is welcome to subscribe to channels (dev mailing list, HOSTING project in Jira, reporsitory-permission-updater).
No special permissions needed to do that and to start contributing and helping users there.

BR, Oleg

On Wednesday, April 29, 2020 at 2:06:25 PM UTC+2, Tim Jacomb wrote:
+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 <[hidden email]> wrote:
For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <[hidden email]> 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 <[hidden email]> 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 <a href="http://jenkins.io/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;">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 <a href="https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;">duplication with existing plugins and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see<a href="https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;"> this thread)
  • Processing plugin release permissions in<a href="https://github.com/jenkins-infra/repository-permissions-updater" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;"> Repository Permission Updater. There is a <a href="https://github.com/orgs/jenkins-infra/teams/hosting" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;">@jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and<a href="https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;"> Plugin adoption requests in the developer mailing list. There is a number of contributors replying to these requests, most of operations can be done via Jenkins<a href="https://www.jenkins.io/projects/infrastructure/ircbot/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;"> IRC bot
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/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 <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/github-admins team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in <a href="https://github.com/jenkins-infra/update-center2" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">/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 <a href="https://www.jenkins.io/doc/developer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;">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 <a href="http://jenkins.io/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;">jenkins.io for it, similar to the <a href="https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;">Core Maintainers Guide.

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 <a href="https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;">https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="8jnZoPecBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/fc1265ba-389c-436f-85dc-a2ae92b91b4e%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/fc1265ba-389c-436f-85dc-a2ae92b91b4e%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/fc1265ba-389c-436f-85dc-a2ae92b91b4e%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/fc1265ba-389c-436f-85dc-a2ae92b91b4e%40googlegroups.com.


--
Website: <a href="http://earl-of-code.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fearl-of-code.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6n4PgqhQTRQjanfDfEls_aRabFg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fearl-of-code.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6n4PgqhQTRQjanfDfEls_aRabFg&#39;;return true;">http://earl-of-code.com

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ba42b3db-f608-451f-aef4-324f6aeba086%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Sladyn Nunes
+1 on this proposal, I would love to learn and contribute wherever I can.
Thanks and stay safe 

On Wed, Apr 29, 2020, 8:40 PM Oleg Nenashev <[hidden email]> wrote:
I created a pull request to jenkins.io with the page for the Hosting team: https://github.com/jenkins-infra/jenkins.io/pull/3142

On Wednesday, April 29, 2020 at 4:59:20 PM UTC+2, slide wrote:
I'm a definite +1 on this. More people looking at the requests and such would definitely be helpful and more people means more ideas on how to streamline and improve the process. 

On Wed, Apr 29, 2020 at 5:38 AM Oleg Nenashev <[hidden email]> wrote:
Thanks Tim and Marky,

Any help there will be appreciated, any bandwidth improvements and higher bus factor would be great.
Will wait for feedback from Alex Earl and other contributors before touching permissions, working on guidelines.

Everyone is welcome to subscribe to channels (dev mailing list, HOSTING project in Jira, reporsitory-permission-updater).
No special permissions needed to do that and to start contributing and helping users there.

BR, Oleg

On Wednesday, April 29, 2020 at 2:06:25 PM UTC+2, Tim Jacomb wrote:
+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 <[hidden email]> wrote:
For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <[hidden email]> 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 <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/fc1265ba-389c-436f-85dc-a2ae92b91b4e%40googlegroups.com.


--

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ba42b3db-f608-451f-aef4-324f6aeba086%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC-LeqsRsOgO%2B_oEv00mQeNg0BDyRyJ_sGKb9-f_FKQho1JhAg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Vlad Silverman
In reply to this post by Marky Jackson
Great idea! I am +1 for both

On Apr 29, 2020, at 5:02 AM, Marky Jackson <[hidden email]> wrote:

For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <[hidden email]> 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 <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/219C9596-6EC2-4BF6-922A-F28DF8E5136F%40gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Gavin Mogan
I'm +1 for formalizing processes and spreading  out the load.


I'm also volunteering for said team. With the exception of the hosting jira tickets I have been trying to review and reply to emails and chat requests as much as I can


On Wed., Apr. 29, 2020, 9:26 a.m. Vlad Silverman, <[hidden email]> wrote:
Great idea! I am +1 for both

On Apr 29, 2020, at 5:02 AM, Marky Jackson <[hidden email]> wrote:

For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <[hidden email]> 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 <[hidden email]> 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/219C9596-6EC2-4BF6-922A-F28DF8E5136F%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuvCt8rkDSd7%3DA5jUGfOdua1a9eJzvuduB1rY_XcMknFbg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Oleg Nenashev
Hi all,

The first version of the Hosting team documentation is live: https://www.jenkins.io/project/teams/hosting/. There is a section for newcomer contributors who are interested to help in this area: https://www.jenkins.io/project/teams/hosting/#assisting-with-qa-and-request-reviews. Thanks to everyone who is interested, welcome aboard!

To have a group for the new onboarding team without merge permissions, I created @jenkins-infra/hosting-contributors. The name is not ideal since we have @jenkins-infra/hosting for the team members with full permissions. Suggestions about better naming are more than welcome.

I also created https://issues.jenkins-ci.org/browse/INFRA-2599 to get Richard added to the jenkins-infra organization, I have no permissions to invite members.

Best regards,
Oleg

On Wednesday, April 29, 2020 at 6:32:24 PM UTC+2, Gavin Mogan wrote:
I'm +1 for formalizing processes and spreading  out the load.


I'm also volunteering for said team. With the exception of the hosting jira tickets I have been trying to review and reply to emails and chat requests as much as I can


On Wed., Apr. 29, 2020, 9:26 a.m. Vlad Silverman, <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="OHw2mQuiBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">vsilv...@...> wrote:
Great idea! I am +1 for both

On Apr 29, 2020, at 5:02 AM, Marky Jackson <<a href="javascript:" rel="nofollow" target="_blank" gdf-obfuscated-mailto="OHw2mQuiBQAJ" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marky....@...> wrote:

For me it is both. +1 for the proposal and +1 to join

On Apr 29, 2020, at 5:01 AM, Oleg Nenashev <<a href="javascript:" rel="nofollow" target="_blank" gdf-obfuscated-mailto="OHw2mQuiBQAJ" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> 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 <<a href="javascript:" rel="nofollow" target="_blank" gdf-obfuscated-mailto="OHw2mQuiBQAJ" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">marky....@...> 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 <a href="http://jenkins.io/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;">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 <a href="https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;">duplication with existing plugins and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see<a href="https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;"> this thread)
  • Processing plugin release permissions in<a href="https://github.com/jenkins-infra/repository-permissions-updater" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;"> Repository Permission Updater. There is a <a href="https://github.com/orgs/jenkins-infra/teams/hosting" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;">@jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and<a href="https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;"> Plugin adoption requests in the developer mailing list. There is a number of contributors replying to these requests, most of operations can be done via Jenkins<a href="https://www.jenkins.io/projects/infrastructure/ircbot/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;"> IRC bot
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/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 <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/github-admins team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in <a href="https://github.com/jenkins-infra/update-center2" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">/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 <a href="https://www.jenkins.io/doc/developer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;">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 <a href="http://jenkins.io/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEo1lmJhX4WqqsewrasDhmLvTPo3A&#39;;return true;">jenkins.io for it, similar to the <a href="https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;">Core Maintainers Guide.

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 <a href="https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;">https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to <a href="javascript:" rel="nofollow" target="_blank" gdf-obfuscated-mailto="OHw2mQuiBQAJ" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/cb01649c-78ea-4627-be12-eef11386d4b7%40googlegroups.com.

-- 
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 <a href="javascript:" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" rel="nofollow" target="_blank" gdf-obfuscated-mailto="OHw2mQuiBQAJ" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" style="font-family:Helvetica;font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCwuXA4e_aohdG2H%2BZHUeZD966DAP5n6wtCJHv6063iog%40mail.gmail.com.


--
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 <a href="javascript:" rel="nofollow" target="_blank" gdf-obfuscated-mailto="OHw2mQuiBQAJ" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/55660D28-44D5-42FD-84F3-1EE641DB893A%40gmail.com.

--
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 <a href="javascript:" rel="nofollow" target="_blank" gdf-obfuscated-mailto="OHw2mQuiBQAJ" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/219C9596-6EC2-4BF6-922A-F28DF8E5136F%40gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/219C9596-6EC2-4BF6-922A-F28DF8E5136F%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/219C9596-6EC2-4BF6-922A-F28DF8E5136F%40gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/219C9596-6EC2-4BF6-922A-F28DF8E5136F%40gmail.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/73940e72-7295-4d86-a2cb-11fbcf7b5c7d%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

YanJun Shi
In reply to this post by Oleg Nenashev
I hope to join this team and contribute my strength

On Wednesday, April 29, 2020 at 5:09:27 PM UTC+8, 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 <a href="http://jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">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 <a href="https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;">duplication with existing plugins and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see<a href="https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;"> this thread)
  • Processing plugin release permissions in<a href="https://github.com/jenkins-infra/repository-permissions-updater" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;"> Repository Permission Updater. There is a <a href="https://github.com/orgs/jenkins-infra/teams/hosting" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;">@jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and<a href="https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;"> Plugin adoption requests in the developer mailing list. There is a number of contributors replying to these requests, most of operations can be done via Jenkins<a href="https://www.jenkins.io/projects/infrastructure/ircbot/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;"> IRC bot
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a <a href="https://github.com/orgs/jenkinsci/teams/github-admins" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/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 <a href="https://github.com/orgs/jenkinsci/teams/github-admins" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/github-admins team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in <a href="https://github.com/jenkins-infra/update-center2" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">/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 <a href="https://www.jenkins.io/doc/developer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;">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 <a href="http://jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">jenkins.io for it, similar to the <a href="https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;">Core Maintainers Guide.

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 the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

Oleg Nenashev
Hi, thanks for your interest! You are welcome to join and to start contributing to hosting reviews. No special permissions needed to get started: https://www.jenkins.io/project/teams/hosting/#assisting-with-qa-and-request-reviews

And thanks for submitting ICLA!

On Sun, May 10, 2020, 04:45 YanJun Shi <[hidden email]> wrote:
I hope to join this team and contribute my strength

On Wednesday, April 29, 2020 at 5:09:27 PM UTC+8, 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC1J9H7-EdM5O8kzqMONX-XO3UkiyWQVAJi4kRF0OWugA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

YanJun Shi
Okay. Thank you for your help, Oleg. I already have done the 4 steps, Is there any other steps I need to do?

  1. Subscribe to the Jenkins Developer Mailing list

  2. Subscribe to the HOSTING project in Jenkins Jira

  3. Subscribe to the Repository Permission Updater repository

  4. Subscribe to the Jenkins Update Center repository


On Fri, May 15, 2020 at 3:58 AM Oleg Nenashev <[hidden email]> wrote:
Hi, thanks for your interest! You are welcome to join and to start contributing to hosting reviews. No special permissions needed to get started: https://www.jenkins.io/project/teams/hosting/#assisting-with-qa-and-request-reviews

And thanks for submitting ICLA!

On Sun, May 10, 2020, 04:45 YanJun Shi <[hidden email]> wrote:
I hope to join this team and contribute my strength

On Wednesday, April 29, 2020 at 5:09:27 PM UTC+8, 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 and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see this thread)
  • Processing plugin release permissions in Repository Permission Updater. There is a @jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and Plugin adoption 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
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a @jenkinsci/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 team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in /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.

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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC1J9H7-EdM5O8kzqMONX-XO3UkiyWQVAJi4kRF0OWugA%40mail.gmail.com.


--
Shi Yanjun(yJunS)

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALfBRDr%2BX0gs30sZ46rMtVUPEjXpzte5D%3DLey59wpD-yp_-%2Bcw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Proposal: Making the Hosting team official (and onboarding new members)

slide
FYI, there are a couple of hosting requests that could use a review right now if anyone wants to take a look. I am going to put up a page on jenkins.io for things to look for in the code. I would recommend waiting until the automated checker (it shows up as me, Alex Earl) marks things as good to go for a human review of the code. Before that happens, the developers of the plugin need to have certain things in place and correct before we even consider doing a review of the code. I'll try and get that doc up on jenkins.io this week.

On Friday, May 15, 2020 at 6:51:33 AM UTC-7, YanJun Shi wrote:
Okay. Thank you for your help, Oleg. I already have done the 4 steps, Is there any other steps I need to do?

  1. Subscribe to the <a href="https://www.jenkins.io/mailing-lists/#jenkinsci-dev-googlegroups-com" style="color:rgb(0,102,153);background-color:transparent" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fmailing-lists%2F%23jenkinsci-dev-googlegroups-com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHsdVCQlkuCRosFlwopqrf3H1SBkA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fmailing-lists%2F%23jenkinsci-dev-googlegroups-com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHsdVCQlkuCRosFlwopqrf3H1SBkA&#39;;return true;">Jenkins Developer Mailing list

  2. Subscribe to the <a href="https://issues.jenkins-ci.org/projects/HOSTING" style="color:rgb(0,102,153);background-color:transparent" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fprojects%2FHOSTING\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF2LxYRH-OMrjakirHk85WDQCRJWw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fprojects%2FHOSTING\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF2LxYRH-OMrjakirHk85WDQCRJWw&#39;;return true;">HOSTING project in Jenkins Jira

  3. Subscribe to the <a href="https://github.com/jenkins-infra/repository-permissions-updater/" style="color:rgb(0,102,153);background-color:transparent" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFcWVq8KHaUItF9eFurQcXeiQVuGw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFcWVq8KHaUItF9eFurQcXeiQVuGw&#39;;return true;">Repository Permission Updater repository

  4. Subscribe to the <a href="https://github.com/jenkins-infra/update-center2" style="color:rgb(0,102,153);background-color:transparent" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">Jenkins Update Center repository


On Fri, May 15, 2020 at 3:58 AM Oleg Nenashev <[hidden email]> wrote:
Hi, thanks for your interest! You are welcome to join and to start contributing to hosting reviews. No special permissions needed to get started: <a href="https://www.jenkins.io/project/teams/hosting/#assisting-with-qa-and-request-reviews" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Fteams%2Fhosting%2F%23assisting-with-qa-and-request-reviews\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGYBs-wlfHjsk31CHosJlhx4Etarg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fproject%2Fteams%2Fhosting%2F%23assisting-with-qa-and-request-reviews\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGYBs-wlfHjsk31CHosJlhx4Etarg&#39;;return true;">https://www.jenkins.io/project/teams/hosting/#assisting-with-qa-and-request-reviews

And thanks for submitting ICLA!

On Sun, May 10, 2020, 04:45 YanJun Shi <[hidden email]> wrote:
I hope to join this team and contribute my strength

On Wednesday, April 29, 2020 at 5:09:27 PM UTC+8, 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 <a href="http://jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">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 <a href="https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fpublishing%2Fpreparation%2F%23look-for-similar-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIftRzIRJ5sbfvYLSNY9glTfp34Q&#39;;return true;">duplication with existing plugins and offering to contribute there instead of hosting a new plugin (but not blocking hosting)
    • Plugin licenses (see<a href="https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ&#39;;return true;"> this thread)
  • Processing plugin release permissions in<a href="https://github.com/jenkins-infra/repository-permissions-updater" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEe8kpefIUOGIrPqFhgHVP4w2c9KA&#39;;return true;"> Repository Permission Updater. There is a <a href="https://github.com/orgs/jenkins-infra/teams/hosting" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkins-infra%2Fteams%2Fhosting\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFG_PFUB15UJcFBNCWZ1_lPjcuKjg&#39;;return true;">@jenkins-infra/hosting team handling it (Alex Earl, Baptiste Mathus and me)
  • Processing GitHub permission and<a href="https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper%2Fplugin-governance%2Fadopt-a-plugin%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGs3ff-HsAmaQWbA3sEPq4aUkRmiA&#39;;return true;"> Plugin adoption requests in the developer mailing list. There is a number of contributors replying to these requests, most of operations can be done via Jenkins<a href="https://www.jenkins.io/projects/infrastructure/ircbot/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fprojects%2Finfrastructure%2Fircbot%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFgT5pbsAQNo_Ojwumd_sOzfG4tmw&#39;;return true;"> IRC bot
  • Manual changes in GitHub repositories for some requests, e.g. plugin renaming. There is a <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/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 <a href="https://github.com/orgs/jenkinsci/teams/github-admins" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Forgs%2Fjenkinsci%2Fteams%2Fgithub-admins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF_sR_3J50srKa-Mueh70QlHPz0oQ&#39;;return true;">@jenkinsci/github-admins team which manages it 
  • Processing blacklisting and plugin tagging/doc URL requests in <a href="https://github.com/jenkins-infra/update-center2" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">/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 <a href="https://www.jenkins.io/doc/developer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jenkins.io%2Fdoc%2Fdeveloper\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHQmHDYsFhVvBkIBJqj-1zrhRhVsA&#39;;return true;">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 <a href="http://jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">jenkins.io for it, similar to the <a href="https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fdocs%2FMAINTAINERS.adoc\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGaizIFzq4vvMJMdyNyhUHq3sHxXw&#39;;return true;">Core Maintainers Guide.

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 <a href="https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe&#39;;return true;">https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC1J9H7-EdM5O8kzqMONX-XO3UkiyWQVAJi4kRF0OWugA%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC1J9H7-EdM5O8kzqMONX-XO3UkiyWQVAJi4kRF0OWugA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC1J9H7-EdM5O8kzqMONX-XO3UkiyWQVAJi4kRF0OWugA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC1J9H7-EdM5O8kzqMONX-XO3UkiyWQVAJi4kRF0OWugA%40mail.gmail.com.


--
Shi Yanjun(yJunS)
Blog:<a href="https://github.com/yJunS" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FyJunS\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFyY_G2HBv-uASoVWmCzAp0j5Orug&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FyJunS\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFyY_G2HBv-uASoVWmCzAp0j5Orug&#39;;return true;">https://github.com/yJunS

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ab6524d4-64c2-49b9-acff-9c8d384799a7%40googlegroups.com.