Proposed addition of Working Group documentation

[eddie-knight]

Feature Request

Description of Problem:

The CFI community is regularly investing effort to a single workstream at the expense of other work that has users and contributors available. The cause of this misallocation of effort is primarily organizational: we have a single stream of communication for three separate workstreams (Compliance Definitions, Reproducable Builds, and Validation Tests)

Potential Solutions:

The following should be documented and implemented:

• Working groups exist for each of the three work streams, with dedicated leadership for each determined by the full CFI community.
• Each working group is to define their own meeting structure and contribution structure.
• The CFI all-community call is given a decreased frequency to provide public updates on each workstream (either 6 or 12 meetings per year)

[eddie-knight]

We'll need to track the creation of each working group independently, as it will involve different people and processes. I'll create simple issues to hold the details for each WG and will link them here for central reference.

[eddie-knight]

Working group documentation may best live in a community/ or working_groups/ directory at the top level of this repo (suggestion from @ml4)