Notes and follow-up from July call

Thanks to everyone who was able to join our July EWG call last week.

*July Meeting Recap*

   - The primary agenda item was to take stock of all the workstreams and
   come up with a way to categorize them based on progress to date.
   - We arrived at a great place.
      - We will adopt a common process used at places like the Apache
      Software Foundation and various "umbrella" projects at the Linux
      Foundation, like CNCF and OpenJS Foundation.
      - Namely, we will have entrance and exit criteria for workstreams.
      - We primarily focused on the exit criteria:

*We will consider a workstream to be "Graduated" from the EWG when there
is an ongoing home (maintainer or sub-project) inside the FreeBSD ecosystem
that is staffed and has a roadmap for ongoing initiatives, or a "completion
date" for one-off projects*


   - We categorized existing workstreams as follows:

Status

Count

Notes

Graduated

6

Staffed and owned by another group

Complete

1

One-time effort that has been shipped

In Progress

3

Actively being worked by named owners

Blocked

4

External dependency or missing sponsor

Not Started

6

Requirement accepted but no resources yet


*We also agreed that now is a great time to produce a status report on the
EWG's work. *

   - *Please find a draft for review and comment
   here: https://docs.google.com/document/d/1h04pAQvxjvInOzm8RfpM7Qh-8J_S47FshiWHBfCyVwo/edit?usp=sharing
   <https://docs.google.com/document/d/1h04pAQvxjvInOzm8RfpM7Qh-8J_S47FshiWHBfCyVwo/edit?usp=sharing>*
   - Please add any comments before the August meeting. I will incorporate
   all comments and publish the report on the EWG Wiki Page:
   https://wiki.freebsd.org/EnterpriseWorkingGroup

*Moving Forward*

   - The WG will focus on the In Progress workstreams, providing support to
   the owners and tracking progress in order to report out.
   - We need a mechanism for adding new Workstreams. For now, please submit
   proposals to the mailing list, using the following convention
      - Subject line: EWG new workstream proposal
      - Email body:
         - Proposed name of workstream
         - Why EWG is the right place, including research demonstrating
         that other fora are not already covering the topic
         - How the gap impacts FreeBSD users
         - Describe how you anticipate resourcing the effort - e.g.
         identifying who can work on the effort and who may be able to fund the
         effort
      - We will then determine how to vote on and prioritize in-coming new
      workstream proposals

*Admin*

   - Unfortunately due to a company policy change, I am unable to share the
   Fathom recording of the July meeting. I am working on getting an exception
   and will share the recording if I can. Going forward, I will be sure to use
   a Zoom recording which I will be able to share. Apologies for the
   inconvenience.

Thank you!!

Greg