[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pdf-devel] Hackers: flyspray tasks status update.
|
From: |
jemarch |
|
Subject: |
Re: [pdf-devel] Hackers: flyspray tasks status update. |
|
Date: |
Fri, 15 May 2009 15:32:30 +0200 |
|
User-agent: |
Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shijō) APEL/10.6 Emacs/23.0.92 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
> I'd like to ask you to change the status to STARTED for every task
> you have assigned. In case you are unable to work on it, someone
> could take over it if you leave it unassigned again.
>
> Please note that there are some situations where it makes sense to
> have a NEXT task assigned: some tasks may depend on another tasks.
>
I'd mark them as TODO in that case, the rules could be:
1. TODO and unassigned: dependency issues, no one in charge.
2. TODO and assigned: dependency issues and someone showed interest.
3. NEXT and unassigned: can be started, nobody interested.
4. NEXT and assigned: someone is interested but can't work on it for
personal
issues.
5. STARTED and assigned: someone is working on the task (no matter the
time
it takes)
Seems reasonable. I just drop a note about this in the hackers guide.
--
Jose E. Marchesi
address@hidden
GNU Project
http://www.gnu.org