HELP NEEDED - Jenkins contributor summit on Jun 25

[Oleg Nenashev]

Dear all,

As you know, we will be organizing the Jenkins contributor summit on June 25th (landing page). I would like to make it a quite big contributor event where we agree on some key Jenkins topics, e.g. security or API/plugin deprecation/EoL policy. There is also interest in contributing onboarding events and to have joint sessions focused on interoperability and on end user experiences.Full coordination document.

The event is in 3 weeks. The preparation was delayed by some professional and personal events, and also the increased GSoC workload. There are a few contributors who planned to dedicate time to help with hosting the event, but unfortunately they will not be able to dedicate enough time. If we want to organize a decent event, more organizers are needed! Beow you can find several activities where help is needed,

Before the summit:

• Finalizing the agenda
• Coordinating the schedule with presenters
• Finalizing the end users presentation agenda
• Getting the event promoted in the community channels
• Working with@Alyssa Tong and the CDF to deliver swag to key summit contributors
  
• Facilitating conversations
• Coordinating hosting of the newcomer track. IIUC Mark will be no longer able to drive that as we discussed with him initially

During the event:

• Hosting / Moderating the event
• Moderating the breakout rooms
• Speaking about projects, SIGs and their statuses
  

After the event:

• Processing and publishing recordings
• Writing a summary blogpost
• Swag logistics
• Capturing follow-ups on the Jenkins roadmap, creating follow-up tasks
  

Please respond to this thread if you would be willing to dedicate some time and to contribute to the event.Please feel free to comment and suggest changes in the.coordination document.

Thanks for your time,

Oleg Nenashev

Acting Jenkins Events Officer

[Olblak]

Hi Oleg,

Thanks for starting this discussion, as a first step, I would like to help with finalizing the agenda.

My understanding is, we need validation from the different speakers (once we agree on the agenda).

Is this right?

If I understand correctly the big picture of the day would be something like.

Project Update from

 1. Board member and officer

 2. Sub-project or SIG

 3. Round Table on specific initiatives that we want to see coming. For instance, in your documentation you highlighted things such as Java 17, Jenkins&Tekton, maybe other people have topic suggestions as well. 

Regarding event capacity,  inside the document, It's mentioned that we expect 300participants.

Do we already have a better estimation of how many people registered for the contributor summit?

I guess the closest we'll be to the event and bigger that number will be and I worry to use Zoom for that.

During the event, I'll be available to help moderate talks.

Cheers

--

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-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCdZ51%3Dztvq%3DqOrB9KL8dAZSo3QQE_%2BvqEEoBVRZwomuQ%40mail.gmail.com.

[Carlos Tadeu Panato Jr]

Hello Oleg and Olivier

I would like to help as, how do I can get started?

thanks!

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b3d60935-5b40-4632-9e7a-7eee48b1d76c%40www.fastmail.com.

[Ivan Fernandez Calvo]

Hi,

I could help with some stuff before, during, and after the event, simply let me know what to do.

Thanks

[Oleg Nenashev]

Hi all, thanks for the interest and feedback! Any contributions will be appreciated. I started a Doodle for the first coordination call, please vote for the slots here: https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll&utm_medium=link

Answers below:

> I would like to help as, how do I can get started?

> I could help with some stuff before, during, and after the event, simply let me know what to do.

Lemme work on that. I could create a GitHub repo with issues for picking up.

It can be a quite good way for onboarding of new event contributors. What do you think?

> My understanding is, we need validation from the different speakers (once we agree on the agenda). Is this right?

Yes, we need to build the schedule and to confirm the timeslots. Will start a Google Sheet or a Google Calendar for it.

> If I understand correctly the big picture of the day would be something like...

Yes. More fine grain plan is in the Google Doc

> Regarding event capacity,  inside the document, It's mentioned that we expect 300participants. ...  I guess the closest we'll be to the event and bigger that number will be and I worry to use Zoom for that.

300 is the maximum expectation based on what we can host in Zoom. Actually the current limit is 500 for Zoom Webinar if we ditch the interactive part in the opening. We can also broadcast to YouTube if needed.

 > Do we already have a better estimation of how many people registered for the contributor summit?

According to the CDF, currently we have about 700 registrations. Do not hold your breadth, the show up rate is likely to be low (4th day of cdCon and the specific agenda).

[Olblak]

Lemme work on that. I could create a GitHub repo with issues for picking up.

It can be a quite good way for onboarding of new event contributors. What do you think?

I wouldn't bother with that.

CDcon is in three weeks so we have two weeks to prepare for the contributor summit.

Let stick to the google document and maybe create a google sheet to work on the schedule.

I think at this stage the best way to help is to either propose topics that should be covered and identify the correct person to lead those topics.

I would be interested to know from RedHat and VirtusLab their vision on the Jenkins operator.

I would be interested to know how to prepare next Jenkins (online) meetup. What people learned about running online event, etc...

I would be interested to have a session on "howto" contribute to Jenkins, targeting new contributors and that would also be a good opportunity to have interactive session. 

I started a Doodle for the first coordination call, please vote for the slots here: https://doodle.com/poll/wsrfhzhm79xcgi2y?utm_source=poll&utm_medium=link

Thank you for the poll, you were faster than me :D

Yes, we need to build the schedule and to confirm the timeslots. Will start a Google Sheet or a Google Calendar for it.

Let me handle that, and I'll put a link to the google document

--

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-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/32b2d317-dd5c-4110-aeda-05ba8e23736en%40googlegroups.com.

[Olblak]

Hi Everybody,

I started a draft for the Contributor summit schedule.

https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0

Feel free to comment if

- A specific session should or should not be present.

- A timeslot allocated to a specific session is too long or too short

- You know a good person of contact for each session

- Anything that you may think of :)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ad20827f-6256-4f0b-b063-82c0d7f6c859%40www.fastmail.com.

[Oleg Nenashev]

Thanks to Olivier for the contributions and willing to help! Based on the feedback in the voting poll, I created a meeting on Thursday, 1PM UTC. At this meeting we will agree on the agenda and split the organization/moderation tasks. Everyone is welcome to participate, and I will also try to record this meeting.

Links:

* [Calendar Link](https://calendar.google.com/event?action=TEMPLATE&tmeid=NzJqczZjZjY1ZDBrYnU1dTk3amowdjEycHMgNHNzMTJmMG1xcjN0YnAxdDJmZTM2OXNsZjRAZw&tmsrc=4ss12f0mqr3tbp1t2fe369slf4%40group.calendar.google.com)
* Zoom: [https://zoom.us/j/92075127451](https://www.google.com/url?q=https://zoom.us/j/92075127451&sa=D&source=calendar&usd=2&usg=AOvVaw0vmVjHpVhjIfQltFhxiNL8)
* [Coordination doc](https://www.google.com/url?q=https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit?usp%3Dsharing&sa=D&source=calendar&usd=2&usg=AOvVaw1CixKPCaFPv2WOYUWlY14h)
* [Contributor Summit Schedule](https://www.google.com/url?q=https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit?usp%3Dsharing&sa=D&source=calendar&usd=2&usg=AOvVaw2OIj6N3yj8cCjKP5YpNUSC)
* [Event landing page](https://www.google.com/url?q=https://www.jenkins.io/events/contributor-summit/&sa=D&source=calendar&usd=2&usg=AOvVaw3INLbGY58ZLcGoCUXTX7iy)

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/n_3LkSgt0w0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b186800c-ea43-47db-8333-d43dac0c516d%40www.fastmail.com.

[Olblak]

Thanks, Oleg for driving this.

Yesterday, Mark suggested to me to move the contributor track as early as possible to have as many people from AMER and EMEA in an interactive session.

This an idea that I like very much and I would like to discuss it tomorrow. 

So we would have "project update", "contributor track", "SIG update", "CDF project collaboration" as I am suggesting in the google sheet.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAuVq6eReV14bnHNvs2R_t9-TLbJDVaSzcfBVdnX2perA%40mail.gmail.com.

[Kara de la Marck]

Hi all,

Thank you for organizing the Contributor Summit and its schedule, Oleg and Olivier. 

I'm very happy to lead on the Cloud Native track to ensure that we have a speaker to summarize recent highlights in the Cloud Native SIG; ideally, this would be an active community member.  

Please note that the time as currently scheduled will be too late for our Cloud Native SIG participants and contributors in India (and APAC generally). 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/fcf33eef-07f4-4d0d-a941-a251530b63e4%40www.fastmail.com.

[Oleg Nenashev]

Hi Kara,

Thanks for the feedback and for helping with the Cloud Native SIG! I understand the timezones are imperfect. Apart from moving a meeting to an earlier slot, we have an option to do the Cloud Native SIG meeting on Saturday, Jun 26.

I can host meetings if they are after 4AM UTC. Maybe Rick or Himandri would be also available.

BR, Oleg

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BSgUiyiVBThKuP_kacpKtJ23MOUhk2V2qwCbf-uOwqvNdLC_g%40mail.gmail.com.

[Kara de la Marck]

Thanks for your suggestion, Oleg!

It's likely better for us to keep all the updates together for the Contributors Summit, that way they will be easier to consume for all interested parties.

Would it be possible for a contributor who can't make it on the 25th to record an update on behalf of a SIG or track?  And that this pre-recorded update would be shown during the allocated time on the 25th?

 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCPaRv9_dmP_0SiryBtme6RC3VNRF_40zUo_EVUwsJ%2BWQ%40mail.gmail.com.

[Baptiste Mathus]

I'm sorry to be so late on this... I am going to write here for visibility, and I'll also add or see to add it correctly the sheet initiated by Oleg.

1. I would like to help facilitate a conversation on Guava upgrade in Jenkins Core.

As you know, this work is already somehow started. I'd like us to take the summit opportunity to decide on next steps, approaches.

Our team at CloudBees is committed to help on this subject.

2. Plugin EOL policy // plugin maintenance status

I think these two subjects would serve us as a community to keep moving Jenkins forward.

For the commons-digester:2.1 recent removal for instance, I think we spent a subtantial amount of effort on plugins nobody should use anymore since a long time.

If we had had such a policy, we could have saved a lot of energy together.

3. Company/team ownership for plugins

As an ex-HOSTING team member and a contributor since a few years, I think we need to have a clearer stance for companies to implement a Jenkins plugin for their software.

It happens regularly than a company, not intimate with the Jenkins Project's governance, will request commit access to a plugin they think they own somehow. (e.g. HOSTING-901, HOSTING-346, HOSTING-288, HOSTING-134, and we could go on)

Only then they discover that from the Jenkins Project's standpoint, they do not exist. An ex-employee that may have even left a given company could disagree to let commit rights go and they would be entitled to this (fortunately didn't happen yet, to my knowledge).

The other case I've got in mind is the "team" concept. That's the one I'm most interested in personally. For example, when people move between teams in our company etc., we usually need to update many files in RPU and request commit access in various repositories.

If we could have an official concept for teams within the Jenkins Project, I think we could set up special GH teams (for example one for ours at CloudBees) + create possibly such a concept for it inside RPU to define this only once.

I think this is already doable (we already have the core team within GH e.g.), and we could request an ad-hoc implementation and move on. But I think there's merit in defining something generalized for the Jenkins Project's governance.

Thanks for reading :). I definitely didn't plan to send such a long email.

Have a great weeked everyone.   

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BSgUizk9b%2B8EyHrSNLqODiWBSXR2f5KhASa-LdBwBZ0wRFFqA%40mail.gmail.com.

[Olblak]

Hi Everybody,

I think I am wrong since the beginning while working on the contributor summit agenda. :(

Is the contributor summit supposed to start at 9AM PDT or 9AM EDT? 

This is "slightly" different for session that would benefit from folks from EU and US west coast

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS40pDAPs%3DtdbBh02-nB-Yj-Mq3Xn1u1CR8Cj4%3DjMR2dfg%40mail.gmail.com.

[Oleg Nenashev]

I think we can schedule it as we wish, we just need to announce it timely. East Coast 9am is my strong preference

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ace47ebc-7e1e-49fc-ac28-45f4c122af4a%40www.fastmail.com.

[Tim Jacomb]

If its east coast 9am I can help more / attend some sessions :)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAG5GcMpn-gK9mZjnxyNP86k%3DkyBR-mF1r-_B7qdFOF9w%40mail.gmail.com.

[Olblak]

Same here, it makes the schedule easier from EU :p

Because of the PDT timezone, I was thinking of the following topic order

1. Project update

2. Contributor track, as this part heavily require participation from attendees

3. SIG  update

followed by all presentations such as unconference,etc.

If we are on EDT, then it would make sense to swap Contributor track and SIG update so

1. Project Update

2. SIG Update <- Seems more logical in terms of timeline

3. Contributor Track <- This would be easier for folks from US West coast to participate

 to the contributor track.

I am curious what people from APAC would prefer?

Again based on all the discussion I am having, I am still trying to  draft schedule here

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BickiKhACxMUdH_cqTDg%2Bv8KQPgMh%3Dx44kDGMahmfoGzgg%40mail.gmail.com.

[Bartłomiej Antoniak]

Hi all,

I'm happy to take over Jenkins Kubernetes Operator part. The initial idea was to present high-level update and further plans during opening session. 

Then reserve a breakout session for the deep dive to particular topics and longer discussion if needed.

Regards,

Bartek

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/247fd121-0f92-4d29-a52b-95b30d80e065%40www.fastmail.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.

[Olblak]

Hi Bartłomiej,

That would be really great. 

Vibhav is interested to present initiatives from the Coud Native SIG, maybe you could sync with him for that part

The sig update is around 10min max and then we have more time in a later session to go deeper on the jenkins kubernetes operator.

I am adding your name on the schedule for the longer session, do you already have an idea of how long you need?

Would 30 min work for you?

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEWeEB1zn--b-_r46SopJ2qsr1OY0fZoiKC2dwzJNkYQXs%2BAMQ%40mail.gmail.com.

[Oleg Nenashev]

Hi all,

I have created the #jenkins-contributor-summit channel in the Continuous Delivery Foundation Slack workspace. Anyone is welcome to join and participate in the organization, planning, and async conversation. How to join the CDF Slack. I have also restructured the agenda in the coordination doc based on the discussion we had last week. Landing page update: https://github.com/jenkins-infra/jenkins.io/pull/4429

On my availability: Sadly, I cannot commit on my availability during, before or after the summit. The Jenkins governance board and officers are informed about the situation. Personal emergency. I will do my best to help where I can and to prepare the State of the Union session. Will try to deliver on other action items like end user panel. Olivier Vernin will be taking over the overall summit coordination, together with other org team members. Thanks a lot to Olivier! As always, everyone is invited to participate and contribute! How to help?

On Kubernetes operator. Based on the separate conversation with Bartek, I have added the breakout session of the operator. We also expect a short 5-10min update during the State of The Union in the beginning of the summit.

Best regards,

Oleg

[Olblak]

Due to personal reasons, I won't be available for the contributor summit.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/61d6df62-20c7-4f1f-87f2-8d4f17b14dcfn%40googlegroups.com.

[Vibhav Bobade]

Hi team, Olblak,

That sounds like a good idea. @BartlomieJ I am available on the continuous delivery foundation slack if you would like to plan out the session. I will PM you there for now then, we can take it from there.

Regards,

Vibhav

[Bartłomiej Antoniak]

Hi,

Sure, let's catch up there and discuss further plan. 

Regards,

Bartek

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAABsqpDn8q9hkMMmTmpGKLQZF%2Bfgxov-fxCe1ZeprdtMxHj-ag%40mail.gmail.com.

[Oleg Nenashev]

Hi all,

I have also shared the draft opening and State of the Union slidedeck here. All Jenkins Board members and officers should have access now. Ping me to get permissions if you want to contribute and get access!

Current plan draft is here:

Best regards,

Oleg

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEWeEB3%3DFYJVEMhCVJR1fhf8-6LezsBFnmrDxY4eSwGtovyGUA%40mail.gmail.com.