[Dune] More flyspray permissions for contributors

Jö Fahlke jorrit at jorrit.de
Mon Jan 30 17:13:45 CET 2012


Am Mon, 30. Jan 2012, 15:20:38 +0100 schrieb Christoph Grüninger:
> Date: Mon, 30 Jan 2012 15:20:38 +0100
> From: Christoph Grüninger <christoph.grueninger at iws.uni-stuttgart.de>
> To: dune at dune-project.org
> Subject: [Dune]  More flyspray permissions for contributors
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929
>  Thunderbird/7.0.1
> X-Envelope-From: <christoph.grueninger at iws.uni-stuttgart.de>
> 
> Hi Jö,
> I think a user owns a task when the task is assigned to him. That's
> the reason why a basic user currently cannot change anything. One of
> the developers must assign a task to a basic user than he can close
> it - but that never happend.
> A proof for my guesswork: If you hover the button "assign to me" a
> part of the URL is "takeownership".
> 
> I am against your proposal that users should not create attachments.
> I hope that's only a mistake.

Indeed it is.  Users should of course be able to create attachments.

> - "View history": Left beside the tab "Comments" is a "history" tab,
> their you can watch what happend. That might prevent data loss if
> users cannot modify that we can get all data from there.

Having a look at it: This means you can access old data -- even stuff that has
been removed on purpose (e.g. because it turned out to be confidential).  So I
suppose Basic users shouldn't have this permission.

> I think it would be easier to create a new group contributors. To
> define contributors was already voted for on the last developer
> meeting in Münster. Someone creating patches for Dune wound not spam
> our Flyspray, would he?

I think bug handling should be as easy as possible for everyone as long as a
few things are observed:

1. It shouln't expose us to a high risk: don't give just anyone read access to
   data we don't want publicly available, don't let just anyone do stuff we
   cannot fix later (i.e. data loss), ...

2. Stylistic guidelines are observed: I would say don't edit old stuff but add
   new stuff at the end so discussion history is preserved, but that is just
   my taste and I open to discussion.

I suppose the Contributors group you propose is already covered by the
existing Developers group (You may note that there are some non-core
developers in there).  Please note that the flyspray permissions are
completely unrelated to the SVN permission.

So I would propose the following:

 - By default flyspray users are members of the bsic group.  They can do
   everything as long as it doesn't violate rules 1. and 2. above.

 - Developers are essentially free to do anything, even stuff that isn't
   easily revertable or that hides information.

Here are the particular rights I propose:

|                                              | Developers | Basic |
|----------------------------------------------+------------+-------|
|                              Project Manager | yes        | no    |
|                                   View tasks | yes        | yes   |
|                               Open new tasks | yes        | yes   |
|                             Modify own tasks | yes        | yes   |
|         Modify tasks that are not user's own | yes        | yes   |
|                                View comments | yes        | yes   |
|                                 Add comments | yes        | yes   |
|                            Edit own comments | yes        | no    |
|                                Edit comments | yes        | no    |
|                              Delete comments | yes        | no    |
|                           Create attachments | yes        | yes   |
|                           Delete attachments | yes        | no    |
|                                 View history | yes        | no    |
|                              Close own tasks | yes        | yes   |
|          Close tasks that are not user's own | yes        | yes   |
| Assign tasks to self if not already assigned | yes        | yes   |
|                 Assign others' tasks to self | yes        | yes   |
|                        Add self to assignees | yes        | yes   |
|                               View event log | yes        | yes   |
|                           Can Vote for tasks | yes        | yes   |
|                             Edit assignments | yes        | yes   |
|                            Show as assignees | yes        | yes   |
|                            Members can login | yes        | yes   |

Satisfied with this?  Or should we rename Developers into Contributors?

Bye,
Jö.

-- 
Jorrit (Jö) Fahlke, Interdisciplinary Center for Scientific Computing,
Heidelberg University, Im Neuenheimer Feld 368, D-69120 Heidelberg
Tel: +49 6221 54 8890 Fax: +49 6221 54 8884

This message is protected by DoubleROT13 encryption
Attempting to decode it violates the DMCA/WIPO acts
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20120130/62eb270c/attachment.sig>


More information about the Dune mailing list