Hi all,

Thanks to everyone who contributed to Hosting request processing as a part 
of the previous discussions. As you may have seen in another thread, Alex 
has stepped down from leading the Hosting team. Thanks a lot to Alex for 
all the contributions and the hosting process automation! We will be 
looking for a new team lead and more contributors, anyone is welcome!

I have started a Doodle for the knowledge transfer session about the 
Hosting 
process: 
https://doodle.com/poll/xiqmx4hxfdt8s4in?utm_source=poll&utm_medium=link 
. Hopefully Alex would be available so that we could discuss and document 
parts not yet documented in https://www.jenkins.io/project/teams/hosting/ 
and other related pages. If you are interested to contribute, please vote 
for the timeslots!

Best regards,
Oleg Nenashev
Jenkins Board Member

On Tuesday, May 19, 2020 at 12:04:15 AM UTC+2 slide wrote:

> 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 Jenkins Developer Mailing list 
>>    <https://www.jenkins.io/mailing-lists/#jenkinsci-dev-googlegroups-com>
>>    2. 
>>    
>>    Subscribe to the HOSTING project 
>>    <https://issues.jenkins-ci.org/projects/HOSTING> in Jenkins Jira
>>    3. 
>>    
>>    Subscribe to the Repository Permission Updater 
>>    <https://github.com/jenkins-infra/repository-permissions-updater/>
>>     repository
>>    4. 
>>    
>>    Subscribe to the Jenkins Update Center 
>>    <https://github.com/jenkins-infra/update-center2> repository
>>    
>>
>> On Fri, May 15, 2020 at 3:58 AM Oleg Nenashev <o.v.ne...@gmail.com> 
>> 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 <siiy...@gmail.com> 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 
>>>>>       
>>>>> <https://www.jenkins.io/doc/developer/publishing/preparation/#look-for-similar-plugins>
>>>>>  
>>>>>       and offering to contribute there instead of hosting a new plugin 
>>>>> (but not 
>>>>>       blocking hosting)
>>>>>       - Plugin licenses (see this thread 
>>>>>       <https://groups.google.com/forum/#!topic/jenkinsci-dev/-KprgkVIDpQ>
>>>>>       )
>>>>>    - Processing plugin release permissions in Repository Permission 
>>>>>    Updater 
>>>>>    <https://github.com/jenkins-infra/repository-permissions-updater>. 
>>>>>    There is a @jenkins-infra/hosting 
>>>>>    <https://github.com/orgs/jenkins-infra/teams/hosting> team 
>>>>>    handling it (Alex Earl, Baptiste Mathus and me)
>>>>>    - Processing GitHub permission and Plugin adoption 
>>>>>    
>>>>> <https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/> 
>>>>>    requests in the developer mailing list. There is a number of 
>>>>> contributors 
>>>>>    replying to these requests, most of operations can be done via Jenkins 
>>>>>    IRC bot <https://www.jenkins.io/projects/infrastructure/ircbot/>
>>>>>    - Manual changes in GitHub repositories for some requests, e.g. 
>>>>>    plugin renaming. There is a @jenkinsci/github-admins 
>>>>>    <https://github.com/orgs/jenkinsci/teams/github-admins> team which 
>>>>>    manages such requests
>>>>>    - Processing repo transfer requests (when maintainers want to 
>>>>>    transfer plugins instead of forking), via jenkinsci-transfer org or 
>>>>>    directly. There is a @jenkinsci/github-admins 
>>>>>    <https://github.com/orgs/jenkinsci/teams/github-admins> team which 
>>>>>    manages it 
>>>>>    - Processing blacklisting and plugin tagging/doc URL requests in 
>>>>>    /update-center2 <https://github.com/jenkins-infra/update-center2> 
>>>>>    for non-security reasons. It is currently handled by Daniel Beck and a 
>>>>>    number of other contributors
>>>>>    - Maintaining the Plugin hosting, publishing and governance 
>>>>>    documentation in https://www.jenkins.io/doc/developer. Docs SIG is 
>>>>>    doing some cleanup
>>>>>
>>>>> If we agree that we want to have a more official team, I will create a 
>>>>> new page on jenkins.io for it, similar to the Core Maintainers Guide 
>>>>> <https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc>
>>>>> .
>>>>>
>>>>> Also, looking for new contributors who would like to join the Hosting 
>>>>> and the triage sub-team!
>>>>>
>>>>> Thanks for your feedback,
>>>>> Oleg
>>>>>
>>>>> -- 
>>>> You received this message because you are subscribed to a topic in the 
>>>> Google Groups "Jenkins Developers" group.
>>>> To unsubscribe from this topic, visit 
>>>> https://groups.google.com/d/topic/jenkinsci-dev/ljwhniI-T3U/unsubscribe
>>>> .
>>>>
>>> To unsubscribe from this group and all its topics, send an email to 
>>>> jenkinsci-dev+unsubscr...@googlegroups.com.
>>>
>>>
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/c471d3ef-f54b-4572-a063-5eaafe4a790d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Developers" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC1J9H7-EdM5O8kzqMONX-XO3UkiyWQVAJi4kRF0OWugA%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLC1J9H7-EdM5O8kzqMONX-XO3UkiyWQVAJi4kRF0OWugA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> -- 
>> Shi Yanjun(yJunS)
>> Blog: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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f799bb15-a771-4a48-8d84-093cfe3bd84cn%40googlegroups.com.

Reply via email to