A page to post the findings of the 2016 community survey and to list the actions proposed to address concerns raised in findings.

Findings

Recommended Actions

We gathered recommendations on this topic through a TST meeting, blog post and mailing list discussion.

Move off of Google Hangouts as a videoconference system since it is inaccessible to community in China and to people in some organizations
Post a Roadmap page on the wiki that contains an easy to find list of upcoming features and how to get involved with each
Post notes of key meetings in addition to video or audio recordings of those meeting since people don't tend to watch an hour long recording of a meeting (for instance, the recording of the March 30 TST meeting has 56 views as of May 18 and that equals 6% of the 914 subscribers of the onos-dev mailing list that is the relevant audience for this content). Also provide a window of time for people who missed the meeting to read the notes and respond to them before making a decision about a topic (so a discussion at a TST meeting could propose a decision and then after feedback on the list the decision could be formalized).
Put more ideas for how to increase transparency here

Implement a module owner system for docs on the wiki to make sure everything there is owned by someone
Put more ideas for how to improve documentation and review technical procedures here

Improve and expand the module ownership system which has already helped remove ON.Lab staff from code review bottlenecks
Put more ideas for how to avoid having ON.Lab become a bottleneck here

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
Put more ideas for how to reduce barriers to contribution here