Changes between Version 10 and Version 11 of org/process/HowWeDoProjectManagement


Ignore:
Timestamp:
Jun 24, 2011, 8:37:35 AM (8 years ago)
Author:
karsten
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • org/process/HowWeDoProjectManagement

    v10 v11  
    4444== What's the workflow here? ==
    4545
    46 First, we realize there needs to be a project.  This could be as formal as a funder listing a deliverable on a contract, or as informal as a developer thinking, "You know, some day BridgeDB should be able to give out bridges over SMS."  At this point, you add an entry to the appropriate product's list of projects on [wiki:org/projects] or one of its subpages.  (If it's a tiny enhancement that can get done in a single task, you could also instead add a trac ticket to the appropriate component.)
     46First, we realize there needs to be a project.  This could be as formal as a funder listing a deliverable on a contract, or as informal as a developer thinking, "You know, some day BridgeDB should be able to give out bridges over SMS."  At this point, you add an entry to the appropriate product's list of projects on [wiki:org/roadmaps] or one of its subpages.  (If it's a tiny enhancement that can get done in a single task, you could also instead add a trac ticket to the appropriate component.)
    4747
    48 At some time before the project becomes active, it should get a new trac ticket for it.  The trac ticket should be named something like "Project: Add Haskell support to Tor."  Link to the trac ticket from the appropriate [wiki:org/projects] subpage.  This is the master ticket for the project.  If it has a due date, assign it to the appropriate milestone.  In its description, add the following code: "[[!TicketQuery(parent=#'''NUM''')]]", where '''NUM''' is the number of the ticket.  This will insert a list of all the child tickets.  If you know the steps needed to finish the project, add them as new tickets, and set their parent id to the master ticket for the project.
     48At some time before the project becomes active, it should get a new trac ticket for it.  The trac ticket should be named something like "Add Haskell support to Tor."  Set the ticket type to "project," and it will be linked from the projects overview section on [wiki:org].  This is the master ticket for the project.  If it has a due date, assign it to the appropriate milestone.  In its description, add the following code: "[[!TicketQuery(parent=#'''NUM''')]]", where '''NUM''' is the number of the ticket.  This will insert a list of all the child tickets.  If you know the steps needed to finish the project, add them as new tickets, and set their parent id to the master ticket for the project.
    4949
    5050A project ticket should contain, at minimum: