How To Join The New Export Control Work Group


 

Rama, Done!

All, a reminder that you can join our new export control WG by sending a mail to:

export-control-wg+subscribe@...

On Oct 18, 2022, at 8:33, D, Rama Devi via lists.openchainproject.org <ramadevi_d=comcast.com@...> wrote:

I would also like to join please.

From: main@... <main@...> on behalf of Balakrishna Mukundaraj <balakrishna1838@...>
Date: Monday, 17 October 2022 at 10:00 PM
To: oss-based-compliance-tooling@groups.io <oss-based-compliance-tooling@groups.io>
Cc: OpenChain Main <main@...>
Subject: [EXTERNAL] Re: [openchain] Export Control Work Group Start Date (was Re: [oss-based-compliance-tooling] OpenChain Work Groups – New and Improved Structure)

I would also like to join please.

On Mon, 17 Oct 2022 at 21:48, Shane Coughlan <scoughlan@...> wrote:
Julian, Chris and Steve, you have all been added to the next Export Control WG mailing list.

Anyone else want to join before the formal launch in November?

Subscribe by sending an email to this address:
export-control-wg+subscribe@...

On Oct 13, 2022, at 15:50, Christopher Wood <cvw01@...> wrote:

Shane
I would be interested in participating in the Export Control WG. I have a lot of experience working these issues.

On Oct 13, 2022, at 6:05 AM, Shane Coughlan <scoughlan@...> wrote:

Topical, definitely ;)

How about we have the first meeting in November? I am thinking circa 15th November.

On Oct 13, 2022, at 11:26, Julian Coccia <julian.coccia@...> wrote:

I'm also very interested in the Export Control WG!

On 13 Oct 2022, at 08:48, Steve Kilbane <stephen.kilbane@...> wrote:
HI all,

Looks good to me.

* I’m keen to see the Export Control WG get up and running. :-)
* Co-ordination between the Licensing and Security WGs will be important, IMO – if the two specs can remain as close as possible while evolving and improving, that will help with adoption, I think.
* You didn’t mention the Telco or Automotive WGs. While there might not be any changes there, perhaps the diagram might separate out the industry-specific WGs into a Verticals column, as they’re distinct from the geographical WGs and the topical WGs? That would also allow for emphasis that there’s scope for more WGs in both verticals and geography as need or desire arises?

steve

From: oss-based-compliance-tooling@groups.io <oss-based-compliance-tooling@groups.io> on behalf of Shane Coughlan <scoughlan@...>
Date: Wednesday, 12 October 2022 at 15:59
To: OpenChain Main <main@...>
Cc: OpenChain Education <education@...>, OpenChain Telco Work Group <telco@...>, OpenChain Conformance <conformance@...>, OpenChain Specification <specification@...>, OpenChain Automotive <openchain-automotive-work-group@groups.io>, OpenChain Tooling <oss-based-compliance-tooling@groups.io>
Subject: [oss-based-compliance-tooling] OpenChain Work Groups – New and Improved Structure
[External]



The OpenChain Project has been very active since its formal launch in late 2016. Our global community has built an ISO/IEC standard for license compliance, launched a de facto (and soon to be ISO/IEC) standard for security. We have contributed to SBOM, OSPO, training, policy and other discussions. We built the world’s largest library of open source management reference material.

To reflect our growth and to make it easier to navigate the project we are going to make some adjustments to our work groups. Nothing too radical, but definitely something to help people find their way around more quickly, and to get the information they want faster. The image above contains a summary of the evolution approved by our Governing Board at their last meeting in September, and targeted for release during October 2022.

The changes?

• The Specification Work Group will split into two parts – a Licensing Work Group for ISO/IEC 5230 and a Security Work Group for the Security Assurance Specification.
• The Education Work Group and Outreach Work Group will combine into the Education Work Group.
• We will launch a new Export Control Work Group and a new Policy Work Group. The former will help to navigate issues around increasing international trade tensions. The later will help us provide strategic advice around the highest level of planning for open source in legislation and business.
• The dormant Conformance Work Group will be wound down and discussions regarding self-certification moved to Education Work Group, with discussions about the nuance of conformance parameters moved to our Steering Committee.
• Finally (if there are no objections), we will re-brand the Reference Tooling Work Group to the Automation Work Group to help guide people hearing about automation to the right solutions.

Feedback?

Your feedback – as always – is most welcome. Please provide comments to our main mailing list:
https://urldefense.com/v3/__https://lists.openchainproject.org/g/main__;!!A3Ni8CS0y2Y!7UKvKw4i4uqlo8p2ARHma4zmbQsXGYNBVRH1C9pmK0rnBuU4nP0j89f7myAOFhWMB1tdfW_n1uYdsBBzIdcFz1RC3wbVjik$<https://urldefense.com/v3/__https:/lists.openchainproject.org/g/main__;!!A3Ni8CS0y2Y!7UKvKw4i4uqlo8p2ARHma4zmbQsXGYNBVRH1C9pmK0rnBuU4nP0j89f7myAOFhWMB1tdfW_n1uYdsBBzIdcFz1RC3wbVjik$>
(or just reply all to this email)

Please provide feedback by Close of Business UTC (17:00 UTC) on the 18th of October 2022.

























--
Thanks & Regards,
Balakrishna

Join main@lists.openchainproject.org to automatically receive all group messages.