[GRASS-dev] Bugtracker: Changing to GForge Platform?

[Patton, Eric]

Jan,

This seems to be a much nicer interface overall. I like the color-coding of
priority levels as well. How difficult would it be to migrate old bug
reports over to GForge? 

~ Eric.

-----Original Message-----
From: grass-dev-bounces at grass.itc.it
To: 'grass-dev at grass.itc.it '
Sent: 9/26/2006 6:10 PM
Subject: [GRASS-dev] Bugtracker: Changing to GForge Platform?

Hi GRASS Developers,

at FOSS4G in Lausanne I talked to Markus and about the
GRASS  development infrastructure he said the thing
that hurts most is the bugtracker.

What we could do instantly is:
create a project "GRASS" at our GForge platform
http://wald.intevation.de
and start with just the bugtracker.

This would basically solve two problems:
- attachments for bug reports work
- management of user accounts through GForge
  and could be delegated to any GRASS developer

You can look at the bugtracker here:
 http://wald.intevation.org/tracker/?group_id=6
It is the one of Thuban, the wxPython desktop GIS.

Comments, suggestions welcome.

All the best

	Jan
-- 
Jan-Oliver Wagner: www.intevation.de/~jan  | GISpatcher:
www.gispatcher.de
Kolab Konsortium : www.kolab-konsortium.de | Thuban    :
thuban.intevation.org
Intevation GmbH  : www.intevation.de       | Kolab     : www.kolab.org
FreeGIS          : www.freegis.org         | GAV       :
www.grass-verein.de

_______________________________________________
grass-dev mailing list
grass-dev at grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev