> 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


On Sun, Jun 6, 2021, at 6:49 PM, Oleg Nenashev wrote:
> 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).
> 
> 
> 
> 
> On Sunday, June 6, 2021 at 12:49:03 PM UTC+2 [email protected] wrote:
>> Hi,
>> 
>> I could help with some stuff before, during, and after the event, simply let 
>> me know what to do.
>> 
>> Thanks
>> El viernes, 4 de junio de 2021 a las 23:22:43 UTC+2, Oleg Nenashev escribió:
>>> Dear all,
>>> 
>>> As you know, we will be organizing the Jenkins contributor summit on June 
>>> 25th (landing page <https://www.jenkins.io/events/contributor-summit/>). 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 
>>> <https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit?usp=sharing>.
>>> 
>>> 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 
>>> <https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit?usp=sharing>.
>>> 
>>> Thanks for your time,
>>> Oleg Nenashev
>>> Acting Jenkins Events Officer
>>> 
> 

> -- 
> 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 [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/32b2d317-dd5c-4110-aeda-05ba8e23736en%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/32b2d317-dd5c-4110-aeda-05ba8e23736en%40googlegroups.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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ad20827f-6256-4f0b-b063-82c0d7f6c859%40www.fastmail.com.

Reply via email to