Re: [Monotone-devel] Project Management

[Rob Schoening]

even without any tools, a one-page roadmap that identifies upcoming releases and identifies features/fixes as targeting one release vs. another would be very nice.  my guess is that this kind of basic plan would do more for adoption of monotone than most features would.

 

* no need to commit to schedule

* no need to assign tasks

* no need to introduce any ceremony

 

just a statement of broad consensus among developers and users about the road ahead.

 

but maybe Graydon is right.  maybe some of us just see monotone as something more than he, and others, do.

 

RS
 

On 7/19/06, Thomas Moschny < address@hidden> wrote:

On Wednesday 19 July 2006 23:26 wrote Thomas Keller:
> [...]
> should help giving these people a top view of the project's status, like
> what features are planned for which version, what is currently been
> worked on, and how things are planned to be incorporated into the code,
> all this. This would also give interested people a good view on where
> the project is heading in the future.

Well, by no means I am trying to push something, but the use of an integrated
wiki/bugtracker/sourcecode browser might help a bit here.

With Trac for example, you can declare milestones, i.e. planned future
releases and assign them to bug reports or feature requests, thus giving
people an idea of what the next and what future steps will be. Additionally,
treating almost everything as wiki text and providing links to wikipages,
tickets as well as revisions aids in providing a good overview of a project's
status.

- Thomas

--
Let's say the docs present a simplified view of reality...    :-)
            -- Larry Wall in  < address@hidden>


_______________________________________________
Monotone-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monotone-devel