[RFC] The way of Trac

[François Perrad]

I write this proposal after #parrotsketch on 2009-04-28.

Some properties of Trac :
* Trac doesn't handle dependence between tickets
* Milestone (in Roadmap) could aggregate some tickets
* Trac supports adding custom, user-defined fields to the ticket module
* Trac allows custom ticket queries

Trac Wiki
=========

1) www.parrot.org is dedicated to general topics, and trac.parrot.org
wiki is dedicated to developper
2) the wiki pages become out of date very quickly

I suggest to limit the usage of Trac Wiki :
 - few pages (1-3) that contains only links to a TOP 30 of most asked RTFM.
Link to item in www.parrot.org or link to current source for example
https://trac.parrot.org/parrot/browser/trunk/docs/project/release_manager_guide.pod
 - and few pages about external efforts like languages, mod_parrot, ...

So, remove most of the current pages.
Don't duplicate documentation (just link).

Trac Roadmap
============

I suggest two kind of milestone :
1) monthly release milestone with a fixed deadline (as currently)
2) milestone as task list (like IO, String, ...) with movable deadline
    * each task is a ticket
(so remove the current task lists in the wiki)

Note: a milestone could contain a text description,
but currently milestone is editable only by very few people.

During #ps, we could review the next montly release milestone
and task list milestones.

Trac Ticket
===========

I suggest to add 2 values for the field 'severity'
1) 'weekly_priority'
2) 'weekly_candidat' or 'please_increase'

Two reports for finding tickets with these 2 values must be created.

Before #ps, committers could set some tickets (their favorite or blocker)
with the 'weekly_candidat' priority. And add a rational as comment in
the ticket.

During #ps, a review is done with the report 'weekly_candidat'.
And some ticket could be promoted to 'weekly_priority'.

During the week, a contributor without task could use the report
'weekly_priority'
and becomes the owner of an unassigned ticket.


François