[GRASS-dev] GRASS at GForge first steps

[Maciej Sieczka]

Maciej Sieczka wrote:
> Maciej Sieczka wrote:
>> Hamish wrote:
>>> Maciej Sieczka wrote:
>>>> Issues tracker is for bugs, defects, wishes. I will take care of it in
>>>> terms of sorting out bugs which are doubtfull or lacking information.
>>>> I can also fix some minor stuff like docs, typos in the code, shell
>>>> scripts etc..
>>> why not a separate tracker for bugs, wishes, docs, website, install
>>> probs... then people who want to work on fixing docs but not C code can
>>> quickly see that there are 3 open doc bugs they can work on, instead of
>>> spending a lot of time going through 56 open bugs of all types to find
>>> any doc ones.
>> Good point. I'll separate them. Maybe today. If not - next days.
> 
> Hamish,
> 
> I forgot there is a "Build query" feature for each tracker.

In a discussion offlist I have agreed with Hamish that having separate
trackers for code, doc and web issues is a good thing - improving the
chance that a volunteer will easily find an issue to work on that suits
his skills and attitude. Moreover, keeping them separate will make it
easier to assign a dedicated maintainer to each tracker.

Note that tickets can be moved between the trackers using the "Data
Type" field, but only by the tracker admins; this forced me to enable
admin access to trackers for all "developers". This is necessary eg. if
a code bug turns out to be a doc wish :).

Please everybody take a look at trackers at the GRASS GForge and let me
know what you think, http://wald.intevation.org.



Berhard,

Should I fill in a wish to enable Techs to move the tickets between the
trackers? Or maybe you can fix it? Currently there is some risk that
somebody can accidently screw things.

Maciek