Just wanted to chime in and say this is all great and much needed. I have
discussed this offline with Tracy and I'm really looking forward  to it.

On Tue, Sep 10, 2019 at 8:43 AM Oleg Nenashev <[email protected]>
wrote:

> Hi all,
>
> Just a quick update, we had a meeting today to discuss the proposal. You
> can find the meeting notes here
> <https://docs.google.com/document/d/1K5dTSqe56chFhDSGNfg_MCy-LmseUs_S3ys_tg60sTs/edit#heading=h.ae5z3dazo3o5>
>  (Advocacy
> and Outreach SIG meeting notes). There are some comments and follow-up
> action items, but basically there is a consensus that we would like to run
> the board election within the proposed timeframe. Next Thursday we will
> have another meeting, and we can use it as an opportunity for additional
> discussion if needed. The Governance meeting vote will happen tomorrow.
>
> After the discussion, we have also updated the list of the motions which
> are tabled for the tomorrow's voting:
>
>    - All officer positions will be voted on in 2019 will be voted on in
>    2020 (Team Leads <https://wiki.jenkins.io/display/JENKINS/Team+Leads>)
>    - 3 Board positions are elected instead of 2 in the base document
>    (Dean Yu's seat + 2 new seats)
>    - CDF will supervise the election and run the voting using The
>    Condorcet Internet voting system <https://civs.cs.cornell.edu/> instead
>    of Single Transferable Vote
>    <https://en.wikipedia.org/wiki/Single_transferable_vote>
>    - The election cut-off date for valid jenkins.io accounts for the 2019
>    election is 1st September 2019
>    - The proposed election schedule will start on 13 September 2019 and
>    conclude on 4 November 2019 with intermediate dates as per dev list thread
>    - Adding new officer role: Documentation officer (content officer from
>    the 2015 Proposal - Project sub-teams
>    <https://wiki.jenkins.io/display/JENKINS/Proposal+-+Project+sub-teams>)
>
> If you are interested to propose more changes, please comment in this
> thread.
>
> Best regards,
> Oleg
>
>
> On Sunday, September 8, 2019 at 10:49:09 PM UTC+2, Oleg Nenashev wrote:
>>
>> Tueday 2PM-3PM UTC is a Winner, Zoom meeting ID:
>> https://zoom.us/j/792918819
>> <https://www.google.com/url?q=https://zoom.us/j/792918819&sa=D&usd=2&usg=AOvVaw2f_Ysi2fsBp2gGTUE-EwCY>
>> Please see Jenkins calendar for the more information and links.
>>
>> BR, Oleg
>>
>>
>> On Friday, September 6, 2019 at 6:28:07 PM UTC+2, Parker Ennis wrote:
>>>
>>> Little late here but +1!
>>>
>>> On Fri, Sep 6, 2019 at 11:32 AM Tracy Miranda <[email protected]>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Thanks all for the great input!
>>>>
>>>> Oleg - thank you so much for the detailed background and input, all
>>>> very useful! Also yes, having a session next week for clarification will be
>>>> amazing!
>>>>
>>>> Lloyd - great suggestion, thanks! I did notice the page is updated
>>>> based on board resolutions so let's hold off on updating until we agree and
>>>> pass the resolutions.
>>>> In the meantime for clarity I have listed specific voting motions on
>>>> the agenda for the next governance meeting:
>>>> https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-September11
>>>> These may evolve before then but thought it would be a good start to
>>>> list the concrete proposals.
>>>>
>>>>  >>Jenkins has joined CDF almost 1 year ago, but there are still A LOT
>>>> of open questions about the migration to CDF
>>>>  If I could indulge one bit of nitpicking: CDF officially launched
>>>> <https://cd.foundation/in-the-news/2019/03/12/cloud-tech-cloudbees-google-and-linux-foundation-launch-continuous-delivery-foundation/>
>>>> March 12 2019 and the SPI resolution for Jenkins
>>>> <http://lists.spi-inc.org/pipermail/spi-general/2019-May/004001.html>
>>>> passed on June 10 2019 and the project is still transitioning. All this to
>>>> stress that while it may feel like a year (and it certainly feels longer
>>>> than that to me!) it is all good and this is an excellent time to be
>>>> running elections and all part of the process as Jenkins evolves within the
>>>> framework of CDF. Please feel free to reach out if any specific questions -
>>>> ultimately we all drive the answers to these questions together.
>>>>
>>>> Looking forward to more election discussions and moving this forward!
>>>>
>>>> Regards,
>>>> Tracy
>>>>
>>>>
>>>> On Fri, Sep 6, 2019 at 11:09 AM Oleg Nenashev <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> In looking at the election process I wonder if it would be good to
>>>>>> have a meeting to discuss any confusion voters may have?
>>>>>>
>>>>>
>>>>> I suggest we run a discussion on Monday or Tuesday to discuss any
>>>>> concerns and to clarify missing bits.
>>>>> I have created https://doodle.com/poll/innt9x487f8wumkr with
>>>>> timeslots when I can run the meeting. Please vote there by Saturday EoD so
>>>>> that I get the session scheduled.
>>>>> Let;s do it in Zoom + use additional Google Doc to record the feedback
>>>>>
>>>>> Ask — Would you kindly update Board Election Process at
>>>>>> https://wiki.jenkins.io/x/lIHPAw and describe your proposal there?
>>>>>>
>>>>>
>>>>> I'd guess the page is restricted to board members only, I am not sure
>>>>> who else have access to it.
>>>>> But we could run a new page e.g. in Google Doc which can be later
>>>>> converted to a JEP on GitHub
>>>>>
>>>>> BR, Oleg
>>>>>
>>>>> On Friday, September 6, 2019 at 5:28:55 AM UTC+2, Lloyd Chang wrote:
>>>>>>
>>>>>> Hi, Tracy,
>>>>>>
>>>>>> Ask — Would you kindly update Board Election Process at
>>>>>> https://wiki.jenkins.io/x/lIHPAw and describe your proposal there?
>>>>>>
>>>>>> Intent of my (meta-level) ask is to align (newcomer) people’s
>>>>>> knowledge acquisition based on existing centralized information on
>>>>>> wiki.jenkins.io web site with revision history.
>>>>>>
>>>>>> Thank you,
>>>>>> Lloyd
>>>>>>
>>>>> --
>>>>> 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/7e654d5a-f42e-4746-9620-a5dbe7831d4f%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/7e654d5a-f42e-4746-9620-a5dbe7831d4f%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/CACTaz6qujjr6%2BMWKO27LPXkeQtfuPOVCjMzLtON6FsZ3tAHqNQ%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6qujjr6%2BMWKO27LPXkeQtfuPOVCjMzLtON6FsZ3tAHqNQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>>
>>> --
>>>
>>> *Parker Ennis*
>>>
>>> *Product Marketing Manager*
>>>
>>> [image: CloudBees-Logo.png]
>>>
>>>
>>> M: (803) 386-7562
>>> E: [email protected]
>>> Skype: parker.cb
>>> Twitter: @Parker_CB <https://twitter.com/Parker_CB>
>>>
>>>
>>> --
> 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/c50eedb2-e2a8-473d-8039-d8308a9ee8f3%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/c50eedb2-e2a8-473d-8039-d8308a9ee8f3%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Kohsuke Kawaguchi

-- 
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/CAN4CQ4wodRRpZ7__3kjGJK8A8z0cbEPX37qi%3DYJ%3DXkUWKdPZPg%40mail.gmail.com.

Reply via email to