Page History

...

We gathered recommendations on this topic through a TST meeting, multiple CST meetings, blog post, Twitter 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
  • Next steps: The TST meeting times have changed and it now alternates between early pacific time and late pacific time to be more friendly to European and Asian community members.  Other meetings can be moved as needed, although there is no ideal solution to the time zone scheduling issue – we'll also need to move to more of an asynchronous decision making model (see below) to fully reduce time zone barriers.

• Create an onboarding experience so people don’t have to figure out so much on their own

• Create a mentorship system

  • Next steps: Proposal to TST to expand role of module owners to include mentoring as well as code reviewer.  Launching Ambassador program will also officially designate people to be community mentors

• 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)

• Put more ideas for how to reduce barriers to contribution here