Thanks for the clarification Nicolas! It should help with transitions. I 
had to go through the same during the last year (putting more than 30 
plugins for adoption). It hurts sometimes, but it is really required to 
keep the focus. Thanks a lot for your contributions to the plugins!

I went through the component list in JIRA, and there are few components 
where you are marked as a lead:

   - aws-credentials-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+aws-credentials-plugin>
   - azure-publishersettings-credentials-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+azure-publishersettings-credentials-plugin>
   - ceylon-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+ceylon-plugin>
   - changes-since-last-success-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+changes-since-last-success-plugin>
   - clever-cloud-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+clever-cloud-plugin>
   - container-slaves-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+container-slaves-plugin>
   - docker-custom-build-environment-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+docker-custom-build-environment-plugin>
   - docker-java-api-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+docker-java-api-plugin>
   - docker-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+docker-plugin>
   - docker-slaves-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+docker-slaves-plugin>
   - jna-posix-api-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+jna-posix-api-plugin>
   - jnr-posix-api-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+jnr-posix-api-plugin>
   - naginator-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+naginator-plugin>
   - one-shot-executor-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+one-shot-executor-plugin>
   - slave-prerequisites-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+slave-prerequisites-plugin>
   - timemachine-plugin 
   
<https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+timemachine-plugin>

Would you like us to mark all these plugins for adoption and remove you as 
a default assignee (or change to otheractive maintainers in some components 
like Docker)?

Best regards,
Oleg


On Thursday, February 21, 2019 at 7:18:50 PM UTC+1, nicolas de loof wrote:
>
> Hi!
>
> Over the years I've been working with Jenkins, I've come to adopt or just 
> patch a few plugins. In some cases, I was only delivering a fix, not really 
> adopting the plugin per-se. Many of them I've been contacted to review  
> pull requests while I only provided a fix for a customer but don't use by 
> myself, so hardly can maintain. As this might have led to some confusion 
> nowadays, I would like to clarify for future requests that I don't consider 
> myself an active maintainer on any plugin.  So I would like to formally 
> tell the community that anyone can consider "my" plugins ready to be 
> adopted if there isn't already another active maintainer. This typically 
> includes the few docker-*-plugins I've created or maintained past years. 
> Some people using them for production would be better candidate for a 
> maintener role.
>
> I hope this will possibly avoid some loops to provide maintainership to 
> requesters, for plugins that are already de facto without an active 
> maintainer.
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e74f423c-44a3-40eb-9a2e-f190f31cac87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to