Hosting process

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

Hosting process

slide
Based on some feedback from various people during plugin hosting requests, our current method of forking and renaming repositories is not as desirable as one might hope. I am thinking of creating a JEP to change the process, but wanted to solicit some feedback before I do so. I would like to propose that the process be changed as follows:

1) Person/Org submits request to the HOSTING project, but the New Repository Name field is removed. 
2) The normal checks occur, however, now the originating repository name must follow the rules that we normally used for New Repository Name (e.g., if a plugin it must end in -plugin, no camelcase, etc). 
3) Once the plugin has has completed the review process as it does now (automated checker and human review) the requester would initiate a repository transfer request on Github
4) Once the transfer request has been submitted, the ircbot would be updated such that the "host" command would accept the transfer and setup the teams on the repository to complete the transfer.

This would remove the need for users to break the relationship between the originating repository and the jenkinsci repository (which would become the canonical repository).

Please let me know your thoughts on this process change idea. If it has good feedback, I'll submit a JEP to document the process.

--

--
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/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

Gavin Mogan
+1
I like the idea of not having to contact support to break the link


On Tue, Aug 27, 2019 at 10:01 AM Slide <[hidden email]> wrote:
Based on some feedback from various people during plugin hosting requests, our current method of forking and renaming repositories is not as desirable as one might hope. I am thinking of creating a JEP to change the process, but wanted to solicit some feedback before I do so. I would like to propose that the process be changed as follows:

1) Person/Org submits request to the HOSTING project, but the New Repository Name field is removed. 
2) The normal checks occur, however, now the originating repository name must follow the rules that we normally used for New Repository Name (e.g., if a plugin it must end in -plugin, no camelcase, etc). 
3) Once the plugin has has completed the review process as it does now (automated checker and human review) the requester would initiate a repository transfer request on Github
4) Once the transfer request has been submitted, the ircbot would be updated such that the "host" command would accept the transfer and setup the teams on the repository to complete the transfer.

This would remove the need for users to break the relationship between the originating repository and the jenkinsci repository (which would become the canonical repository).

Please let me know your thoughts on this process change idea. If it has good feedback, I'll submit a JEP to document the process.

--

--
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/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%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/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

Matt Sicker
Sounds like a good idea.

On Tue, Aug 27, 2019 at 12:03 PM 'Gavin Mogan' via Jenkins Developers
<[hidden email]> wrote:

>
> +1
> I like the idea of not having to contact support to break the link
>
>
> On Tue, Aug 27, 2019 at 10:01 AM Slide <[hidden email]> wrote:
>>
>> Based on some feedback from various people during plugin hosting requests, our current method of forking and renaming repositories is not as desirable as one might hope. I am thinking of creating a JEP to change the process, but wanted to solicit some feedback before I do so. I would like to propose that the process be changed as follows:
>>
>> 1) Person/Org submits request to the HOSTING project, but the New Repository Name field is removed.
>> 2) The normal checks occur, however, now the originating repository name must follow the rules that we normally used for New Repository Name (e.g., if a plugin it must end in -plugin, no camelcase, etc).
>> 3) Once the plugin has has completed the review process as it does now (automated checker and human review) the requester would initiate a repository transfer request on Github
>> 4) Once the transfer request has been submitted, the ircbot would be updated such that the "host" command would accept the transfer and setup the teams on the repository to complete the transfer.
>>
>> This would remove the need for users to break the relationship between the originating repository and the jenkinsci repository (which would become the canonical repository).
>>
>> Please let me know your thoughts on this process change idea. If it has good feedback, I'll submit a JEP to document the process.
>>
>> --
>> Website: 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/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%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/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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/CAEot4ow%2BuDOThca%3DjzYvgB1Pc7P0N%3DhGxtSXpXa%2BRgQwFD%2BM2g%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

Oleg Nenashev
 the requester would initiate a repository transfer request on Github

Note that it used to require some additional automation logic, because a contributor cannot just move a project to jenkinsci.
It has to happen through an intermediate organization like https://github.com/jenkinsci-transfer we use now.

I need to test whether there is a transfer request feature in GitHub and whether we can automate the bot somehow. If so, this is perfect

 

On Wednesday, August 28, 2019 at 5:16:04 PM UTC+2, Matt Sicker wrote:
Sounds like a good idea.

On Tue, Aug 27, 2019 at 12:03 PM 'Gavin Mogan' via Jenkins Developers
<<a href="javascript:" target="_blank" gdf-obfuscated-mailto="J8jyw2kqBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com> wrote:

>
> +1
> I like the idea of not having to contact support to break the link
>
>
> On Tue, Aug 27, 2019 at 10:01 AM Slide <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="J8jyw2kqBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">slid...@...> wrote:
>>
>> Based on some feedback from various people during plugin hosting requests, our current method of forking and renaming repositories is not as desirable as one might hope. I am thinking of creating a JEP to change the process, but wanted to solicit some feedback before I do so. I would like to propose that the process be changed as follows:
>>
>> 1) Person/Org submits request to the HOSTING project, but the New Repository Name field is removed.
>> 2) The normal checks occur, however, now the originating repository name must follow the rules that we normally used for New Repository Name (e.g., if a plugin it must end in -plugin, no camelcase, etc).
>> 3) Once the plugin has has completed the review process as it does now (automated checker and human review) the requester would initiate a repository transfer request on Github
>> 4) Once the transfer request has been submitted, the ircbot would be updated such that the "host" command would accept the transfer and setup the teams on the repository to complete the transfer.
>>
>> This would remove the need for users to break the relationship between the originating repository and the jenkinsci repository (which would become the canonical repository).
>>
>> Please let me know your thoughts on this process change idea. If it has good feedback, I'll submit a JEP to document the process.
>>
>> --
>> 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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="J8jyw2kqBQAJ" 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/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%40mail.gmail.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%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="J8jyw2kqBQAJ" 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/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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/a9f09d9d-7c03-4610-993d-c5a448134192%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

slide

On Wed, Aug 28, 2019 at 8:59 AM Oleg Nenashev <[hidden email]> wrote:
 the requester would initiate a repository transfer request on Github

Note that it used to require some additional automation logic, because a contributor cannot just move a project to jenkinsci.
It has to happen through an intermediate organization like https://github.com/jenkinsci-transfer we use now.

I need to test whether there is a transfer request feature in GitHub and whether we can automate the bot somehow. If so, this is perfect


Correct, the transfer request is initiated by someone with access on the origin repository side, but the request has to be authorized by the receiving organization. The automation of the transfer request acceptance is definitely something that needs to be figured out.

 
 

On Wednesday, August 28, 2019 at 5:16:04 PM UTC+2, Matt Sicker wrote:
Sounds like a good idea.

On Tue, Aug 27, 2019 at 12:03 PM 'Gavin Mogan' via Jenkins Developers
<[hidden email]> wrote:

>
> +1
> I like the idea of not having to contact support to break the link
>
>
> On Tue, Aug 27, 2019 at 10:01 AM Slide <[hidden email]> wrote:
>>
>> Based on some feedback from various people during plugin hosting requests, our current method of forking and renaming repositories is not as desirable as one might hope. I am thinking of creating a JEP to change the process, but wanted to solicit some feedback before I do so. I would like to propose that the process be changed as follows:
>>
>> 1) Person/Org submits request to the HOSTING project, but the New Repository Name field is removed.
>> 2) The normal checks occur, however, now the originating repository name must follow the rules that we normally used for New Repository Name (e.g., if a plugin it must end in -plugin, no camelcase, etc).
>> 3) Once the plugin has has completed the review process as it does now (automated checker and human review) the requester would initiate a repository transfer request on Github
>> 4) Once the transfer request has been submitted, the ircbot would be updated such that the "host" command would accept the transfer and setup the teams on the repository to complete the transfer.
>>
>> This would remove the need for users to break the relationship between the originating repository and the jenkinsci repository (which would become the canonical repository).
>>
>> Please let me know your thoughts on this process change idea. If it has good feedback, I'll submit a JEP to document the process.
>>
>> --
>> Website: 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/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%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/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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/a9f09d9d-7c03-4610-993d-c5a448134192%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/CAPiUgVea1oZG7yWsAwjbEUyz1HOWMfs8b0AodnVvbf_m_w3hwQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

Gavin Mogan
Why transfer it at all? Why not clone, create the new repo, then push.

That would break the fork linkage, and be less complicated.

Probably a little slower but doesn't need to be realtime speeds

On Wed., Aug. 28, 2019, 9:03 a.m. Slide, <[hidden email]> wrote:

On Wed, Aug 28, 2019 at 8:59 AM Oleg Nenashev <[hidden email]> wrote:
 the requester would initiate a repository transfer request on Github

Note that it used to require some additional automation logic, because a contributor cannot just move a project to jenkinsci.
It has to happen through an intermediate organization like https://github.com/jenkinsci-transfer we use now.

I need to test whether there is a transfer request feature in GitHub and whether we can automate the bot somehow. If so, this is perfect


Correct, the transfer request is initiated by someone with access on the origin repository side, but the request has to be authorized by the receiving organization. The automation of the transfer request acceptance is definitely something that needs to be figured out.

 
 

On Wednesday, August 28, 2019 at 5:16:04 PM UTC+2, Matt Sicker wrote:
Sounds like a good idea.

On Tue, Aug 27, 2019 at 12:03 PM 'Gavin Mogan' via Jenkins Developers
<[hidden email]> wrote:

>
> +1
> I like the idea of not having to contact support to break the link
>
>
> On Tue, Aug 27, 2019 at 10:01 AM Slide <[hidden email]> wrote:
>>
>> Based on some feedback from various people during plugin hosting requests, our current method of forking and renaming repositories is not as desirable as one might hope. I am thinking of creating a JEP to change the process, but wanted to solicit some feedback before I do so. I would like to propose that the process be changed as follows:
>>
>> 1) Person/Org submits request to the HOSTING project, but the New Repository Name field is removed.
>> 2) The normal checks occur, however, now the originating repository name must follow the rules that we normally used for New Repository Name (e.g., if a plugin it must end in -plugin, no camelcase, etc).
>> 3) Once the plugin has has completed the review process as it does now (automated checker and human review) the requester would initiate a repository transfer request on Github
>> 4) Once the transfer request has been submitted, the ircbot would be updated such that the "host" command would accept the transfer and setup the teams on the repository to complete the transfer.
>>
>> This would remove the need for users to break the relationship between the originating repository and the jenkinsci repository (which would become the canonical repository).
>>
>> Please let me know your thoughts on this process change idea. If it has good feedback, I'll submit a JEP to document the process.
>>
>> --
>> Website: 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/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%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/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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/a9f09d9d-7c03-4610-993d-c5a448134192%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/CAPiUgVea1oZG7yWsAwjbEUyz1HOWMfs8b0AodnVvbf_m_w3hwQ%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/CAG%3D_DuuhTKg%3D2i25eZ3a7rZrHm4kgQ7hTWOyVOMKPpXibDBSEA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

slide


On Wed, Aug 28, 2019 at 9:31 AM 'Gavin Mogan' via Jenkins Developers <[hidden email]> wrote:
Why transfer it at all? Why not clone, create the new repo, then push.

That would break the fork linkage, and be less complicated.

Probably a little slower but doesn't need to be realtime speeds

That is another option. That would require the ircbot that completes the hosting request to have git capabilities in its container to clone the originating repo and push to the newly created repo. That is not unreasonable, it may be more complex to make sure all steps work all of the time.

 

On Wed., Aug. 28, 2019, 9:03 a.m. Slide, <[hidden email]> wrote:

On Wed, Aug 28, 2019 at 8:59 AM Oleg Nenashev <[hidden email]> wrote:
 the requester would initiate a repository transfer request on Github

Note that it used to require some additional automation logic, because a contributor cannot just move a project to jenkinsci.
It has to happen through an intermediate organization like https://github.com/jenkinsci-transfer we use now.

I need to test whether there is a transfer request feature in GitHub and whether we can automate the bot somehow. If so, this is perfect


Correct, the transfer request is initiated by someone with access on the origin repository side, but the request has to be authorized by the receiving organization. The automation of the transfer request acceptance is definitely something that needs to be figured out.

 
 

On Wednesday, August 28, 2019 at 5:16:04 PM UTC+2, Matt Sicker wrote:
Sounds like a good idea.

On Tue, Aug 27, 2019 at 12:03 PM 'Gavin Mogan' via Jenkins Developers
<[hidden email]> wrote:

>
> +1
> I like the idea of not having to contact support to break the link
>
>
> On Tue, Aug 27, 2019 at 10:01 AM Slide <[hidden email]> wrote:
>>
>> Based on some feedback from various people during plugin hosting requests, our current method of forking and renaming repositories is not as desirable as one might hope. I am thinking of creating a JEP to change the process, but wanted to solicit some feedback before I do so. I would like to propose that the process be changed as follows:
>>
>> 1) Person/Org submits request to the HOSTING project, but the New Repository Name field is removed.
>> 2) The normal checks occur, however, now the originating repository name must follow the rules that we normally used for New Repository Name (e.g., if a plugin it must end in -plugin, no camelcase, etc).
>> 3) Once the plugin has has completed the review process as it does now (automated checker and human review) the requester would initiate a repository transfer request on Github
>> 4) Once the transfer request has been submitted, the ircbot would be updated such that the "host" command would accept the transfer and setup the teams on the repository to complete the transfer.
>>
>> This would remove the need for users to break the relationship between the originating repository and the jenkinsci repository (which would become the canonical repository).
>>
>> Please let me know your thoughts on this process change idea. If it has good feedback, I'll submit a JEP to document the process.
>>
>> --
>> Website: 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/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%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/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
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/a9f09d9d-7c03-4610-993d-c5a448134192%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/CAPiUgVea1oZG7yWsAwjbEUyz1HOWMfs8b0AodnVvbf_m_w3hwQ%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/CAG%3D_DuuhTKg%3D2i25eZ3a7rZrHm4kgQ7hTWOyVOMKPpXibDBSEA%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/CAPiUgVeeS8BvK46bZ2SNds-CERS0XnTQ2WY1nELaVrX%3D%2BB%2Bmvg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

Jesse Glick-4
In reply to this post by Gavin Mogan
On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers
<[hidden email]> wrote:
> That would break the fork linkage

Which would be a downside I think. Also the current method forces you
to remember to delete your own account’s clone so the @jenkinsci one
does not appear as a fork of it.

Also you would lose any existing issues, PRs, etc.

The repository transfer operation seems like the most intuitive and
least problematic approach.

--
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/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

Gavin Mogan
> Which would be a downside I think.

Oh I thought that was the intention

Yea for sure a downside

On Wed, Aug 28, 2019 at 11:56 AM Jesse Glick <[hidden email]> wrote:
On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers
<[hidden email]> wrote:
> That would break the fork linkage

Which would be a downside I think. Also the current method forces you
to remember to delete your own account’s clone so the @jenkinsci one
does not appear as a fork of it.

Also you would lose any existing issues, PRs, etc.

The repository transfer operation seems like the most intuitive and
least problematic approach.

--
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/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%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/CAG%3D_DutDuG5o9bBrGwCX3-JvOkqzocb%3DqEFk8c%2BVwqN4kxvLVQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

Oleg Nenashev
As long as the transfer process is automated, +100 for that.
It should also help to avoid issues when contributor companies request hosting but then continue development in their own repos (no finger-pointing in this thread).

On Wednesday, August 28, 2019 at 8:58:13 PM UTC+2, Gavin Mogan wrote:
> Which would be a downside I think.

Oh I thought that was the intention

Yea for sure a downside

On Wed, Aug 28, 2019 at 11:56 AM Jesse Glick <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="OWlZMIk2BQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jgl...@...> wrote:
On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers
<<a href="javascript:" target="_blank" gdf-obfuscated-mailto="OWlZMIk2BQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com> wrote:
> That would break the fork linkage

Which would be a downside I think. Also the current method forces you
to remember to delete your own account’s clone so the @jenkinsci one
does not appear as a fork of it.

Also you would lose any existing issues, PRs, etc.

The repository transfer operation seems like the most intuitive and
least problematic approach.

--
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="OWlZMIk2BQAJ" 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/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%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/cc66f864-4acc-4cc0-b79f-71d918f3fe37%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Hosting process

Baptiste MATHUS
I am +1000 on the transfer goal, instead of forking.

I am quite bothered TBH by the immense amount of fork links that are still present on many (most?) plugins in our GH org. I believe that it sends quite a misleading message especially to new contributors.

We indeed need to be very careful and automate ideally everything, because to be allowed to transfer repo, AFAIR one needs to be admin. And in the past, we've had someone even *delete* the https://github.com/jenkinsci-transfer organization after the transfer had been done, thinking this was a one-off one...

On top of the fact PRs against forked repositories are simply ignored in one's statistics (granted, not everybody cares about this, but I think this can be important for some people, possibly more juniors, who want to join the pleasant and the useful to grow their résumé).

Le jeu. 29 août 2019 à 11:48, Oleg Nenashev <[hidden email]> a écrit :
As long as the transfer process is automated, +100 for that.
It should also help to avoid issues when contributor companies request hosting but then continue development in their own repos (no finger-pointing in this thread).

On Wednesday, August 28, 2019 at 8:58:13 PM UTC+2, Gavin Mogan wrote:
> Which would be a downside I think.

Oh I thought that was the intention

Yea for sure a downside

On Wed, Aug 28, 2019 at 11:56 AM Jesse Glick <[hidden email]> wrote:
On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers
<[hidden email]> wrote:
> That would break the fork linkage

Which would be a downside I think. Also the current method forces you
to remember to delete your own account’s clone so the @jenkinsci one
does not appear as a fork of it.

Also you would lose any existing issues, PRs, etc.

The repository transfer operation seems like the most intuitive and
least problematic approach.

--
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/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%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/cc66f864-4acc-4cc0-b79f-71d918f3fe37%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/CANWgJS6dOhyxLosHF78nGcas27okKPx2tjjno-E-5iYJ-M3Thw%40mail.gmail.com.