A page to post the findings of the 2016 community survey and to list the actions proposed to address concerns raised in findings.
The community survey identified four areas for us to focus on improving:
We need to increase transparency
We need to have better documentation and review technical procedures
We need to avoid ON.Lab staff becoming a bottleneck
We need to reduce barriers to contribution
More details about the findings can be found at:
We gathered recommendations on this topic through a TST meeting, multiple CST meetings, blog post, Twitter and mailing list discussion.
Look into etherpad as way to do collaborative note taking
Put more ideas for how to increase transparency here
We gathered recommendations on this topic through a TST meeting, multiple CST meetings, blog post, Twitter 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 gathered recommendations on this topic through a TST meeting, multiple CST meetings, blog post, Twitter 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
We gathered recommendations on this topic through a TST meeting, multiple CST meetings, blog post, Twitter and mailing list discussion.
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 (for exampe, a TST meeting can discuss and propose a decision and then after posting about this to the mailing list and allowing time for feedback the decision could then be formalized).
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)