[Adopt a plugin] crowd2-plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Adopt a plugin] crowd2-plugin

mail
Hi all,

as discussed in https://issues.jenkins-ci.org/browse/JENKINS-27070 I
would love to help out fixing the open issues of crowd2-plugin. It is
not marked for apoption yet, but it saw its last commit four years!
ago.

My account username is pingunaut, I'm already maintaining the small
schedule-build plugin.

Best regards,
Martin

--
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/8fc5a1798eed7c6ba4eb4ef39349a79cdc233f72.camel%40martinspielmann.de.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [Adopt a plugin] crowd2-plugin

Kanstantsin Shautsou-2
As i already wrote to somebody else, i'm not maintaining this plugin anymore. Dealing with acegi-security is waste of time in 2018 year. 
Also please remove me from jira assigns. 
Huge refactoring to the right acegi/jenkins api consumption is still available in branch (remember me works for non SSO configuration, SSO needs fix/change in one place). If you want to have correct plugin implementation you can end refactored and cleaned code.


On Monday, June 4, 2018 at 10:04:24 PM UTC+3, Martin Spielmann wrote:
Hi all,

as discussed in <a href="https://issues.jenkins-ci.org/browse/JENKINS-27070" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-27070\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE68Iojp7WawxHpwcYBQ2jvu7sBOA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-27070\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE68Iojp7WawxHpwcYBQ2jvu7sBOA&#39;;return true;">https://issues.jenkins-ci.org/browse/JENKINS-27070 I
would love to help out fixing the open issues of crowd2-plugin. It is
not marked for apoption yet, but it saw its last commit four years!
ago.

My account username is pingunaut, I'm already maintaining the small
schedule-build plugin.

Best regards,
Martin

--
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/d2842194-70d4-4852-8fcb-66fad7384d50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [Adopt a plugin] crowd2-plugin

Oleg Nenashev
Hi Martin and Kanstantin,

Thanks Kanstantin! I consider the response as a confirmation, and I'd guess the previous thread was here. The new maintainer has never committed something, so I do not consider him as a maintainer. I removed you from JIRA assigns.

Martin, I have transferred ownership to you. If you are not in the Jenkinsci GitHub organization, you should receive an email. Once you are ready to release, you will also need to update https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-crowd2.yml

Welcome aboard!

Best regards,
Oleg

On Wednesday, June 6, 2018 at 11:36:47 PM UTC+2, Kanstantsin Shautsou wrote:
As i already wrote to somebody else, i'm not maintaining this plugin anymore. Dealing with acegi-security is waste of time in 2018 year. 
Also please remove me from jira assigns. 
Huge refactoring to the right acegi/jenkins api consumption is still available in branch (remember me works for non SSO configuration, SSO needs fix/change in one place). If you want to have correct plugin implementation you can end refactored and cleaned code.


On Monday, June 4, 2018 at 10:04:24 PM UTC+3, Martin Spielmann wrote:
Hi all,

as discussed in <a href="https://issues.jenkins-ci.org/browse/JENKINS-27070" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-27070\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE68Iojp7WawxHpwcYBQ2jvu7sBOA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-27070\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE68Iojp7WawxHpwcYBQ2jvu7sBOA&#39;;return true;">https://issues.jenkins-ci.org/browse/JENKINS-27070 I
would love to help out fixing the open issues of crowd2-plugin. It is
not marked for apoption yet, but it saw its last commit four years!
ago.

My account username is pingunaut, I'm already maintaining the small
schedule-build plugin.

Best regards,
Martin

--
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/8fafa1c1-6807-48bb-a3fc-63d2e7f58974%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.