Hi all,

I started a Doodle for the initial meeting: 
https://doodle.com/poll/4p3ureaxuscvwgi7. It would be great to have the 
meeting next week so that we have initial discussion between volunteers 
about the next steps. After that we could setup regular SIG meetings in 
June.

I have also drafted a new meeting agenda doc 
<https://docs.google.com/document/d/13zeaKgtud5jZ5RqZEh1lrwjDXJRm7j31scPymlrMpfo/edit?usp=sharing>,
 
and added a few items for the discussion:

   - Cloud Native SIG 2.0 - Defining areas of interest (see the original 
   message)
   - Founding projects.Some projects (Jenkins Kubernetes Operator, 
   Jenkinsfile Runner) can be moved from the previous SIG edition, but we may 
   want to revisit the scope
   - Jenkins Kubernetes Operator - Online meetup follow-ups && how could we 
   help the project (features needed in upstream components, etc.)?

Please vote in Doodle and add your topics to the agenda!

Best regards,
Oleg



On Friday, May 15, 2020 at 6:49:04 PM UTC+2, Sumit Sarin wrote:
>
> Hi Oleg!
> Tremendously excited for this. And after completion of work on the 
> External Fingerprint Storage, looking forward to contribute to all the 
> other exciting projects you mentioned! :)
>
> Thanks and Regards,
> Sumit
>
> On Friday, 15 May 2020 10:31:43 UTC+5:30, Sladyn Nunes wrote:
>>
>> I agree , there are quite a few integration possibilities with CNCF 
>> projects, and various other cloud focused initiatives could be undertaken. 
>> Count me in. +1
>>
>>
>> On Fri, May 15, 2020, 5:12 AM Vlad Silverman <vsilv...@gmail.com> wrote:
>>
>>> I would be glad contributing to this as well
>>>
>>> On May 14, 2020, at 3:06 PM, Marky Jackson <marky....@gmail.com> wrote:
>>>
>>> I whole heartily support this and please count me in to do whatever is 
>>> needed.
>>>
>>> On May 14, 2020, at 2:39 PM, Oleg Nenashev <o.v.n...@gmail.com> wrote:
>>>
>>> 
>>> Hi all,
>>>
>>> The Jenkins Cloud Native special interest group 
>>> <https://jenkins.io/sigs/cloud-native/> has been dormant for about a 
>>> year since the offline meeting at Kubecon 2019 in Barcelona. There is a lot 
>>> of interest from the users about running Jenkins in cloud environments and, 
>>> specifically, in Kubernetes. We have recently started a series of "Jenkins 
>>> in Kubernetes" online meetups 
>>> <https://www.meetup.com/Jenkins-online-meetup/>, and we got positive 
>>> feedback and many follow-ups there. It would be great if we could recover 
>>> the SIG.
>>>
>>> Previously the SIG was mostly focused on the deep Jenkins architecture 
>>> changes, including pluggable storage and architecture changes towards 
>>> stateless Jenkins. This is definitely a valiant goal which should be worked 
>>> on, but for the SIG it was a challenge to consolidate a critical mass of 
>>> contributors to push such deep surgery changes forward. I hope that we will 
>>> eventually get there, but the SIG format did not work well.
>>>
>>> I would suggest to change the scope of the SIG and to refocus it on 
>>> use-cases for Jenkins end users and administrators:
>>>
>>>    - Integrations with Kubernetes and other projects from the CNCF 
>>>    landscape
>>>    - Managing Jenkins in Kubernetes: Helm charts, Jenkins operator, 
>>>    monitoring with Prometheus, etc.
>>>    - Jenkins on Cloud providers (AWS, Google Cloud, Azure, etc): 
>>>    Provisioning of agents, cloud storage, and other common use-cases
>>>    - Jenkins FaaS Capabilities: Jenkinsfile Runner and similar engines
>>>    - Integrations with cloud native CI/CD engines like Tekton and 
>>>    Jenkins X
>>>    
>>>
>>> Immediate projects the SIG would focus on: Kubernetes plugin ecosystem, 
>>> Jenkins Kubernetes Operator (JEP-219), Jenkinsfile Runner, External 
>>> Fingerprint Storage (GSoC 2020 project), "Jenkins on Kubernetes" meetup 
>>> follow-up discussions with speakers. We could add more projects if there 
>>> are active initiatives there and put them on the Jenkins roadmap 
>>> <https://www.jenkins.io/project/roadmap/>.
>>>
>>> What do you think? I would appreciate any feedback and comments. If 
>>> there are multiple contributors interested, I am ready to go ahead and get 
>>> the SIG running again.
>>>
>>> Thanks for your feedback,
>>> Oleg
>>>
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/168EC3AC-204F-4486-A776-8F999C058FDD%40gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/168EC3AC-204F-4486-A776-8F999C058FDD%40gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/6FF427E7-C776-41DF-BB8B-58639066F7B9%40gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/6FF427E7-C776-41DF-BB8B-58639066F7B9%40gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a9b8fa62-7f66-4b00-9272-240e31272578%40googlegroups.com.

Reply via email to