Thanks for this topic. One idea is to start with the ‘core’ and ‘integrity’ subgroups, and move to others in a few weeks, after the first two solidify.
Please attend tomorrow if you can, and let’s discuss.
From: Steve Springett <firstname.lastname@example.org>
Sent: Tuesday, March 31, 2020 8:22 PM
To: email@example.com; Kay Williams <firstname.lastname@example.org>
Subject: Re: 3T-SBOM Meeting Agenda
What is the cadence for the subgroups to meet?
There are 7 subgroups. I’m interested in all of their topics, but if each group meets weekly for an hour, that’s an entire day dedicated to this effort. What is the plan on making data-driven design decisions efficiently?
I’ll likely attend all (if efficient) or none.
On Mar 31, 2020, 10:14 PM -0500, Kay Williams <email@example.com>, wrote:
Here is a draft agenda for tomorrow’s 12 noon pacific meeting. Additions and suggestions are welcome, please send to me or add directly to the
June 22-26 - OMG Technical Meeting - Orlando, FL USA (or virtual)?
Sign up for subgroups (here)
Identify facilitators for each group
When to kick off additional subgroups?
Start with core and integrity and work out the kinks?
Don’t spread ourselves too thin?
Core Subgroup recap (William)
Licensing (spec and code)
Mission, scope, values, governance, licensing, website, etc.
Infrastructure needed for subgroups (Google drive, GitHub, mailing lists?, other?)