Proposa noves funcionalitats
#DecidimRoadmap Dissenyant el Decidim entre totes
Is your feature request related to a problem? A clear and concise description of what the problem is.
Author = the user that created the initiative in the first place
Member = user that was accepted as a member in the promoter committee
Currently members have the same permissions as the author of the initiative. A member can send the initiative to technical validation (without a way to cancel) remove and accept other members. This creates a high level of uncertaintety around the process of drafting an initiatives. We added versioning so we can at least track changes made by everyone.
Here is an exhaustive permission table for members and authors : https://user-images.githubusercontent.com/11473995/101887291-f073f400-3b9c-11eb-8c74-e01925d55bf2.png
Describe the solution you'd like
We think that distinguishing the permissions of the initial author and the co-author would help solve this issue.
Here's the updated permission table that we propose implementing :
Describe alternatives you've considered
None
Does this issue could impact on users private data?
No
Funded by
National Assembly and OSP
Reportar contingut inapropiat
Aquest contingut no és apropiat?
10 comentaris
Conversa amb Virgile Deville
@product would love to get your feedback on this
Hi @virgile_deville ! Could you please explain the problem a little better? What does high uncertainty mean? We understand that the author of an initiative invites people with whom she has a certain level of trust
@product Of course we can assume the author of an initiative will invite only people she trust, one could argue that a relationship of trust in a group of people can sometimes evolve.
The fact that members can share the invitation link, accept, reject, revoke members of the promoter committee puts at risk the trusting environment originally intended by the original group of people promoting the initiative.
1/2
The reasons why we are proposing to differentiate the permissions between authors and members
- Initiatives, the way they are currently implemented are not error tolerant. If you send the initiative to technical validation there is no way of going back to the « create » state ;
- Collaboration on the initiative texts are limited, most of time the text is drafted on collaborative pad outside of Decidim. In this context it makes sense to centralize core actions (sending to technical validation, accepting, rejecting and revoking members) on the author to avoid coordination mistakes ;
Essentially we find that the main purpose of the promoter committee is to have a way to have multiple authors as condition to publication and to display them on the initiative page.
2/2
Conversa amb Carol Romero
@josanFFiG could you please chime in and give feedback here?
As an admin I can perform all the actions of a promoter's committee member. I think there wouldn't be any impact on @josanFFiG usage.
Can we get a feedback on this soon as we'll need to get started with the development as soon as next week ...
Thanks in advance !
@virgile_deville I think @josanFFiG 's main doubt with this is that, being and admin, he often comes on board as a temporary committee member to help the promoters.
I was kind of confused by that because the admin can do everything a promoter's committee member can do. So from what I understand there's no need for the admin to join in order to be able to help.
IMHO, taking into account the experience lived so far with initiatives in Barcelona, I think it is better not to give the responsibility of certain actions to a single person because it can become a bottleneck, this is the only " but "I see there.
Hey @josanFFiG ,
Could you tell us more specifically what may happen ?
I imagine cases like the author dropping out leaving the rest of the promoter committee having to restart a new initiative. Apart from that nothing comes to mind.
Have you seen a lot of collaboration "on" Decidim to draft an initiative ? I mean like different people changing the description, the title adding a joint file sending it technical validation. I feel like all of that happens outside of Decidim on solutions more fit to it like Etherpad, or google docs and that the promoter's committee members are really here to show that it's a collective supporting the initiative and not just one group or person.
Would love to learn more about your hands on experience ? Thank you so much in advance.
Deixa el teu comentari
Inicia la sessió amb el teu compte o registra't per afegir el teu comentari.
Carregant els comentaris ...