|
# How we do project management
|
|
# How we do project management - WIP
|
|
|
|
|
|
This page explains how we keep track of our ongoing tasks in the Tor Project.
|
|
This page explains how we keep track of our ongoing tasks in the Tor Project.
|
|
|
|
|
... | @@ -7,7 +7,7 @@ Project management as described here serves a few different purposes: |
... | @@ -7,7 +7,7 @@ Project management as described here serves a few different purposes: |
|
* Paid developers want to keep a handle on what their actual current tasks are, and what everybody else is working on.
|
|
* Paid developers want to keep a handle on what their actual current tasks are, and what everybody else is working on.
|
|
* Volunteer developers and researchers want to know about interesting tasks that we want to get done, but which we _aren't_ actually working on.
|
|
* Volunteer developers and researchers want to know about interesting tasks that we want to get done, but which we _aren't_ actually working on.
|
|
* Users want to know what we're working on, and what they can do to help us.
|
|
* Users want to know what we're working on, and what they can do to help us.
|
|
* Funders want to stay apprised of how well we're doing at meeting our promises to them, without having to read trac ticket updates or git commits.
|
|
* Funders want to stay apprised of how well we're doing at meeting our promises to them, without having to read trac ticket updates or git commits.
|
|
|
|
|
|
Notes: Some of this is document is _aspirational_ as of July 2010: we aren't yet following this process throughout our whole organization. Also, this document is a **draft**: it represents our current best ideas on how to do this, but we are still refining those ideas. See the [page for the project to set up this system](./org/process/SetUpProjectMgt) for open questions, status on converting things to use this system, and so on.
|
|
Notes: Some of this is document is _aspirational_ as of July 2010: we aren't yet following this process throughout our whole organization. Also, this document is a **draft**: it represents our current best ideas on how to do this, but we are still refining those ideas. See the [page for the project to set up this system](./org/process/SetUpProjectMgt) for open questions, status on converting things to use this system, and so on.
|
|
|
|
|
... | @@ -20,11 +20,11 @@ There are different kinds of projects. Some projects represent _external commit |
... | @@ -20,11 +20,11 @@ There are different kinds of projects. Some projects represent _external commit |
|
|
|
|
|
Projects involve creating or enhancing some **products**. Most of our **products** are programs, but some (like the website, or the company itself) aren't.
|
|
Projects involve creating or enhancing some **products**. Most of our **products** are programs, but some (like the website, or the company itself) aren't.
|
|
|
|
|
|
Projects are divided into **tasks.** Each **task** should represent a comprehensible unit of work that can get done in a matter of hours or days. Example tasks for "Make Tor support UDP" might be "write a specification for ".
|
|
Projects are divided into **tasks.** Each **task** should represent a comprehensible unit of work that can get done in a matter of hours or days. Example tasks for "Make Tor support UDP" might be "write a specification for ".
|
|
|
|
|
|
There are a few ways we represent projects, depending on their status:
|
|
There are a few ways we represent projects, depending on their status:
|
|
* Every **active** project should get represented by a trac ticket linked from [org/projects](org/projects) or one of its sub-pages listing the projects for a particular product. All significant to-do items for a project should be child tickets of the main project ticket.
|
|
* Every **active** project should get represented by a trac ticket linked from [org/projects](org/projects) or one of its sub-pages listing the projects for a particular product. All significant to-do items for a project should be child tickets of the main project ticket.
|
|
* Really complex projects can also get a wiki page with a name like org/projects/ShortProductName/DescriptionOfTheProject for figuring out the work plan. Serious design should still get discussed on or-dev, though, or via the proposal system.
|
|
* Really complex projects can also get a wiki page with a name like org/projects/ShortProductName/DescriptionOfTheProject for figuring out the work plan. Serious design should still get discussed on or-dev, though, or via the proposal system.
|
|
* Blue-sky projects and projects that aren't ready for action can be represented by a single line on the list of projects.
|
|
* Blue-sky projects and projects that aren't ready for action can be represented by a single line on the list of projects.
|
|
|
|
|
|
|
|
|
... | @@ -57,4 +57,4 @@ Next, we create tasks and milestones, linking them from the project page. XX say |
... | @@ -57,4 +57,4 @@ Next, we create tasks and milestones, linking them from the project page. XX say |
|
|
|
|
|
(Note: There is no mention of milestones above.)
|
|
(Note: There is no mention of milestones above.)
|
|
|
|
|
|
Then, we start working on the thing, checking off tasks as we go. XX say more. XX |
|
Then, we start working on the thing, checking off tasks as we go. XX say more. XX |
|
\ No newline at end of file |
|
|