Organizational and leadership structure

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
public

A common problem with an all-volunteer Dojo, has been that top contributors are the first ones to get hired and/or are too overloaded w/ work. We've also asked developers/teachers to churn out well produced learning materials and produce a very ambitious website. This again, puts a burden on those with very little time.

Even without a formal entity - an organization, leadership, decision making, and incentive structure will ensure that the Dojo and related efforts have the resources to make it stable and sustainable.

Production and marketing

The following is largely based on the Drupal Association. Since there is no official Dojo entity, this would be a collective of individuals. *Please note that the roles, responsibilities, and people are still being sorted out.

  • Communications director/producer - Gus Austin (http://groups.drupal.org/user/1915)
    • roles/responsibilities
      • Communicating our activities to the community, and for improving outreach in general.
      • Coordinates schedules and facilitates communication between the creative and technical teams.
  • Director of Education - Alex Urevick-Ackelsberg/Alex UA - http://groups.drupal.org/user/9424
    • roles/responsibilities
      • Develop curriculum
      • Plan, budget, and coordinate Workshops and Training
  • Business manager - TBD
    • roles/responsibilities
      • Defines strategies and objectives for both the short and long term.
      • Creates and manages budgets
      • Develops and controls strategic relationships with third-party companies
  • Technical project manager - TBD
    • roles/responsibilities
      • plan, budget, and coordinate technical projects (including the Dojo.com redesign)
  • Lead technical writer - Stacy Wray - http://drupal.org/user/379039
    • roles/responsibilities
      • Writes and/or edits original documentation.
      • Creates website, grant, and sponsorship proposals
      • Researches technical information.
  • Production manager - TBD
    • roles/responsibilities
      • plan, budget, and coordinate multimedia production (audio, video, interactive, etc.)
  • Infrastructure Manager - Mike Stewart (http://drupal.org/user/30158)

Training and Curriculum

Tracks or Dojos

Anything that would be considered a contribution to Drupal and adheres to the projects mission statement and principles should be considered appropriate Dojo curriculum. Most lessons, tasks, and projects should fit into the following categories, tracks, dojos(?) - each with their own set of leaders, mentors, and coaches.

Site building/code/development

Overview: Learn the latest techniques in site development. / simpletests, coding practices, scalability, deployment and so on.

Leads/Mentors/Coaches
Alex Urevick-Ackelsberg/Alex UA - http://groups.drupal.org/user/9424

Design and user experience

Overview: focus on the site builders, themers and those interested in delivering a killer user experience both for Drupal itself and for their own sites.
Leads/Mentors/Coaches
tbd

Core, contributions and trends

Overview: Keep up with the latest activities, and plans for the future of the Drupal project.

Leads/Mentors/Coaches
tbd

Marketing,  business and growing communities

Overview: showcases, case studies, industry discussions, discussions about the business of consulting, and the business of open source. / local community building and focus on efforts such as the Knight Drupal Initiative, Google Summer of Code and GHOP.

Leads/Mentors/Coaches
Gus Austin - http://groups.drupal.org/user/1915