Drupal Open Learning: Roles, Responsibilities, Benefits, and Incentives

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

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
    • Project funds - TBD % of each project will be allocated as overhead

Technology

Activities pertaining to production of tools and technology.

  • Roles
    • Project Manager
    • Designer
    • Themer
    • Developer
    • Tester
    • Technical communicator
    • Infrastructure
  • Budget/Funding sources - Cost should be estimated on a per project basis at a client rate.
    • Sponsors will have the option to fund the program and/or any particular project.

Production

The Drupal Open Learning Initiative will create a media education program to compliment the Drupal Dojo. After the initial period, all activities pertaining to production and content creation will be funded through the media program.

  • Roles
    • Multimedia Producer
    • Editor
    • Writer
    • Event producer
  • Budget/Funding sources - This cost will initially be part of the funds raised for the pilot program
    • Direct funding via Individual donations, Corporate sponsorships, Grants
    • Project funds - TBD % of each project will be allocated as overhead

Mentors, Apprentices, and Volunteers

Apprentice

  • Roles/responsibilities
    • the apprentice is ultimately responsible for completing their project or task
    • the task or project will vary from simple bug fixes, documentation, to working on real projects
  • Benefits
    • stipend (if applicable) will depend on the nature of the role (development, design, business, etc.), level of expertise, and involvement in the project
  • Skills required
    • a desire to learn and pick up new skills
  • Number of apprentices required
    • As many as possible!
  • Time Commitment
    • Actual time requirement will vary depending on the scope of the project. But plan on roughly ~10-30 hrs/week

Mentor

  • Roles/responsibilities
    • be a resource person for your apprentice
    • helping them to scope out their project, making sure it's staying on track
    • communicating with the organization administrators.
    • On a day-to-day basis, you might be doing code reviews, helping the apprentice to find resources that will help them over hurdles, or helping to shepherd a young contributor in the ways of the Drupal Ninjas.
  • Benefits
    • stipend (if applicable) will depend on the nature of the role (development, design, business, etc.), level of expertise, and involvement in the project; this will often times be determined by the level of expertise/involvement of the apprentice.
  • Skills required
    • Competent/Advanced skills in the area of your expertise
    • Kindness, patience, and being good at explaining things.
    • Extra bonus if you've mentored a successful student before!
  • Number of mentors required
    • As many as possible!
  • Time Commitment
    • Actual time requirement will vary dramatically by apprentice/project. But plan on roughly ~10 hrs/week

Project Idea Curators

  • Roles/responsibilities
    • find faults (in a nice way) with proposals
    • If what they propose duplicates another project or is too vague, let them know
    • give advice on how they might change it to fit in more with the community's needs.
  • Benefits
    • stipend tbd
  • Skills required
    • Kindness, patience, a critical eye
  • Time Commitment
    • ~ .5 hour per proposal

Project Idea Thinker Uppers

  • Roles/responsibilities
    • propose projects and tasks valuable to the Drupal community
  • Benefits
    • code!
  • Skills required
    • An itch, and the ability to communicate how you want it scratched.
  • Number of volunteers required
    • As many as possible!
  • Time Commitment
    • ~2-3 hours per proposal

Comments

Similarites and differences to GSOC and GHOP

gusaus's picture

While inspired by the Google programs, the Drupal Kata, hopes to provide additional flexibility and benefit to the community and those who participate. Key differences are as follows:

  • We're not relying on a particular program to complete a project (i.e. Google or Knight may be potential funding sources, but not the only one);
  • There must be the proper incentives for the mentors, project leads, producers, and administrators to ensure the program is sustainable and projects are completed up to spec.
  • Apprentices would only receive stipends for successful completion of the project or task. In utilizing the FossFactory model (http://www.fossfactory.org/), sponsors would only be rewarding something that was completed up to spec.

Similar to a traditional development shop we need to build the admin/overhead into the cost of a project. To do this, it seems, a project would be spec'ed out at a standard rate ($100/hr) w/ a % allocated to fund the overhead, the mentors, and the apprentices. Never having worked at a successful shop, I'm hoping others could provide ideas in terms of a base rate and how project funds could be allocated. What should apprentices receive for completed work? What about benefits/stipends for others? How many man hours/month will it take to administer the program?

Gus Austin
PepperAlley Productions

Gus Austin

gusaus's picture

Qualified people in these roles can be the difference in a project/programs success or failure. Beginning with the pilot project, we would like to provide opportunities for apprentices to pick up these valuable skills. How exactly this should work is up in the air. Suggestions on a process, incentive structure, and how to get mentors involved, are highly encouraged.

Gus Austin
PepperAlley Productions

Gus Austin

Regional teams

gusaus's picture

Ideally these teams could come together on a local level. Benefits to local interaction would be very similar to what's illustrated in this GSoc post.

Gus Austin
PepperAlley Productions

Gus Austin

Stipends only if applicable

gusaus's picture

My feeling (at least at this moment) is it might be best to provide a a good set of guidelines and the tools that would enable the owners/managers/producers of a given Kata project control of how they want to fundraise and offer incentives. If we can keep the overhead to a minimum, it should be easier to cover that cost and we'd stay out of the issues that might comes with dictating a standard incentive structure.

If that seems like a logical way to start, we still need to determine that costs/time resources for ongoing administration. Any thoughts on the cost and roles/skills we need?

Gus Austin
PepperAlley Productions

Gus Austin

Non monetary incentives such as belts

gusaus's picture

Belts as a measurement of apprentice achievement was something discussed back when the Dojo started - http://groups.drupal.org/node/2195#comment-5799. Better late than never - possibly it's something we should define. Anyone want to take a stab at it?

Gus Austin
PepperAlley Productions

Gus Austin