[GRASS-dev] GRASS at GForge first steps

Martin Landa landa.martin at gmail.com
Sat Nov 4 17:48:02 EST 2006

Hi Maciek,

2006/11/4, Maciej Sieczka <tutey at o2.pl>:


> Patches tracker is for storing and managing the patches candidates
> (both code and docs). Currently, they are often sent to dev list. If
> they are not reacted upon quickly, or too intrusive to be applied right
> away but valuable for future developmement, they happen to be
> forgotten. The tracker might help us to manage them in a convenient
> way. Jachym volunteered to maintain the code patches submitted. Thanks
> Jachym! Is there somebody willing to take care of docs submitted?

I can do it (not sure whether I am the right person for managing docs...)


> GForge provides many functionalities. AFAIK, it was aggreed that we are
> currently going to use only the Trackers, as all the other
> functionalities are implemented in the current GRASS infrastructure
> (besides surveys, which I discuss later in this mail). Thus, although
> there are various project member Roles possible to define, IMHO we
> should only use 3: admin, user and developer:
> 1. Admin is in charge of accepting requests to join the project and
> configuring the GRASS project at GForge. Currently I'm the only admin.
> We need 2 (3?), in case I'm not available. Candidates?

+1 (if needed, BUT no experience with GForge)

> 2. Developer can do most of the things that admin can. Only that he
> doesn't have his duties and he can't remove the whole project,
> add/modify/delete trackers. He also can't delete a ticket permanently -
> only the admin can. I think such restrictions are sane - getting
> familiar with GForge options takes some time, and we don't want
> accdental corruptions. Eg. I happened to remove a tracker by accident
> when learning GForge. And I'm definitely not an expert yet.
> 3. User. He can open new tickets in the trackers and participate it
> surveys (Admin and developer can too, of course).
> Talking of surveys - Jachym suggested using this nice GForge feature.
> Any GRASS project member at GForge can vote on the survey. Admin can
> access the survey results, and create new ones. I was wondering if
> GRASS folks find it usefull. Thus, I have created a survey for that :)
> [7]. Opinions? The possible problem I see is that only admin can access
> the survey results :(, and there is no way to change this (CCing
> Bernhard if he has an idea). You can see an example results in the
> picture attached (I accidently voted twice - as admin and as a testing
> user).
> GForge manuals are here: [6].
> [1]http://wald.intevation.org/tracker/?atid=182&group_id=21&func=browse
> [2]http://wald.intevation.org/tracker/?atid=183&group_id=21&func=browse
> [3]http://wald.intevation.org/account/register.php
> [4]http://wald.intevation.org/projects/grass/
> [5]http://wald.intevation.org/project/request.php?group_id=21
> [6]http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1

Best regards, Martin

Martin Landa <landa.martin at gmail.com> * http://gama.fsv.cvut.cz/~landa *

More information about the grass-dev mailing list