<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="+1"><font face="FreeSerif">As a new contributor it would be
very helpful to me to be able to see upcoming jobs that need doing, so
that whenever I have a couple of hours spare I can just pick something
up. As this is my first release cycle I find John's schedule a little
too general at times - it would be great to have a more detailed list
of subtasks.<br>
<br>
Nathan<br>
</font></font><br>
On 19/03/10 01:16, Karsten Wade wrote:
<blockquote cite="mid:20100319011636.GR5501@calliope.phig.org"
type="cite">
<pre wrap="">On Thu, Mar 18, 2010 at 07:31:44PM -0400, Paul W. Frields wrote:
</pre>
<blockquote type="cite">
<pre wrap="">back. Here are a couple of problems it might help us solve:
</pre>
</blockquote>
<pre wrap="">
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
</pre>
</blockquote>
</body>
</html>