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.
...
We need to have better documentation and review technical procedures
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.
Have section on wiki showing new edits
Hackathon type events on wiki each quarter
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 need to avoid ON.Lab staff becoming a bottleneck
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
We need to reduce barriers to contribution
We gathered recommendations on this topic through a TST meeting, multiple CST meetings, blog post and mailing list discussion.
- Review the times of all community meetings to make sure communities around the world can attend. For instance, the TST meeting at 3 pacific is too late for Europe and too early for Asia – perhaps the meeting could alternate between an earlier time (maybe 10 pacific) and a later time (perhaps 4 or 5 pacific) so that community members in Europe and Asia have a chance to attend
Create an onboarding experience so people don’t have to figure out so much on their own
Create a mentorship system to share information that is tacit
Create a system of asynchronous decision making so people who miss a call still have a chance to have a voice in decisions
Put testing in place to make sure existing processes are working (for example, current registration system breaks regularly and we don't always detect failures quickly)
- Put more ideas for how to reduce barriers to contribution here