Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
We gathered recommendations on this topic through a TST meeting, multiple CST meetings, blog post and mailing list discussion.
Reorganize wiki content structure and create owners for each section responsible for that content
Build up a documentation community through community calls, docs mailing list, docs Slack channel, etc.
- Make better use of Confluence wiki tool (for instance, use tags for pages that need edits so it is easy to have list of pages to work on)
Have section on wiki showing new edits
Hackathon type events on wiki each quarter
- Prioritize creating an API Guide for the wiki
Create a user guide
Can documentation be baked into the code base somehow -- coding and documenting feel separate today (bonus: docs are versioned along with code) - is this a better way for people to consume though?
Find way to connect information – content is often there but fragmented and spread across YouTube, wiki, Slack, etc
Put more ideas for how to improve documentation and review technical procedures here
...
We gathered recommendations on this topic through a TST meeting, multiple CST meetings, blog post and mailing list discussion.
Improve and expand the module ownership system which has already helped remove ON.Lab staff from code review bottlenecks and provide more incentives around reviewing to encourage people to do more of it
Launch the ONOS Ambassadors program to identify people who can run, organize and speak at events that have required staff presence in the past
Create a formal projects lifecycle process to allow anyone to create a project independently without needing TST’s involvement
- Put more ideas for how to avoid having ON.Lab become a bottleneck here
...