Wood, Chris <chris.wood@...>
toggle quoted message
Show quoted text
Hello OpenChain team
Allow me to introduce myself to those who do not know me. I am Dr. Chris Wood and I have been working for the past 30 years in the software assurance arena and 20 years specifically with open-source licensing. For my Company I was a member
of the original team who created a licensing scanner that enabled our business to conduct deep software scanning capability across all software languages for both open source and commercial software. I personally ran the team for 17 years who performed the
software analysis and then reviewed the proposed compliance actions with Legal Counsel to either approve or reject them. During development we created an automated tool to produce the software bill of materials (SBOMS) which includes: component names, a copy
of every license, notice, and provided author(s) attributions where requested. These SBOMS were provided to the customer (internal and external).
I have been actively participating in the OpenChain project since approximately 2017 and have contributed substantial review and substance to both the license governance and the software security guide specifications.
Thank you for considering me as a candidate, it would be my honor to serve the team in any capacity where needed.
Dr. Chris Wood CISSP
On Wed, Nov 16, 2022 at 10:04 AM Shane Coughlan <scoughlan@...
Steve, Helio, Jacob and Chris, I would like to invite you to share a brief bio of yourself in this thread to help our potential votes to understand who you are. Given our wide community, not everyone makes our
calls, and may not know you from your active contributions there and on GitHub, etc.
> On Nov 16, 2022, at 9:59, Shane Coughlan via
lists.openchainproject.org <scoughlan=linuxfoundation.org@...> wrote:
> OpenChain Specification Chair Election Period Now Open
> The OpenChain Project is running an election for co-chairs of the Specification Work Group. The election period is from today (2022-11-16) until 2022-11-22 Close of Business UTC.
> Here are our current nominees:
> • Steve Kilbane, Analog Devices
> • Helio Chissini de Castro, CARIAD
> • Jacob Wilson, Gemini
> • Chris Wood, Lockheed Martin
> Everyone is invited to vote for their preferred chairs. Here is how:
> • You have two votes.
> • One is licensing focused (Steve or Helio) and one is security focused (Jacob or Chris).
> • You can vote by (a) signing up to our Specification mailing list (because this mailing list is our single source of truth for specification work) and (b) sending an email to
operations@... with the subject “Specification Chair Elections” and the following content:
> My name is NAME and my votes are as follows:
> NAME for licensing
> NAME for security
> YOUR NAME
> Some notes:
> • The email address ending your vote must be subscribed to the specification mailing list.
> • Any vote not provided in this format will be invalid.
> • You can vote for yourself.
> • You can only submit your votes once.
> More Details
> How we are running this election is split into two lengthy descriptions below. We are striving to do two things:
> • Create an open election process
> • Address the potential we have to have multiple domain experts sharing work
> Because this is our first major election for Specification Chair, the process may have some rough edges. If there are any critical issues, we will address them.
> How We Are Running The Elections
> 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
> (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 22nd 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.
> For This Specific Election
> 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.
> 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.