New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

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

New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Akram Ben Aissi
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





--

AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a style="color:rgb(0,136,206);font-size:11px;margin:0px" href="tel://+33631570860" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      


--
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Gavin Mogan
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





--

AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a style="color:rgb(0,136,206);font-size:11px;margin:0px" href="tel://+33631570860" target="_blank" rel="noreferrer">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      


--
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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_Duu%3Dng6-2NaTEKEKFNEXtm_zpdSYp%2BRuWkwkgsgVZJZrLw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Oleg Nenashev
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





--

AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a style="color:rgb(0,136,206);font-size:11px;margin:0px" href="tel://+33631570860" rel="noreferrer nofollow" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      


--
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3bcabfca-2083-400a-bc5e-4c91f68c55b2n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Oleg Nenashev
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





--

AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a style="color:rgb(0,136,206);font-size:11px;margin:0px" href="tel://+33631570860" rel="noreferrer nofollow" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      


--
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Mark Waite-2
+1 from me.

On Wed, Nov 11, 2020 at 1:38 PM Oleg Nenashev <[hidden email]> wrote:
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





--

AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a style="color:rgb(0,136,206);font-size:11px;margin:0px" href="tel://+33631570860" rel="noreferrer nofollow" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      


--
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%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/CAO49JtE9iwsJ2hfrj2Q0oO6ULJo1oL%2BrrOHO%3DeLUBJc_RQp4ig%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Ulli Hafner
+1 from me as well

Am 11.11.2020 um 21:41 schrieb Mark Waite <[hidden email]>:

+1 from me.

On Wed, Nov 11, 2020 at 1:38 PM Oleg Nenashev <[hidden email]> wrote:
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





-- 
AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a href="tel://+33631570860" rel="noreferrer nofollow" target="_blank" style="color: rgb(0, 136, 206); font-size: 11px; margin: 0px;" class="">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      



-- 
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%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/CAO49JtE9iwsJ2hfrj2Q0oO6ULJo1oL%2BrrOHO%3DeLUBJc_RQp4ig%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/F489D9B7-5D9F-437E-BDC4-00C11ABCD74A%40gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

slide
+1

On Wednesday, November 11, 2020 at 1:52:11 PM UTC-7 [hidden email] wrote:
+1 from me as well

Am 11.11.2020 um 21:41 schrieb Mark Waite <[hidden email]>:

+1 from me.

On Wed, Nov 11, 2020 at 1:38 PM Oleg Nenashev <[hidden email]> wrote:
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





-- 
AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a href="tel://+33631570860" rel="noreferrer nofollow" style="color:rgb(0,136,206);font-size:11px;margin:0px" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      



-- 
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%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].

--
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/cbf5ca2a-d09e-4e13-8044-1539bb2098e9n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Oleg Nenashev
I will create the new repository tomorrow if there is no negative feedback in this thread

On Wed, Nov 11, 2020 at 10:23 PM slide <[hidden email]> wrote:
+1

On Wednesday, November 11, 2020 at 1:52:11 PM UTC-7 [hidden email] wrote:
+1 from me as well

Am 11.11.2020 um 21:41 schrieb Mark Waite <[hidden email]>:

+1 from me.

On Wed, Nov 11, 2020 at 1:38 PM Oleg Nenashev <[hidden email]> wrote:
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





-- 
AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a href="tel://+33631570860" rel="noreferrer nofollow" style="color:rgb(0,136,206);font-size:11px;margin:0px" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      



-- 
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%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].

--
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/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cbf5ca2a-d09e-4e13-8044-1539bb2098e9n%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/CAPfivLD6tCHgUgmssMtww7T_nXD3K3-LVdik%3De8UmerO75m%2BsQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Victor Martinez
+1 That's brilliant! 

On Wednesday, 11 November 2020 at 22:20:41 UTC Oleg Nenashev wrote:
I will create the new repository tomorrow if there is no negative feedback in this thread

On Wed, Nov 11, 2020 at 10:23 PM slide <[hidden email]> wrote:
+1

On Wednesday, November 11, 2020 at 1:52:11 PM UTC-7 [hidden email] wrote:
+1 from me as well

Am 11.11.2020 um 21:41 schrieb Mark Waite <[hidden email]>:

+1 from me.

On Wed, Nov 11, 2020 at 1:38 PM Oleg Nenashev <[hidden email]> wrote:
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





-- 
AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a href="tel://+33631570860" rel="noreferrer nofollow" style="color:rgb(0,136,206);font-size:11px;margin:0px" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      



-- 
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%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].

--
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/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cbf5ca2a-d09e-4e13-8044-1539bb2098e9n%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/c922ce1f-6e67-4333-a634-12822bf8b3edn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

slide
Do we want them to go through the normal hosting process?

On Wed, Nov 11, 2020, 16:32 Victor Martinez <[hidden email]> wrote:
+1 That's brilliant! 

On Wednesday, 11 November 2020 at 22:20:41 UTC Oleg Nenashev wrote:
I will create the new repository tomorrow if there is no negative feedback in this thread

On Wed, Nov 11, 2020 at 10:23 PM slide <[hidden email]> wrote:
+1

On Wednesday, November 11, 2020 at 1:52:11 PM UTC-7 [hidden email] wrote:
+1 from me as well

Am 11.11.2020 um 21:41 schrieb Mark Waite <[hidden email]>:

+1 from me.

On Wed, Nov 11, 2020 at 1:38 PM Oleg Nenashev <[hidden email]> wrote:
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





-- 
AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a href="tel://+33631570860" rel="noreferrer nofollow noreferrer" style="color:rgb(0,136,206);font-size:11px;margin:0px" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      



-- 
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%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].

--
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/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cbf5ca2a-d09e-4e13-8044-1539bb2098e9n%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/c922ce1f-6e67-4333-a634-12822bf8b3edn%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/CAPiUgVc7uwJDHVxXb0AQVATC1vNrjUqZa3Wm6iQkY3rEWk6ZSg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Oleg Nenashev
> Do we want them to go through the normal hosting process?

Since this is a request for a new repo creation (not a fork/move) && there is a consensus here, I do not see a particular need. A HOSTING ticket would be useful to understand the desired permissions, but we can figure it out as we go.

I have created a repo here: https://github.com/jenkinsci/simple-jenkins-operator
Right now only Akram has access.



On Thursday, November 12, 2020 at 2:03:01 AM UTC+1 slide wrote:
Do we want them to go through the normal hosting process?

On Wed, Nov 11, 2020, 16:32 Victor Martinez <[hidden email]> wrote:
+1 That's brilliant! 

On Wednesday, 11 November 2020 at 22:20:41 UTC Oleg Nenashev wrote:
I will create the new repository tomorrow if there is no negative feedback in this thread

On Wed, Nov 11, 2020 at 10:23 PM slide <[hidden email]> wrote:
+1

On Wednesday, November 11, 2020 at 1:52:11 PM UTC-7 [hidden email] wrote:
+1 from me as well

Am 11.11.2020 um 21:41 schrieb Mark Waite <[hidden email]>:

+1 from me.

On Wed, Nov 11, 2020 at 1:38 PM Oleg Nenashev <[hidden email]> wrote:
Hi all, any additional feedback about the hosting request?

Thanks in advance,
Oleg

On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
It is me who asked for a developer mailing list thread. There is no problem with the hosting itself, I can create repos when there is a consensus. I asked for a more public process (not so many contributors watch HOSTING), because it is a follow-up to the Jenkins Kubernetes Operator: Open Governance Proposal that got stuck due to the lack of public response from Virtus Lab. As discussed at the governance board meetings in August and October, hosting a new operator is an alternative to getting the upstream https://github.com/jenkinsci/kubernetes-operator unblocked. So this request basically applies an alternate plan.
 
I am +1 for hosting a new operator, because I see no clear way for unblocking https://github.com/jenkinsci/kubernetes-operator. We got some private response from Virtus Lab to the Jenkins Board on Oct 16, but I have no permission to share it. Although this response is somewhat promising, it does not immediately unblocks contributions to the repository. There is no public response from Virtus Lab as they intended to do, and there is little activity in the repository. Although there is a declared intent to introduce changes in November, I am not sure it is . Having an alternate repository is how we could unblock contributors while we keep communicating with Virtus Lab and trying to unlock the upstream.

No strong opinion about naming

Best regards,
Oleg

On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [hidden email] wrote:
You need to open a hosting jira ticket.


And that'll create everything for you (repo, team, etc)


On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[hidden email]> wrote:
Hi Jenkins Devs,

I am delighted to announce the creation of a new Jenkins Operator for kubernetes under the name "Simple Jenkins Operator".
 
A kubernetes operator is kubernetes native component that is able to install, manage and operate applications running in kubernetes.

Hence, the Simple Jenkins Operator will provide a simple and straightforward experience to allow installation, management, upgrade and backup of Jenkins when it is running in kubernetes.

This projects comes into an alternative to the first Jenkins Operator namely jenkinsci/kubernetes-operator and aims to provide a simpler user experience by using more kubernetes native component.

Our first version will be 0.7.0 and will be compatible with operator-sdk 1.0.1 .
Please, jenkins board member, could you please create a repository named (jenkinsci/simple-jenkins-operator) so we can push our existing code base there.

Of course, contributions are welcome, and we really want an open govervnance for the very start, so any individual or enterprise contributor is welcome.

greetings





-- 
AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER


M: <a href="tel://+33631570860" rel="noreferrer nofollow noreferrer" style="color:rgb(0,136,206);font-size:11px;margin:0px" target="_blank">+33.6.31.57.08.60       T: @akrambenaissi

E: [hidden email]    #: Akram      



-- 
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/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%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/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%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].

--
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/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cbf5ca2a-d09e-4e13-8044-1539bb2098e9n%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].

--
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/727abc75-84d1-437b-ba59-276bd3614429n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Daniel Beck-2


On Thu, Nov 12, 2020 at 12:07 PM Oleg Nenashev <[hidden email]> wrote:
Since this is a request for a new repo creation (not a fork/move) && there is a consensus here, I do not see a particular need. A HOSTING ticket would be useful to understand the desired permissions, but we can figure it out as we go.

So are you saying that anyone can circumvent hosting processes by asking for a new repo "to push existing code"? Because that's what I'm hearing.

(FWIW we stopped doing this several years ago because we customize repos in the ircbot code, set up permissions – which you've already noticed is a problem now – and apply some other custom defaults. Plus having empty repos around that never got populated for months or years is also not great.) 

--
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/CAMo7Pt%2BtmogApuyJkNET8gmV0sr8%2Bs3og3x8NSw%3DJrV3o7CAPg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Oleg Nenashev
Hi Daniel,

I agree that I bypassed a few steps in the Hosting process for this repo.
I am happy to discuss why in another channel, but please be sure it is not about "anyone".
If you or other Hosting team members want me to revert my actions, I will do so.

Best regards,
Oleg


On Thu, Nov 12, 2020 at 1:34 PM Daniel Beck <[hidden email]> wrote:


On Thu, Nov 12, 2020 at 12:07 PM Oleg Nenashev <[hidden email]> wrote:
Since this is a request for a new repo creation (not a fork/move) && there is a consensus here, I do not see a particular need. A HOSTING ticket would be useful to understand the desired permissions, but we can figure it out as we go.

So are you saying that anyone can circumvent hosting processes by asking for a new repo "to push existing code"? Because that's what I'm hearing.

(FWIW we stopped doing this several years ago because we customize repos in the ircbot code, set up permissions – which you've already noticed is a problem now – and apply some other custom defaults. Plus having empty repos around that never got populated for months or years is also not great.) 

--
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/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BtmogApuyJkNET8gmV0sr8%2Bs3og3x8NSw%3DJrV3o7CAPg%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/CAPfivLAh-myF7iCMTod%3D5xAa63V%3DYN22ZSRW2GsqaA0VTrVS8w%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Oleg Nenashev
Hi Akram,

I have noticed that the repo was renamed to https://github.com/jenkinsci/jenkins-automation-operator . We briefly discussed the potential renaming at the previous Cloud Native SIG meeting, but AFAICT there was no finalized decision.  Although the maintainers have admin permissions and can rename repos, naming agreements are a part of the hosting process.  So it would be great to agree on the name here.

The code has not been pushed there yet as well. I highlighted this issue to Vibhav at the last Cloud Native SIG meeting on Nov 20, and IIUC there was a plan to move the code to the new upstream shortly. 

P.S: It highlights the importance of the formal hosting process. Although it does not prevent from all issues, it helps to ensure that everyone is on the same page.

BR, Oleg
On Thursday, November 12, 2020 at 2:22:42 PM UTC+1 Oleg Nenashev wrote:
Hi Daniel,

I agree that I bypassed a few steps in the Hosting process for this repo.
I am happy to discuss why in another channel, but please be sure it is not about "anyone".
If you or other Hosting team members want me to revert my actions, I will do so.

Best regards,
Oleg


On Thu, Nov 12, 2020 at 1:34 PM Daniel Beck <[hidden email]> wrote:


On Thu, Nov 12, 2020 at 12:07 PM Oleg Nenashev <[hidden email]> wrote:
Since this is a request for a new repo creation (not a fork/move) && there is a consensus here, I do not see a particular need. A HOSTING ticket would be useful to understand the desired permissions, but we can figure it out as we go.

So are you saying that anyone can circumvent hosting processes by asking for a new repo "to push existing code"? Because that's what I'm hearing.

(FWIW we stopped doing this several years ago because we customize repos in the ircbot code, set up permissions – which you've already noticed is a problem now – and apply some other custom defaults. Plus having empty repos around that never got populated for months or years is also not great.) 

--
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/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].

--
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/94d497ad-fca6-44f7-bdd5-79f3f84a4557n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Akram Ben Aissi
Hi Oleg et all,

sorry, this was a mistake. We were thinking of another name but despite not reaching a consensus there was a misunderstanding and one of the team member renamed it.
I just reverted the name to the original one and notified all the team members.


On Tuesday, December 1, 2020 at 10:15:55 AM UTC+1 Oleg Nenashev wrote:
Hi Akram,

I have noticed that the repo was renamed to https://github.com/jenkinsci/jenkins-automation-operator . We briefly discussed the potential renaming at the previous Cloud Native SIG meeting, but AFAICT there was no finalized decision.  Although the maintainers have admin permissions and can rename repos, naming agreements are a part of the hosting process.  So it would be great to agree on the name here.

The code has not been pushed there yet as well. I highlighted this issue to Vibhav at the last Cloud Native SIG meeting on Nov 20, and IIUC there was a plan to move the code to the new upstream shortly. 

P.S: It highlights the importance of the formal hosting process. Although it does not prevent from all issues, it helps to ensure that everyone is on the same page.

BR, Oleg
On Thursday, November 12, 2020 at 2:22:42 PM UTC+1 Oleg Nenashev wrote:
Hi Daniel,

I agree that I bypassed a few steps in the Hosting process for this repo.
I am happy to discuss why in another channel, but please be sure it is not about "anyone".
If you or other Hosting team members want me to revert my actions, I will do so.

Best regards,
Oleg


On Thu, Nov 12, 2020 at 1:34 PM Daniel Beck <[hidden email]> wrote:


On Thu, Nov 12, 2020 at 12:07 PM Oleg Nenashev <[hidden email]> wrote:
Since this is a request for a new repo creation (not a fork/move) && there is a consensus here, I do not see a particular need. A HOSTING ticket would be useful to understand the desired permissions, but we can figure it out as we go.

So are you saying that anyone can circumvent hosting processes by asking for a new repo "to push existing code"? Because that's what I'm hearing.

(FWIW we stopped doing this several years ago because we customize repos in the ircbot code, set up permissions – which you've already noticed is a problem now – and apply some other custom defaults. Plus having empty repos around that never got populated for months or years is also not great.) 

--
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/oAWCXDbgcG4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].

--
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/3095285c-29a7-4bc9-b452-393a47aeff2en%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

Akram Ben Aissi
Hi Jenkinsers,

after discussions, our team has agreed in using a different name instead of simple-jenkins-operator which may be too restrictive.

We conducted a poll internally and it seems that we have a consensus around "jenkins-automation-operator" .
Could you please, folks, consider that change and give any feedback?

After that, please let us know about the change. At the moment, we haven't pushed any code yet, and we have still our code base in a public github repository.

Greetings
Akram




--
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/d0c49b4d-b52d-4618-9e41-3027075ec2c0n%40googlegroups.com.