[Discovery Umbrella] Inventory and Things

[parispittman]

Streams that will kick us off and set us up for success. We can set separate detailed issues for each with their respective owners.

Things we are going to need to move forward:

• Create a resources page #15 Resources page

• create short, focused survey [beating the keep to our scope drum] to send to project maintainers Create a discovery survey for contrib programs and gov #19
  paris/karen

• draw out the contributor related items needed for graduation and other should and nice to haves to start on contributor health check due diligence for TOC
  Josh/Gerred/Stephen/Paris

People to meet with:

• GB Reps: Matt and Michelle. Talk about how we can work together to feed this group with some of the contributor related things coming from past and current discussions with maintainers. The GB Reps will also deal with matters that are out of scope with us so make sure we find common ground vs combining efforts. We shouldn't be in or out of their way - need a happy middle.
  (potential artifact: list of contributor related needs, add to charter roadmap where necessary or add to the 'future roadmaps' section so others can pick up that might want to work on it.
  Gerred

• talk to matt about how he wants updates, info, etc.
  chairs

• talk to cheryl about getting a program bootstrapped for contributor<->end user
  bootstrap with cncf members, open to other end users
  start a separate issue
  paris/stephen/ihor/karen

What else?
Reminder: our SIG is high risk for scope creep. Stay cautious :)

[gerred]

@parispittman I will (it's Friday night, so not thinking of new things) own meeting with Matt and Michelle, and put together the list of dev mailing lists.

[justaugustus]

a list of maintainer related dev mailing lists for cncf projects (example: [email protected]) - possibly links to communication docs for contributors
NEEDS AN OWNER

I'll pick this one up.
oop, nevermind. I missed @gerred's previous comment.

---

Will also work on README and updating cncf/toc w/ our TOC liaisons.

---

do working groups need their own meeting times? we should have a main meeting bi weekly to bootstrap for 6 months but i could see this go once a month with smaller working groups going and coming together at the main group. [low priority]

In an informal hang, I mentioned to @parispittman and @gerred that we could alternate meetings. One biweekly could be the formal SIG ContribStrat meeting, with the other being an Office Hours of sorts, dedicated to meets w/ GB Reps, discussions/presentations from other SIGs on pain points.

[justaugustus]

Opened two issues that could be considered part of this umbrella:

• [idea] Create cncf/community repo: [idea] Create cncf/community repo #4
• ContribStrat GitHub Management: ContribStrat GitHub Management #5

[jberkus]

draw out the contributor related items needed for graduation and other should and nice to haves to start on contributor health check due diligence for TOC
NEEDS AN OWNER/PROBABLY JOSH

Yeah, this sounds like me.

[parispittman]

@idvoretskyi has an out dated list of maintainer mailing lists; @gerred will link to up ihor

[idvoretskyi]

Here is the list of the lists - https://github.com/cncf/contribute/tree/master/projects

[idvoretskyi]

Surveys - https://github.com/cncf/surveys/

[idvoretskyi]

@jberkus the surveys data is updated at https://github.com/cncf/surveys/; please check.

[parispittman]

closing this issue and will open a fresh one for the end user bullet