Transferring JenkinsPipelineUnit to Jenkins Org

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

Transferring JenkinsPipelineUnit to Jenkins Org

Ozan Günalp
Hi,

I am posting this here to have a public discussion: 

As discussed during Jenkins World 2017 we are up for transferring the JenkinsPipelineUnit project into Jenkins Organization.
We naturally want to make sure that current maintainers and LesFurets Org stay collaborators on the project. 

One option was expressed by @OlegNenashev, quote :

https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins covers the hosting process based on forking. In the case of PipelineUnit we would rather prefer moving the project. Usually we use the following approach:
  1. We grant you administrative access to the https://github.com/jenkinsci-transfer organization
  1. You move the project to this organization
  1. One of Jenkins GitHub org admins (e.g. me or Daniel) moves the project to jenkinsci org
Such approach allows to retain issues, stars, followers, etc. There will be also automatic redirect by GitHub, so previous links from external sources won't be broken.

Let me know how to proceed,

Cheers

Ozan

--
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/729c5f51-9ca1-4744-ab6c-0248bb4c6c0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Daniel Beck

> On 20. Sep 2017, at 12:18, Ozan Günalp <[hidden email]> wrote:
>
> We naturally want to make sure that current maintainers and LesFurets Org stay collaborators on the project.

Orgs cannot be orgs of other orgs, but if we make you team maintainers, you can add or remove collaborators at will. That would probably be the best option here.

> One option was expressed by @OlegNenashev, quote :

This would be the preferred approach IMO as well, for the stated reasons.

--
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/0095CA91-0C97-4F4D-9D74-1B56C0333548%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Ozan Günalp


On Wednesday, September 20, 2017 at 1:41:20 PM UTC+2, Daniel Beck wrote:

> On 20. Sep 2017, at 12:18, Ozan Günalp <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="xzO9tcpLBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ozang...@...> wrote:
>
> We naturally want to make sure that current maintainers and LesFurets Org stay collaborators on the project.

Orgs cannot be orgs of other orgs, but if we make you team maintainers, you can add or remove collaborators at will. That would probably be the best option here.
Ok that works for me. 

> One option was expressed by @OlegNenashev, quote :

This would be the preferred approach IMO as well, for the stated reasons. 

Ozan

--
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/3a6a83fc-2cd2-4faa-9618-1f0b10736d4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Oleg Nenashev
+1 from me.
I am ready to iterate once we are ready.

Since it is a kind of strategic move in Pipeline ecosystem, I would propose to have a quick discussion at the Governance meeting today so that anybody can provide feedback.

BR, Oleg

среда, 20 сентября 2017 г., 15:01:47 UTC+3 пользователь Ozan Günalp написал:


On Wednesday, September 20, 2017 at 1:41:20 PM UTC+2, Daniel Beck wrote:

> On 20. Sep 2017, at 12:18, Ozan Günalp <[hidden email]> wrote:
>
> We naturally want to make sure that current maintainers and LesFurets Org stay collaborators on the project.

Orgs cannot be orgs of other orgs, but if we make you team maintainers, you can add or remove collaborators at will. That would probably be the best option here.
Ok that works for me. 

> One option was expressed by @OlegNenashev, quote :

This would be the preferred approach IMO as well, for the stated reasons. 

Ozan

--
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/edfc3a4a-3fb3-4fdb-ab99-35bfcaeeba0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Daniel Beck

> On 27. Sep 2017, at 11:45, Oleg Nenashev <[hidden email]> wrote:
>
> discussion at the Governance meeting today so that anybody can provide feedback

Nobody bothered to speak up in this thread for the past week, so I don't think this is necessary.

--
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/06DAAE82-4B84-4CE9-84D7-7720990D0B00%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Baptiste MATHUS
FWIW, +1 all for it obviously, we've already had the opportunity to discuss this at Jenkins World.

And thanks again for that move Ozan, Emmanuel & your company LesFurets.

IMO the next step is to file a JIRA into the HOSTING project, linking to this thread here (also to essentially remind that a standard fork is not desirable for the typical reasons).

2017-09-27 11:50 GMT+02:00 Daniel Beck <[hidden email]>:

> On 27. Sep 2017, at 11:45, Oleg Nenashev <[hidden email]> wrote:
>
> discussion at the Governance meeting today so that anybody can provide feedback

Nobody bothered to speak up in this thread for the past week, so I don't think this is necessary.

--
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/06DAAE82-4B84-4CE9-84D7-7720990D0B00%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--
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/CANWgJS5HaUs1D%3DWnNwJDNCiKuKYkW-r9rp9e74Sf-TwFt61p7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Ozan Günalp
So is everyone ok with me creating a ticket on the Hosting project even though it is not a plugin hosting request ? 
I was waiting for you to give me admin rights on jenkinsci-transfer organization for making the transfer.

Let me know.

On Friday, September 29, 2017 at 8:55:28 PM UTC+2, Baptiste Mathus wrote:
FWIW, +1 all for it obviously, we've already had the opportunity to discuss this at Jenkins World.

And thanks again for that move Ozan, Emmanuel & your company LesFurets.

IMO the next step is to file a JIRA into the <a href="https://issues.jenkins-ci.org/projects/HOSTING" 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, linking to this thread here (also to essentially remind that a standard fork is not desirable for the typical reasons).

2017-09-27 11:50 GMT+02:00 Daniel Beck <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="VQbVq46sBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">m...@...>:

> On 27. Sep 2017, at 11:45, Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="VQbVq46sBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.ne...@...> wrote:
>
> discussion at the Governance meeting today so that anybody can provide feedback

Nobody bothered to speak up in this thread for the past week, so I don't think this is necessary.

--
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="VQbVq46sBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/06DAAE82-4B84-4CE9-84D7-7720990D0B00%40beckweb.net" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/06DAAE82-4B84-4CE9-84D7-7720990D0B00%40beckweb.net&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/06DAAE82-4B84-4CE9-84D7-7720990D0B00%40beckweb.net&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/06DAAE82-4B84-4CE9-84D7-7720990D0B00%40beckweb.net.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
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/a7d8e3ae-e07f-4ecb-9887-62d299b50a78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Daniel Beck

> On 3. Oct 2017, at 23:57, Ozan Günalp <[hidden email]> wrote:
>
> So is everyone ok with me creating a ticket on the Hosting project even though it is not a plugin hosting request ?

Seems pointless given the discussion having taken place here. This thread gave people plenty of time to object (and it's followed by a lot more people than hosting requests). Since we wouldn't be able to use the bot to fork anyway, there's no reason left to go through hosting.

> I was waiting for you to give me admin rights on jenkinsci-transfer organization for making the transfer.

Done.

Sorry about the delay.

--
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/1B3FAD72-3C89-4530-AC7C-E06F592930E0%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Ozan Günalp
FYI I transferred the project to jenkinsci-transfer organization.

On Wednesday, October 4, 2017 at 12:13:29 AM UTC+2, Daniel Beck wrote:

> On 3. Oct 2017, at 23:57, Ozan Günalp <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="fBaRkMa6BwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ozang...@...> wrote:
>
> So is everyone ok with me creating a ticket on the Hosting project even though it is not a plugin hosting request ?

Seems pointless given the discussion having taken place here. This thread gave people plenty of time to object (and it's followed by a lot more people than hosting requests). Since we wouldn't be able to use the bot to fork anyway, there's no reason left to go through hosting.

> I was waiting for you to give me admin rights on jenkinsci-transfer organization for making the transfer.

Done.

Sorry about the delay.

--
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/c8491978-188e-4d54-bf8f-b62b05653a6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Oleg Nenashev
Hi,

The Repository has been moved, new location is https://github.com/jenkinsci/JenkinsPipelineUnit.
I also created a pipeline-unit-developers team and invited you to it. As Daniel suggested above, members of this team can add new collaborators to the repo if required.

What would be the name of the repository in jenkinsci org? I would propose renaming it to "pipeline-unit".

Anyway, welcome onboard!

BR, Oleg

среда, 4 октября 2017 г., 16:24:14 UTC+2 пользователь Ozan Günalp написал:
FYI I transferred the project to jenkinsci-transfer organization.

On Wednesday, October 4, 2017 at 12:13:29 AM UTC+2, Daniel Beck wrote:

> On 3. Oct 2017, at 23:57, Ozan Günalp <[hidden email]> wrote:
>
> So is everyone ok with me creating a ticket on the Hosting project even though it is not a plugin hosting request ?

Seems pointless given the discussion having taken place here. This thread gave people plenty of time to object (and it's followed by a lot more people than hosting requests). Since we wouldn't be able to use the bot to fork anyway, there's no reason left to go through hosting.

> I was waiting for you to give me admin rights on jenkinsci-transfer organization for making the transfer.

Done.

Sorry about the delay.

--
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/b773cd85-b083-4df1-98cd-225dbda9ceea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Baptiste MATHUS
\o/ Welcome and great! Thanks again everyone.

2017-10-04 19:06 GMT+02:00 Oleg Nenashev <[hidden email]>:
Hi,

The Repository has been moved, new location is https://github.com/jenkinsci/JenkinsPipelineUnit.
I also created a pipeline-unit-developers team and invited you to it. As Daniel suggested above, members of this team can add new collaborators to the repo if required.

What would be the name of the repository in jenkinsci org? I would propose renaming it to "pipeline-unit".

Anyway, welcome onboard!

BR, Oleg

среда, 4 октября 2017 г., 16:24:14 UTC+2 пользователь Ozan Günalp написал:
FYI I transferred the project to jenkinsci-transfer organization.

On Wednesday, October 4, 2017 at 12:13:29 AM UTC+2, Daniel Beck wrote:

> On 3. Oct 2017, at 23:57, Ozan Günalp <[hidden email]> wrote:
>
> So is everyone ok with me creating a ticket on the Hosting project even though it is not a plugin hosting request ?

Seems pointless given the discussion having taken place here. This thread gave people plenty of time to object (and it's followed by a lot more people than hosting requests). Since we wouldn't be able to use the bot to fork anyway, there's no reason left to go through hosting.

> I was waiting for you to give me admin rights on jenkinsci-transfer organization for making the transfer.

Done.

Sorry about the delay.

--
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/b773cd85-b083-4df1-98cd-225dbda9ceea%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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/CANWgJS6eA-iBop%2BuLifPJOVy3ki3VVB1a9P2OqqyxstArpL%2Bbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Transferring JenkinsPipelineUnit to Jenkins Org

Jesse Glick-4
You probably want to enable archetypes then:

https://github.com/jenkinsci/archetypes/pull/25/files#r144350828

--
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/CANfRfr2C7PkifULXVqYcVkVsJN6Gjki50VqaSSgvkSwK%3DqzR8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.