Page History

For now, this is just a brainstormed list for purposes of discussion. It's not in any particular orderThis is our proposed draft of 2019 priorities in order of importance.

Initial discussion began in this mailing list thread.

1. 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)
2. 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
   • Stacking up TF (especially for newcomers)
     • devstack-like experience for developers who want to contribute
     • Katacoda demos
3. 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
4. Improve Developer Diversity
   
   • Customers (carriers, enterprises) that are using the code, but not contributing
   • Establish community metrics
     • See the marketing working groups current idea list
       • 2019 Marketing WG Goal Brainstorming
     • 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

...

• 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
• Stacking up TF (especially for newcomers)
  • devstack-like experience for developers who want to contribute
  • Katacoda demos

...

• TSC: please try to get all comments in this week!

...