Now that we're set up as a drupal project we probably should set up some roadmaps and guidelines. The incredibly successful GHOP project should provide a very nice framework for how we set things up. Anyone care to help hash out a process?

Relevant GHOP pages:
* How to write a good task - could a similar set of guidelines/template work for Dojo?
* Instructions on how to submit a task idea - similar thing for dojo lessons, tasks and workshops?
* Notes for administrators - A lot of these ideas/examples might work mentors and ninjas? These also are guidelines on how folks in the Dojo could help.

Possibly this type of thing IS something we could submit as a GHOP task? Curious to get some thoughts.

Comments

add1sun’s picture

add1sun commented
Component: Code » Documentation

Well first we need to figure out all of our moving pieces. Hopefully we can talk out the dd.com features and get a first round set by mid January-ish. We already know what g.d.o and d.o offer us. Then we can sketch out the workflow we envision for these things (using dd.com/d.o/g.d.o - ugh) and adjust/tweak accordingly.

I don't think we are not going to have enough in place to work from in time for a GHOP student to document any of this unfortunately.

gusaus’s picture

gusaus commented

Points well taken - having said that, it's looking like we're already getting some good feature requests (yet, we need more, people):
http://drupal.org/node/201891

Possibly we can take a look at the GHOP task format as something that would work for Drupal Dojo.

GHOP Template for submissions

  • Title
    • A short description of what the task entails
  • Description
    • An initial sentence or two that describes what the task entails and the value prop (emphasize importance to project, transferable skills...).
    • Several sentences/bullets that provide more detail into the task: What approach should students use? What level of detail are you looking for?
    • A sentence about what the expected deliverable is (a tutorial reviewed by at least one member of the documentation team and posted to the handbook, a patch in the core issue queue marked ready to be
      committed...)
  • Resources
    • Bulleted list of resources specific to the task.
    • This includes handbook pages, off-site resources, IRC channels, related groups on groups.drupal.org, etc.
  • Estimated time - a "day" range of how long you think the task will take to complete
  • Primary contact
    • The person we should list as the "owner" of the task, who will monitor student submissions and give the final sign-off.
    • This should be either you or someone who you've talked to about taking this on.

Possibly this template could be the basis for our own CCK type?
http://drupal.org/node/202086

RE: Working with the GHOP project? Well... possibly the DrupalDojo can carry the flame when the GHOP project ends.

gusaus’s picture

gusaus commented

Related issue posted here - http://drupal.org/node/207042. Should we consolidate?

gusaus’s picture

gusaus commented
Status: Active » Closed (duplicate)
gusaus’s picture

gusaus commented
Title: Create guidelines on how to submit lesson, task, and project ideas » Create guidelines on how to define and scope out projects and tasks
Priority: Normal » Critical
Status: Closed (duplicate) » Active
Issue tags: +guidelines, +kata

Created a project template largely based on this years Summer of Code - will customize based on feedback in this thread -
http://groups.drupal.org/node/22361

gusaus’s picture

gusaus commented
Issue summary: View changes
Status: Active » Closed (outdated)