Due to personal reasons, I won't be available for the contributor summit.
On Sat, Jun 19, 2021, at 10:39 AM, Oleg Nenashev wrote: > 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 > <https://github.com/jenkins-infra/jenkins.io/blob/4ae597e83870f4e86475ecd702f0895acb5c5cdf/chat/#continuous-delivery-foundation>. > I have also restructured the agenda in the coordination doc > <https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit#heading=h.j46ljtvh5tfx> > 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? > <https://docs.google.com/document/d/1JVbWudREipEF5UJn-bBRU5QIjKf8mzFP9iFdwWbgFB0/edit#heading=h.4hqgkvihqtvc> > > *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 > > On Thursday, June 17, 2021 at 1:39:08 PM UTC+2 Olblak wrote: >> __ >> 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? >> >> >> >> On Thu, Jun 17, 2021, at 9:50 AM, 'Bartłomiej Antoniak' via Jenkins >> Developers wrote: >>> 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 >>> >>> śr., 16 cze 2021 o 13:28 'Olblak' via Jenkins Developers >>> <[email protected]> napisał(a): >>>> __ >>>> 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 >>>> <https://docs.google.com/spreadsheets/d/1k2xvtJVMwOTZjzCFlqaQpHlxJkiwS67VjNtnJN0ynXs/edit#gid=0> >>>> >>>> >>>> >>>> >>>> On Wed, Jun 16, 2021, at 12:34 PM, Tim Jacomb wrote: >>>>> If its east coast 9am I can help more / attend some sessions :) >>>>> >>>>> On Wed, 16 Jun 2021 at 11:02, Oleg Nenashev <[email protected]> wrote: >>>>>> I think we can schedule it as we wish, we just need to announce it >>>>>> timely. East Coast 9am is my strong preference >>>>>> >>>>>> On Wed, Jun 16, 2021, 11:53 'Olblak' via Jenkins Developers >>>>>> <[email protected]> wrote: >>>>>>> __ >>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> On Fri, Jun 11, 2021, at 9:46 PM, Baptiste Mathus wrote: >>>>>>>> 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. >>>>>>>> >>>>>>>> Le jeu. 10 juin 2021 à 14:27, Kara de la Marck >>>>>>>> <[email protected]> a écrit : >>>>>>>>> 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? >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jun 10, 2021 at 2:03 AM Oleg Nenashev <[email protected]> >>>>>>>>> wrote: >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Jun 9, 2021, 21:50 Kara de la Marck <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>>> 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). >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Jun 9, 2021 at 11:48 AM 'Olblak' via Jenkins Developers >>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>> __ >>>>>>>>>>>> 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. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Jun 9, 2021, at 6:45 AM, Oleg Nenashev wrote: >>>>>>>>>>>>> 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) >>>>>>>>>>>>> >>>>>>>>>>>>> <https://zoom.us/j/92075127451%5D(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) >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Jun 7, 2021 at 10:48 AM 'Olblak' via Jenkins Developers >>>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>>> __ >>>>>>>>>>>>>> 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 :) >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Jun 7, 2021, at 9:06 AM, 'Olblak' via Jenkins Developers >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/ad20827f-6256-4f0b-b063-82c0d7f6c859%40www.fastmail.com?utm_medium=email&utm_source=footer>. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> 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 [email protected]. >>>>>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/b186800c-ea43-47db-8333-d43dac0c516d%40www.fastmail.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/b186800c-ea43-47db-8333-d43dac0c516d%40www.fastmail.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/CAPfivLAuVq6eReV14bnHNvs2R_t9-TLbJDVaSzcfBVdnX2perA%40mail.gmail.com >>>>>>>>>>>>> >>>>>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAuVq6eReV14bnHNvs2R_t9-TLbJDVaSzcfBVdnX2perA%40mail.gmail.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/fcf33eef-07f4-4d0d-a941-a251530b63e4%40www.fastmail.com >>>>>>>>>>>> >>>>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/fcf33eef-07f4-4d0d-a941-a251530b63e4%40www.fastmail.com?utm_medium=email&utm_source=footer>. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> 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 >>>>>>>>>>> [email protected]. >>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BSgUiyiVBThKuP_kacpKtJ23MOUhk2V2qwCbf-uOwqvNdLC_g%40mail.gmail.com >>>>>>>>>>> >>>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BSgUiyiVBThKuP_kacpKtJ23MOUhk2V2qwCbf-uOwqvNdLC_g%40mail.gmail.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/CAPfivLCPaRv9_dmP_0SiryBtme6RC3VNRF_40zUo_EVUwsJ%2BWQ%40mail.gmail.com >>>>>>>>>> >>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCPaRv9_dmP_0SiryBtme6RC3VNRF_40zUo_EVUwsJ%2BWQ%40mail.gmail.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/CA%2BSgUizk9b%2B8EyHrSNLqODiWBSXR2f5KhASa-LdBwBZ0wRFFqA%40mail.gmail.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BSgUizk9b%2B8EyHrSNLqODiWBSXR2f5KhASa-LdBwBZ0wRFFqA%40mail.gmail.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/CANWgJS40pDAPs%3DtdbBh02-nB-Yj-Mq3Xn1u1CR8Cj4%3DjMR2dfg%40mail.gmail.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS40pDAPs%3DtdbBh02-nB-Yj-Mq3Xn1u1CR8Cj4%3DjMR2dfg%40mail.gmail.com?utm_medium=email&utm_source=footer>. >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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 >>>>>>> [email protected]. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/ace47ebc-7e1e-49fc-ac28-45f4c122af4a%40www.fastmail.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/ace47ebc-7e1e-49fc-ac28-45f4c122af4a%40www.fastmail.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/CAPfivLAG5GcMpn-gK9mZjnxyNP86k%3DkyBR-mF1r-_B7qdFOF9w%40mail.gmail.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAG5GcMpn-gK9mZjnxyNP86k%3DkyBR-mF1r-_B7qdFOF9w%40mail.gmail.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/CAH-3BickiKhACxMUdH_cqTDg%2Bv8KQPgMh%3Dx44kDGMahmfoGzgg%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BickiKhACxMUdH_cqTDg%2Bv8KQPgMh%3Dx44kDGMahmfoGzgg%40mail.gmail.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/247fd121-0f92-4d29-a52b-95b30d80e065%40www.fastmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/247fd121-0f92-4d29-a52b-95b30d80e065%40www.fastmail.com?utm_medium=email&utm_source=footer>. >>> >>> Email correspondence is considered personal data processing. Check out our >>> Privacy Policy <https://virtuslab.com/gdpr> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAEWeEB1zn--b-_r46SopJ2qsr1OY0fZoiKC2dwzJNkYQXs%2BAMQ%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAEWeEB1zn--b-_r46SopJ2qsr1OY0fZoiKC2dwzJNkYQXs%2BAMQ%40mail.gmail.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/61d6df62-20c7-4f1f-87f2-8d4f17b14dcfn%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/61d6df62-20c7-4f1f-87f2-8d4f17b14dcfn%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/eed0b74c-c057-4046-89e8-8672631b3b29%40www.fastmail.com.
