On Nov 1, 2022, at 11:49 AM, Helio Chissini de Castro <heliocastro@...> wrote:



Hello Shane and all

I'm stepping up for one of the positions of specification working group chair.

I've been on the OpenChain board before through my previous company, and in my current company, Cariad, I'm in charge of setting the open source tooling processes and technologies to be applied in the compliance area, so I think coming back to OpenChain is a good fit right now.

Best regards

On Mon, Oct 31, 2022 at 7:15 PM Shane Coughlan <scoughlan@...> wrote:

Mark Gisi, our founding chair of the OpenChain Specification Work Group (leading the creation of ISO/IEC 5230), will formally pass the leadership torch before end of year.

Because of this we are seeking two people to act as OpenChain Specification Chairs. The idea is to allow chairs to split the work and/or alternate between editing around License Compliance (ISO/IEC 5230) and Security (OpenChain Security Assurance Specification).

== How this will work ==

Being a chair around our specifications does not require specialized experience, but of course we do have some preferences:
(1) Be from a company using open source in products or services;
(2) Have domain knowledge in either license compliance or security assurance;
(3) Be detail-focused and unbiased;
(4) Have experience building consensus in community discussions.

== What the chairs do ==

(a) Participate in our monthly community calls;
(b) Help lead the segment reviewing open issues or accepting new issues around the specifications;
(c) Make judgement calls around what is included in the edit cycle and what is not (subject to Steering Committee approval for final decisions);
(d) Coordinate with the General Manager to finalize editing around the specifications;
(e) Participate in future Steering Committee meetings (4 per year from 2023) to vote on final versions of our specifications.

== How do I nominate myself? ==

Just say so in this thread.

== Is anyone else currently nominated? ==

Yes, Steve Kilbane from Analogue Devices has kindly stepped forward as a nominee for specification chair.

== 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.

== Rationale ==

The OpenChain Project has always had a strong focus on sustainability. As the maintainer of two industry standards, and the facilitator of a large supply chain community, our strategic position has always been to look at multi-year horizons.

As part of this, we are aware of the need to ensure our project reflects how people and activities adjust their priorities over time. A key example is the question it how we will address continuity in our work groups as our initial chairpeople reach the natural end of their tenure.

The answer is straightforward (as with most things in this project). We are introducing elections to allow chairs to rotate in a manner that is predictable and accessible.

Throughout this quarter and into 2023 we will gradually introduce more elections, and by 2H 2023 all the primary OpenChain work groups should have completed the introduction of chair elections.

== End ==

Regards

Shane

Shane Coughlan
OpenChain General Manager
+818040358083
Book a meeting:
https://meetings.hubspot.com/scoughlan

On Nov 1, 2022, at 17:49, Helio Chissini de Castro <heliocastro@...> wrote:

Hello Shane and all

I'm stepping up for one of the positions of specification working group chair.

I've been on the OpenChain board before through my previous company, and in my current company, Cariad, I'm in charge of setting the open source tooling processes and technologies to be applied in the compliance area, so I think coming back to OpenChain is a good fit right now.

Best regards




On Mon, Oct 31, 2022 at 7:15 PM Shane Coughlan <scoughlan@...> wrote:
Mark Gisi, our founding chair of the OpenChain Specification Work Group (leading the creation of ISO/IEC 5230), will formally pass the leadership torch before end of year.

Because of this we are seeking two people to act as OpenChain Specification Chairs. The idea is to allow chairs to split the work and/or alternate between editing around License Compliance (ISO/IEC 5230) and Security (OpenChain Security Assurance Specification).

== How this will work ==

Being a chair around our specifications does not require specialized experience, but of course we do have some preferences:
(1) Be from a company using open source in products or services;
(2) Have domain knowledge in either license compliance or security assurance;
(3) Be detail-focused and unbiased;
(4) Have experience building consensus in community discussions.

== What the chairs do ==

(a) Participate in our monthly community calls;
(b) Help lead the segment reviewing open issues or accepting new issues around the specifications;
(c) Make judgement calls around what is included in the edit cycle and what is not (subject to Steering Committee approval for final decisions);
(d) Coordinate with the General Manager to finalize editing around the specifications;
(e) Participate in future Steering Committee meetings (4 per year from 2023) to vote on final versions of our specifications.

== How do I nominate myself? ==

Just say so in this thread.

== Is anyone else currently nominated? ==

Yes, Steve Kilbane from Analogue Devices has kindly stepped forward as a nominee for specification chair.

== 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.

== Rationale ==

The OpenChain Project has always had a strong focus on sustainability. As the maintainer of two industry standards, and the facilitator of a large supply chain community, our strategic position has always been to look at multi-year horizons.

As part of this, we are aware of the need to ensure our project reflects how people and activities adjust their priorities over time. A key example is the question it how we will address continuity in our work groups as our initial chairpeople reach the natural end of their tenure.

The answer is straightforward (as with most things in this project). We are introducing elections to allow chairs to rotate in a manner that is predictable and accessible.

Throughout this quarter and into 2023 we will gradually introduce more elections, and by 2H 2023 all the primary OpenChain work groups should have completed the introduction of chair elections.

== End ==

Regards

Shane

Shane Coughlan
OpenChain General Manager
+818040358083
Book a meeting:
https://meetings.hubspot.com/scoughlan

On Nov 1, 2022, at 22:42, Christopher Wood <cvw01@...> wrote:

Hello Shane
I would be interested in stepping up for the security side.
Regards
Chris

On Nov 1, 2022, at 11:49 AM, Helio Chissini de Castro <heliocastro@...> wrote:

Hello Shane and all

I'm stepping up for one of the positions of specification working group chair.

I've been on the OpenChain board before through my previous company, and in my current company, Cariad, I'm in charge of setting the open source tooling processes and technologies to be applied in the compliance area, so I think coming back to OpenChain is a good fit right now.

Best regards




On Mon, Oct 31, 2022 at 7:15 PM Shane Coughlan <scoughlan@...> wrote:
Mark Gisi, our founding chair of the OpenChain Specification Work Group (leading the creation of ISO/IEC 5230), will formally pass the leadership torch before end of year.

Because of this we are seeking two people to act as OpenChain Specification Chairs. The idea is to allow chairs to split the work and/or alternate between editing around License Compliance (ISO/IEC 5230) and Security (OpenChain Security Assurance Specification).

== How this will work ==

Being a chair around our specifications does not require specialized experience, but of course we do have some preferences:
(1) Be from a company using open source in products or services;
(2) Have domain knowledge in either license compliance or security assurance;
(3) Be detail-focused and unbiased;
(4) Have experience building consensus in community discussions.

== What the chairs do ==

(a) Participate in our monthly community calls;
(b) Help lead the segment reviewing open issues or accepting new issues around the specifications;
(c) Make judgement calls around what is included in the edit cycle and what is not (subject to Steering Committee approval for final decisions);
(d) Coordinate with the General Manager to finalize editing around the specifications;
(e) Participate in future Steering Committee meetings (4 per year from 2023) to vote on final versions of our specifications.

== How do I nominate myself? ==

Just say so in this thread.

== Is anyone else currently nominated? ==

Yes, Steve Kilbane from Analogue Devices has kindly stepped forward as a nominee for specification chair.

== 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.

== Rationale ==

The OpenChain Project has always had a strong focus on sustainability. As the maintainer of two industry standards, and the facilitator of a large supply chain community, our strategic position has always been to look at multi-year horizons.

As part of this, we are aware of the need to ensure our project reflects how people and activities adjust their priorities over time. A key example is the question it how we will address continuity in our work groups as our initial chairpeople reach the natural end of their tenure.

The answer is straightforward (as with most things in this project). We are introducing elections to allow chairs to rotate in a manner that is predictable and accessible.

Throughout this quarter and into 2023 we will gradually introduce more elections, and by 2H 2023 all the primary OpenChain work groups should have completed the introduction of chair elections.

== End ==

Regards

Shane

Shane Coughlan
OpenChain General Manager
+818040358083
Book a meeting:
https://meetings.hubspot.com/scoughlan

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.

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.

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.