Jenkins Operator sub-project of Jenkins request

[Bartłomiej Antoniak]

Hi,

I'd like to request Jenkins Kubernetes Operator https://github.com/jenkinsci/kubernetes-operator to be added as Jenkins sub-project.

For VirtusLab, this is a strategic project, with dedicated team and long-term commitment. 

We are planning to join CD.Foundation projects portfolio, as well as establish general membership to bring some expertise in cloud-native CI/CD ecosystem.

Having Jenkins Operator part of Jenkins avoids legal and compliance work needed to join CD.Foundation.

Please let me know if there are any specific document/pull requests needed.

Regards,

Bartek

Email correspondence is considered personal data processing. Check out our Privacy Policy for details about the controller of your data and your rights according to GDPR/RODO.

--
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/207eb42e-e8e4-4fad-8786-fc45269beff7n%40googlegroups.com.

[Oleg Nenashev]

Hi Bartek,

Thanks for starting this thread! I am +1 for officially making Jenkins Kubernetes Operator an official sub-project. It is the current state anyway, so it just formalizes the current state.

I am still not sure how Jenkins subprojects and CDF projects align in this context. I doubt it is possible to be a Jenkins subproject and a separately listed Jenkins project at the same time. For example, Jenkins X has started as a Jenkins subproject and then it became independent project under the umbrella of the CDF. If I understand correctly, the same approach might be applied to the Jenkins Operator project.

Best regards,

Oleg

On Monday, March 1, 2021 at 4:21:34 PM UTC+1 [hidden email] wrote:

Hi,

I'd like to request Jenkins Kubernetes Operator https://github.com/jenkinsci/kubernetes-operator to be added as Jenkins sub-project.

For VirtusLab, this is a strategic project, with dedicated team and long-term commitment. 

We are planning to join CD.Foundation projects portfolio, as well as establish general membership to bring some expertise in cloud-native CI/CD ecosystem.

Having Jenkins Operator part of Jenkins avoids legal and compliance work needed to join CD.Foundation.

Please let me know if there are any specific document/pull requests needed.

Regards,

Bartek

--
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/a394d33d-2b73-417b-abb3-607c92f40bfbn%40googlegroups.com.

[Bartłomiej Antoniak]

Hi Oleg,

Thank you for your response. Indeed the project is already part of the jenkinsci org for some time, I'm glad we finally have a chance to formalize it :)

Correct, we'd like do it in the same way as Jenkins X and other projects. The Jenkins Operator will be listed as separate project in CDF portfolio. 

Regards,

Bartek

On Thu, Mar 4, 2021, 12:10 AM Oleg Nenashev <[hidden email]> wrote:

Hi Bartek,

Thanks for starting this thread! I am +1 for officially making Jenkins Kubernetes Operator an official sub-project. It is the current state anyway, so it just formalizes the current state.

I am still not sure how Jenkins subprojects and CDF projects align in this context. I doubt it is possible to be a Jenkins subproject and a separately listed Jenkins project at the same time. For example, Jenkins X has started as a Jenkins subproject and then it became independent project under the umbrella of the CDF. If I understand correctly, the same approach might be applied to the Jenkins Operator project.

Best regards,

Oleg

On Monday, March 1, 2021 at 4:21:34 PM UTC+1 [hidden email] wrote:

Hi,

I'd like to request Jenkins Kubernetes Operator https://github.com/jenkinsci/kubernetes-operator to be added as Jenkins sub-project.

For VirtusLab, this is a strategic project, with dedicated team and long-term commitment. 

We are planning to join CD.Foundation projects portfolio, as well as establish general membership to bring some expertise in cloud-native CI/CD ecosystem.

Having Jenkins Operator part of Jenkins avoids legal and compliance work needed to join CD.Foundation.

Please let me know if there are any specific document/pull requests needed.

Regards,

Bartek

--
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/a394d33d-2b73-417b-abb3-607c92f40bfbn%40googlegroups.com.

Email correspondence is considered personal data processing. Check out our Privacy Policy for details about the controller of your data and your rights according to GDPR/RODO.

--
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/CAEWeEB2T_11_MRiPijDxrnDJ-P9z27C0Ci7Dr%2Br%2Bj7Srfj54xQ%40mail.gmail.com.

[Bartłomiej Antoniak]

Hi,

I just wanted to thank you all for letting us being part of the community and finally formalised Jenkins Operator place as sub-project https://www.jenkins.io/projects/#jenkins-operator-for-kubernetes

We are happy to be more active in this space and align with overall Jenkins roadmap. Also, I'll do my best to join SIG meetings from time to time.

Regards,

Bartek

czwartek, 4 marca 2021 o 08:48:05 UTC+1 Bartłomiej Antoniak napisał(a):

Hi Oleg,

Thank you for your response. Indeed the project is already part of the jenkinsci org for some time, I'm glad we finally have a chance to formalize it :)

Correct, we'd like do it in the same way as Jenkins X and other projects. The Jenkins Operator will be listed as separate project in CDF portfolio. 

Regards,

Bartek

On Thu, Mar 4, 2021, 12:10 AM Oleg Nenashev <[hidden email]> wrote:

Hi Bartek,

Thanks for starting this thread! I am +1 for officially making Jenkins Kubernetes Operator an official sub-project. It is the current state anyway, so it just formalizes the current state.

I am still not sure how Jenkins subprojects and CDF projects align in this context. I doubt it is possible to be a Jenkins subproject and a separately listed Jenkins project at the same time. For example, Jenkins X has started as a Jenkins subproject and then it became independent project under the umbrella of the CDF. If I understand correctly, the same approach might be applied to the Jenkins Operator project.

Best regards,

Oleg

On Monday, March 1, 2021 at 4:21:34 PM UTC+1 [hidden email] wrote:

Hi,

I'd like to request Jenkins Kubernetes Operator https://github.com/jenkinsci/kubernetes-operator to be added as Jenkins sub-project.

For VirtusLab, this is a strategic project, with dedicated team and long-term commitment. 

We are planning to join CD.Foundation projects portfolio, as well as establish general membership to bring some expertise in cloud-native CI/CD ecosystem.

Having Jenkins Operator part of Jenkins avoids legal and compliance work needed to join CD.Foundation.

Please let me know if there are any specific document/pull requests needed.

Regards,

Bartek

--
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/a394d33d-2b73-417b-abb3-607c92f40bfbn%40googlegroups.com.

Email correspondence is considered personal data processing. Check out our Privacy Policy for details about the controller of your data and your rights according to GDPR/RODO.

Email correspondence is considered personal data processing. Check out our Privacy Policy for details about the controller of your data and your rights according to GDPR/RODO.

--
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/8b5567f3-1d8b-42a1-9539-6d4def3e0297n%40googlegroups.com.

[Oleg Nenashev]

Thanks for the jenkins.io update!

And let's keep working on the alignment, there are many opportunities. 

On Tuesday, March 23, 2021 at 3:52:55 PM UTC+1 [hidden email] wrote:

Hi,

I just wanted to thank you all for letting us being part of the community and finally formalised Jenkins Operator place as sub-project https://www.jenkins.io/projects/#jenkins-operator-for-kubernetes

We are happy to be more active in this space and align with overall Jenkins roadmap. Also, I'll do my best to join SIG meetings from time to time.

Regards,

Bartek

czwartek, 4 marca 2021 o 08:48:05 UTC+1 Bartłomiej Antoniak napisał(a):

Hi Oleg,

Thank you for your response. Indeed the project is already part of the jenkinsci org for some time, I'm glad we finally have a chance to formalize it :)

Correct, we'd like do it in the same way as Jenkins X and other projects. The Jenkins Operator will be listed as separate project in CDF portfolio. 

Regards,

Bartek

On Thu, Mar 4, 2021, 12:10 AM Oleg Nenashev <[hidden email]> wrote:

Hi Bartek,

Thanks for starting this thread! I am +1 for officially making Jenkins Kubernetes Operator an official sub-project. It is the current state anyway, so it just formalizes the current state.

I am still not sure how Jenkins subprojects and CDF projects align in this context. I doubt it is possible to be a Jenkins subproject and a separately listed Jenkins project at the same time. For example, Jenkins X has started as a Jenkins subproject and then it became independent project under the umbrella of the CDF. If I understand correctly, the same approach might be applied to the Jenkins Operator project.

Best regards,

Oleg

On Monday, March 1, 2021 at 4:21:34 PM UTC+1 [hidden email] wrote:

Hi,

I'd like to request Jenkins Kubernetes Operator https://github.com/jenkinsci/kubernetes-operator to be added as Jenkins sub-project.

For VirtusLab, this is a strategic project, with dedicated team and long-term commitment. 

We are planning to join CD.Foundation projects portfolio, as well as establish general membership to bring some expertise in cloud-native CI/CD ecosystem.

Having Jenkins Operator part of Jenkins avoids legal and compliance work needed to join CD.Foundation.

Please let me know if there are any specific document/pull requests needed.

Regards,

Bartek

--
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/a394d33d-2b73-417b-abb3-607c92f40bfbn%40googlegroups.com.

Email correspondence is considered personal data processing. Check out our Privacy Policy for details about the controller of your data and your rights according to GDPR/RODO.

--
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/8625baa7-2a53-44bc-9466-6bf9edf32048n%40googlegroups.com.