...
- Build Release / Community Releases
- Please chime in on this wiki page!
- TSC: please try to get all comments in this week!
- Tagging
- Branching
- Validation CI/CD
- Release schedule
- Release notes (+ automation of) - To be discussed again
- Creation of committees
- Documentation
- Community Infrastructure (CI/CD)
- Please chime in on this wiki page!
- Improve Ease of Use
- Improve documentation
- Establish target goals
- Ensure there is a cadence between the documentation working group and TSC to meet goals
- Review current implementation and challenges
- Clarifications on where to make changes
- Release branches versus Master
- Clarifications on where to make changes
- "First contact" documentation
- Stacking up TF (especially for newcomers)
- devstack-like experience for developers who want to contribute
- Katacoda demos
- Improve documentation
- Review Governance Process
- The ARB question (see this governance issue)
- The CLA question (see this other governance issue; may mostly be resolved by the automated CLA stuff?)
- Working Groups: do we have the right ones and are they staffed appropriately?
- Are there other gaps in the project's needs? If so, how do we recruit to fill them?
- Review recent move to Jira to confirm it's complete & documented appropriately
- Improve Developer Diversity
- Customers (carriers, enterprises) that are using the code, but not contributing
- Establish community metrics
- See Community Metrics for 2019
- See the marketing working groups current idea list
- Grimoire
- Stackalytics
- Determine which tools to expose those metrics
- Stackalytics
- Grimoire
- Internships/outreach for developers
- GSoC (in progress)
- Google Code-In
- Outreachy
- Rails Girls Summer of Code
- LF interns
- Others?
- How to get more community members and endusers of TF to provide developer resources?
- Internships/outreach for networking/system engineers
- NANOG Hackathons
- IETF Hackathons
- Greater China engagement