The following is a first stab in terms of establishing guidelines and a workflow for open drupal development. As this is coming from somebody whose never 'properly' spec-ed out/managed a project, input/ideas from the experts are strongly encouraged.
Define the project
It will be important for the “open” projects to get the requirements nailed down as much as possible prior to work beginning. This will make the apprentices more efficient and will help with keeping track of time.
- Break down the project as if it was a traditional client job
- Even if the client is internal 'such as Drupal-dojo', have
people assume the client role (will help people learn from real world
situations)
- Plan, Gather Requirements, spec out, apply milestones
- Create a collaborative workshop for each major issue or task
- An introductory videocast for to set up each issue or task
- Collaborate/workshop Drupal Dojo style (live over vnc, skypecast, irc)
- Document each step of the process with documentation, videocasts, and podcasts
- An introductory videocast for to set up each issue or task
Assemble team
Create roles and delegate tasks. Roles would vary depending on nature of the project.
- Core team
- assemble a core team that would be responsible for managing/fulfilling the project
- compensated at a competitive non-profit rate
- Apprentice
- would be compensated w/ $$ or swag (would be up to the apprentice)
- some sort of merit reward for each task
- Mentor
Interact with Drupal
Utilize the Drupal support and infrastructure wherever applicable
- enable a means for Drupal and the community to engage, learn, and participate (will vary depending on the client and/or project)
- Open up channels of communication/collaboration with Drupal, Drupal Dojo, and other related efforts.
- Set up the appropriate project on drupal.org.
- set up a development environment that will be conducive to collaboration
- Connect and collaborate with other Drupal working and regional groups
Comments
Comment #1
add1sun CreditAttribution: add1sun commentedAside from project specific details I think we need a process set up for:
a) how can people present projects for consideration (especially what parameters will we put on ones we'd even consider)?
b) how do we choose which ones to do?
c) do we ensure a project would be completed? What is possible fallout if it isn't?
Comment #2
gusaus CreditAttribution: gusaus commentedSeems like this is related to this 'meta' discussion:
http://groups.drupal.org/node/7999
Comment #3
add1sun CreditAttribution: add1sun commentedProject is abandoned. Closing all issues.
Comment #4
gusaus CreditAttribution: gusaus commentedThis task is being hashed out here - http://groups.drupal.org/node/8051
Comment #5
gusaus CreditAttribution: gusaus commentedComment #6
gusaus CreditAttribution: gusaus commented