[GRASS-dev] GRASS at GForge first steps

Maciej Sieczka tutey at o2.pl
Sun Nov 5 07:00:05 EST 2006

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.


I forgot there is a "Build query" feature for each tracker. Every
project member can create any number of queries suiting his needs. You
can create a query for open bugs, docs, etc. Wouldn't that be good
enough, instead of separate trackers?

You can create a few testing tickets and see how it works for you (I
have disabled forwarding GRASS project GForge traffic to the dev list
until we have it working properly, so don't hesitate). Same for patches


More information about the grass-dev mailing list