Guidelines

Drupal Open Learning is a project-based learning program that provides training in a wide range of areas ranging from site planning, drafting proposals, project management, information architecture, development, design, infrastructure, to Drupal workflows and community. It does this by pairing apprentices with a mentor or mentors, thus gaining exposure to real-world scenarios and connections with the local and global community.

All approved apprentices will be asked to keep track of the pertinent details about their project in a central wiki page on this group. The following is a template for them to use to do this.

Project information

Project page on drupal.org: http://drupal.org/project/FOO
Apprentice: Joe Sock (socks on d.o, socks@drupal.org on g.d.o)
Mentor: John Daff (J.D.)
Co-mentor(s): Jane Guru (guru)
Local mentor(s):

Current status: Describe briefly where your project is this week. Are you in the process of scoping? Are you working on a particular deliverable?

Description

A brief summary of your project and why it's awesome, with links off to further relevant information (the original public discussion, your full application, etc.) if you'd like.

The following roles, responsibilities, and benefits are being defined during the initial stage of the Drupal Open Learning Initiative.

Operations

The following activities are necessary to keep both the program and associated website(s) operational and sustainable.

• Roles
  • Program Management
  • Business and Strategy
  • Fundraising
  • Marketing and Outreach
  • Documentation
  • System Administrator
• Budget/Funding sources
  • Direct funding via Individual donations, Corporate sponsorships, and Grants

Let's try to define our core values, rules of the road, dos and dont's. Here are a few ideas - please question, comment, clarify and/or add your own...

The following is a first stab in terms of establishing guidelines and a workflow for open drupal development. Ideally we can use this wiki (and discussion thread) to hash out a process for the Dojo 2.0. (issue here) and other collaborative projects. This process is geared more towards building a complete site from start to finish.