task tracking

Karsten Wade kwade at redhat.com
Fri Mar 19 01:16:36 UTC 2010


On Thu, Mar 18, 2010 at 07:31:44PM -0400, Paul W. Frields wrote:

> back.  Here are a couple of problems it might help us solve:

Heck, if people want to keep notes on paper about what they are doing,
they'll still get work done.

My focus is on enabling other, new or returning people at
participating.

Whatever makes a visible task list with _visible_holes_ is my main
goal in this thinking.  If a wiki list is going to bitrot, then
something else.

Central task tracking also means, if someone has to disappear or gets
eaten by a raptor, we can help support them and the project with a
visible list of assigned tasks.

And, yeah, I don't dig bugzilla as a task tool, but it's great for
content bugs.  Trac is where you take 1 bug and generate N individual
work items for individual people.  Doing that in bugzilla is highly
sub-optimal and not trivial.

- Karsten
-- 
name:  Karsten 'quaid' Wade, Sr. Community Gardener
team:                Red Hat Community Architecture 
uri:               http://TheOpenSourceWay.org/wiki
gpg:                                       AD0E0C41
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/docs/attachments/20100318/e846fd7a/attachment.bin 


More information about the docs mailing list