[GRASS-dev] tracker write/read access at GForge

Bernhard Reiter bernhard at intevation.de
Fri Oct 27 04:06:42 EDT 2006

Hi Maciej,

On Monday 23 October 2006 22:37, Maciej Sieczka wrote:
> The trackers for GRASS at GForge are ready to be deployed and announced
> [1]. 


> There is one thing stopping me though. I believe that it should be 
> possible to have project members with no writing access for trackers.
> So that only selected members could modify and *delete* tickets
> sumbitted. 

Can you tell me more about the use case behind this user role?
In my opinion it is good to give a member of the team the right
to manipulate tracker entries as first permission.

> And although GForge seems to provide such option via setting 
> 'Read' access for a given 'Role', it doesn't work as I expect it. Even
> if I create a user with a 'Junior Developer' Role, who has only Read
> access for trackers, he is still able to delete and remove tickets as
> if he was an admin.
> I read the GForge manual [2], but found no answer. What's wrong (with me?)?

This could be a bug in the gforge software that we are running on wald.
Best is to add a report how to reproduce the problem to the
We already know a few shortcomings and work to overcome them.
Our next step will be to upgrade to a newer version of gforge,
for this we run staging tests first.
This is also the prerequisite for us to do further improvements
to the software.

Best Regards,

Managing Director - Owner, www.intevation.net       (Free Software Company)
Germany Coordinator, fsfeurope.org       (Non-Profit Org for Free Software)
www.kolab-konsortium.com   (Email/Groupware Solution, Professional Service)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20061027/a68e61bf/attachment.bin

More information about the grass-dev mailing list