I wanted to provide a brief clarification to our election process. Thanks to Chris Wood for flagging the ambiguity.
We are fortunate to have four people - two with a background in compliance and two with a background in security - standing for our two co-chair positions. For this specific election we are splitting the vote so our end result will include an expert from each domain.
However, for clarity, the intent is not to split the development of our licensing and security specifications into two different paths. The intent is that both chairs will work on both specifications by helping to collect community feedback and so on, with this feedback being provided to the Steering Committee for formal review and ratification if and when we decide to produce new versions of our standards.
We do not want to split development into two diverging channels :)
toggle quoted message
Show quoted text
On Nov 7, 2022, at 21:08, Shane Coughlan via lists.openchainproject.org <scoughlan=linuxfoundation.org@...> wrote:
As promised, a detailed outline of how we will run the specification work group co-chair election for 2022. This is our first time to run this election, so please forgive any hiccups on the way, but we expect smooth sailing.
===
The OpenChain Governing Board is formally considering who should be appointed by the board for the position(s) of OpenChain Specification Chairperson, and invites the broader OpenChain community to provide their perspective.
In this process, the broader OpenChain community will have nominees proposed and voted on to provide a recommendation. That recommendation will be passed to the OpenChain Governing Board for review, approval and ratification at their next meeting.
The specific process on behalf of the community is to undertake a voting process after a period of nomination. The community will vote in the following manner:
Votes for chairpeople will be sent by email to operations@... (received by the OpenChain General Manager and Project Manager).
Each member of our specification@ can cast *one* vote. All members of main@ are entitled to join specification@. The requirement to join the specification list is to maintain that list as the “single source of truth” for our specification-editing and other core specification work.
The votes will be tallied by the General Manager and prepared for the OpenChain Governing Board to review.
The tally will be reported to the OpenChain governing board. Their feedback and final decision will be provided to the community-at-large after their next formal governing board meeting.
For the 2022 OpenChain Specification Work Group elections the following notes are provided:
(1) we are operationally splitting the specification work group into two work groups: licensing and security, reflecting our two specifications in-market.
(2) for *this* specific election, we will split the election into two threads: one license biased (two nominees) and one security biased (two nominees). The result will be two chairs to fill the co-chair positions after approval by the OpenChain Governing Board.
(3) this means everyone on specification@ should vote for:
(i) their preferred choice for license work group chair;
(I) their preferred choice for security work group chair.
(4) these votes may be cast between the 16th and 22d of November 2022.
(5) the OpenChain Governing Board will receive the tally of votes expressing community feedback, and will review it formally at their next meeting on the 8th of December 2022.
(6) it is expected that at this juncture the community will receive a response from the OpenChain Governing Board regarding their decision(s) around specification chairperson(s) circa 9th December 2022, and our new specification chairs will begin their term of office prior to 2023.
This process may be adjusted at any time by the governing board, and feedback to improve the process is always welcome, with the optic of ensuring that we continually refine the process as time progresses.
Regards
Shane
Shane Coughlan
OpenChain General Manager
+818040358083
Book a meeting:
https://meetings.hubspot.com/scoughlan
On Nov 4, 2022, at 17:26, Shane Coughlan via lists.openchainproject.org <scoughlan=linuxfoundation.org@...> wrote:
Thanks Steve. Great question.
Let’s clarify the election process.
For the nomination period, we happen to have two people well versed in license compliance (Steve and Helio) and two people with a security background (Jacob and Chris). This suggest that our co-chair election - for *this* specific election, should break into two threads: one license biased (two nominees) and one security biased (two nominees). The result will be two chairs to fill the co-chair positions after approval by the OpenChain Governing Board.
Any objections?
I will send an email early next week clarifying the election period itself in the post November 15th period: how the community votes, what precisely the vote means, and how it relates to the Governing Board. Nutshell: there will be an open vote and the resulting names will go before the Governing Board. More to follow.
Regards
Shane
On Nov 2, 2022, at 9:52, Steve Kilbane <stephen.kilbane@...> wrote:
Hi Shane,
Can you clarify the election process, please? Are there two separate votes, for each of the chair positions, or one single vote, and the two candidates who receive the highest number of votes are the two new chairs?
I’m asking because, if you’re aiming for one chair well-versed in license compliance and another well-versed in security, you could end up electing two people who fall on the same side of that divide.
To give people some background, I’m the OSPO director at Analog Devices, and I’m very much on the license-compliance side, not so much on the security side.
steve
From: main@... <main@...> on behalf of Shane Coughlan <scoughlan@...>
Date: Wednesday, 2 November 2022 at 08:30
To: OpenChain Specification <specification@...>
Cc: OpenChain Main <main@...>
Subject: Re: [openchain] Introducing Work Group Chair Elections: Specification Work Group
[External]
Hello everyone!
Here are our current nominees in the specification co-chair election:
Steve Kilbane, Analog Devices
Jacob Wilson, Gemini
Helio Chissini de Castro, CARIAD
Chris Wood, Lockheed Martin
There are two spaces, so we already have an interesting and excellent election! Well done all.
Are you interested in entering this election? You can nominate yourself before November 15th.
Please note: everyone is standing as an individual. I am just citing their companies as a way to contextualize who I am referring to, due to our community containing thousands of people :)
Regards
Shane
On Oct 31, 2022, at 20:56, Jacob Wilson <jacobdjwilson@...> wrote: == How do I nominate myself? ==
Just say so in this thread.
[…]
== What happens next ==
(1) We have two spaces in total available (co-chairs);
(2) If two or fewer people are nominated before November 15th, they will become co-chairs of the specification activity around OpenChain with a one year term;
(3) If more than two people are nominated before November 15th, an election will be triggered;
(4) The election will take place via email between 15th and 22nd November and will be “first past the post;”
(5) Current chairs may be re-elected in the next cycle in the same manner as this time.
We may, of course, adjust this process for future years depending on lessons learned from this first election cycle.
|
