The status table has columns with the following meanings:
- Workstream: the interdependency being tracked, linking back to related issues on the community board.
- Status color: At a glance indication of the status of the workstream:
Workstream is in trouble, somehow seriously off-track, or significantly behind schedule
There is an increased risk of the workstream milestones being affected.
When everything is going well but you have some reservations about calling it all the way Green.
The project is on-track and on-schedule.
- Notes: Details about the status, listing blockers and actions.
| Workstream | Status | SIG :: Owner(s) | Notes |
|---|---|---|---|
| Attracting users |  |
NONE | Open source dev intake needs work SRE coop students process for SRE Camp is OK for docs and mentoring, curriculum needed Needs an SRE learning paths SIG Action: Put out call for a SIG to handle open source dev intake path definition and laying out the vision for what the SRE learning paths will look like. |
| Messaging |  |
Community SIG :: Karsten Wade, Gordon Haff | New next step is honing in the community with Gordon Haff, Jason Brooks, et al Needs community mailing list discussions and ODF-style to finalize Action: As part of honing, start messaging thread on mailing list about the state of messaging and where decisions/consensus is needed |
| Contributor experience | |
NONE | New contributor experience is rough and confusing Community Handbook effort should help, but a critical threshold in the Community Handbook is needed to make it through good-enough tiers: ready for experienced people, ready for some level of close assistance, ready for anyone, etc. Action: Continue to drive thread on mailing list about the Handbook and handbook-first philosophy Ask for commitments, volunteers to get handbook rolling We have the SMEs we need for this, a SIG or subproject is needed to work with SMEs, create a plan, and implement the changes. |
| Governance | |
Community SIG :: Karsten Wade | Discussion draft is open and being worked for a Dec 2021/Jan 2022 closure. Mailing list thread contains more details and discussion. |
| Learning paths |  |
NONE | New operate-first/training repo created, needs configuring with owners, README, and contributing.mdA lot of internal alignment happening, will be looking to start SRE SIG in Op1st Need to start creating learning paths on website using new TBD format Action: Generate ADR about where the training pool will be; does SRE SIG keep all in same SRE repo? |
| Metrics plan | |
NONE | New efforts underway to capture the baseline, such as this Jupyter Notebook. Need to move from ad-hoc to strategic Action: SIG needs to take responsibility to define and run this metrics effort. |
| Documentation plan | |
NONE | Working on plan now in this issue Project overall has the right idea, the Community Handbook should help a lot. User documentation needs organizing, gap analysis, and a plan. Part of the new contributor experience being rough is the UX around discovering and using documentation Action A SIG needs to take responsibility to define and run this effort. |
| Infrastructure (visibility, resources) | |
NONE | All there, more visibility of what is where is needed More hardware needed but coming soon NOTE: we hear about 100x afterward when someone is held for no resources, it's bad for our reputation Action: Needs transparent update page to ease concerns and help with planning, reputation Action A SIG needs to take responsibility to define and run this effort. |
| Marketing plan | |
NONE | Needs to be converted entirely into a community document and see the project board is filled properly with all the aspects Action A SIG needs to take responsibility to define and run this effort. |
| Event planning | |
NONE | Action: CFP and event coordination underway for SCaLE 19x, KubeCon Valencia 2022, Red Hat Summit, and KubeCon Detroit 2022. Action A SIG needs to take responsibility to define and run this effort. |
| Brand review | |
NONE | Need an open source designer and a logo review/refresh. Action A SIG needs to take responsibility to define and run this effort. Blocked on people's time |
| Help wanted | |
NONE | Fairly simple process, just beginning to use. Need to document how to use it, and spread the word about using these, as well as getting it into the Community Handbook. Action A SIG needs to take responsibility to define and run this effort. Blocked on people's time |
| Good first issue | |
NONE | Fairly straightforward process, just beginning to use. Need to document how to use it, and spread the word about using these, as well as getting it into the Community Handbook. Action A SIG needs to take responsibility to define and run this effort. Blocked on people's time |