This site uses cookies. By continuing to browse the site, you agree to our use of cookies. Find out more about cookies.
Skip to main content
Metadecidim's official logo
  • English Triar la llengua Elegir el idioma Choose language
    • Català
    • Castellano
Sign Up Sign In
  • Home
  • Processes
  • Assemblies
  • Initiatives
  • Consultations
  • Conferences
  • Help

Propose new functionalities for Decidim software

#DecidimRoadmap Designing Decidim together

Phase 1 of 1
Open 2019-01-01 - 2030-12-31
Process phases Submit a proposal
  • The process
  • Debates
  • Propose new features
  • News
chevron-left Back to list

Collaborative proposals

Avatar: Carol Romero Carol Romero verified-badge
22/01/2021 11:37  

Is your feature request related to a problem? A clear and concise description of what the problem is.

The collaborative drafts feature is currently underused, as it has several usability issues. To begin with, there are 2 different wizards, one for creating a collaborative draft and one for (individual) proposals. This also presents maintainability problems at the code level (the draft wizard is totally outdated).

The purpose of collaborative drafts is to co-create proposals, but there is no reason why they should be separate from the rest of the proposals.

Describe the solution you'd like

As a participant, I want to be able to...

- [ ] ... have a single proposal creation wizard, with a checkbox at the last step where I can flag whether I leave the proposal open for collaboration.

- [ ] ... navigate both individual and collaborative proposals through the same index.

- [ ] ... filter by the proposals that are open to collaboration.

- [ ] ... request access to participate in a collaborative proposal.

- [ ] ... get a notification/mail saying wether my access request has been accepted and/or rejected.

- [ ] ... view all changes that have been made to a colaborative proposal through version control.

- [ ] ... view a homogeneous interface for the common elements of individual and collaborative proposals.

As an author of a collaborative proposal, I want to...

- [ ] ... get a notification/mail when another participant requests access to the proposal

- [ ] ... be the only one who can accept and/or reject new contributors to the proposal

- [ ] ... be the only one who can withdraw the proposal

Describe alternatives you've considered

Keep the two workflows separate, updating the outdated wizard.

Mockups

1) New wizard

https://i.imgur.com/oncsOHM.png

2) Index of proposals

https://i.imgur.com/kAA8R4p.png

3) View as the author of an individual proposal

https://i.imgur.com/H74ZIiH.png

4) View as the author of a collaborative proposal

https://i.imgur.com/tGYIZfp.png

5) View as the contributor of a collaborative proposal (request access)

https://i.imgur.com/KAFBGCw.png

Does this issue could impact on users private data?

No

Additional context

Note: as one of the people who originally participated in the design of this feature, the hypothesis was to have a space for co-creation of proposals, without time limitations to edit them and facilitate collaboration among participants. This actually presents time synchronization problems with the "individual" proposals (while individual proposals cannot usually be edited after 5', collaborative proposals have no time limit).

After 3 years probably it makes more sense to hypothesize that during the proposal creation phase there should be no time limit for editing proposals, whether they are individual or collaborative. This could be solved by modifying the current setting, and simply allow the editing or not of proposals in a phase.

This raises some issues, for example, should the collection of endorsements and/or supports be allowed while proposals are open for editing? In my opinion clearly not. But limiting this by code is very tricky because of legacy. Instead, a warning should be displayed explaining the risk of simultaneously editing proposals and collecting support/endorsements.

Funded by

No funding yet

  • Filter results for category: Proposals Proposals

List of Endorsements

Avatar: Asociación aLabs Asociación aLabs verified-badge
Avatar: Oliver Azevedo Barnes Oliver Azevedo Barnes
Avatar: Ivan Vergés Ivan Vergés verified-badge
Avatar: Pau Parals Pau Parals verified-badge
Avatar: Pauline Bessoles Pauline Bessoles verified-badge
Avatar: Virgile Deville Virgile Deville
Avatar: agustibr ☂️ agustibr ☂️ verified-badge
Avatar: Antti Hukkanen Antti Hukkanen
Avatar: Nil Homedes Nil Homedes verified-badge
Avatar: Vera Rojman Vera Rojman
Avatar: txema txema verified-badge
and 8 more people (see more) (see less)
Endorsements count11
Collaborative proposals Comments 9

Reference: MDC-PROP-2021-01-16154
Version number 2 (of 2) see other versions
Check fingerprint

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It's useful to ensure the content hasn't been tampered with, as a single modification would result in a totally different value.

Value: 70494bbb07fb0c188fe70f4af2dec4063c30dcf79f6f6ca0a7c37c9860bfb4b0

Source: {"body":{"en":"<p><strong>Is your feature request related to a problem? A clear and concise description of what the problem is.</strong></p><p>The collaborative drafts feature is currently underused, as it has several usability issues. To begin with, there are 2 different wizards, one for creating a collaborative draft and one for (individual) proposals. This also presents maintainability problems at the code level (the draft wizard is totally outdated).</p><p>The purpose of collaborative drafts is to co-create proposals, but there is no reason why they should be separate from the rest of the proposals.</p><p><strong>Describe the solution you'd like</strong></p><p>As a participant, I want to be able to...</p><p>- [ ] ... have a single proposal creation wizard, with a checkbox at the last step where I can flag whether I leave the proposal open for collaboration.</p><p>- [ ] ... navigate both individual and collaborative proposals through the same index.</p><p>- [ ] ... filter by the proposals that are open to collaboration.</p><p>- [ ] ... request access to participate in a collaborative proposal.</p><p>- [ ] ... get a notification/mail saying wether my access request has been accepted and/or rejected.</p><p>- [ ] ... view all changes that have been made to a colaborative proposal through version control.</p><p>- [ ] ... view a homogeneous interface for the common elements of individual and collaborative proposals.</p><p>As an author of a collaborative proposal, I want to...</p><p>- [ ] ... get a notification/mail when another participant requests access to the proposal</p><p>- [ ] ... be the only one who can accept and/or reject new contributors to the proposal</p><p>- [ ] ... be the only one who can withdraw the proposal</p><p><strong>Describe alternatives you've considered</strong></p><p>Keep the two workflows separate, updating the outdated wizard.</p><p><strong>Mockups</strong></p><p>1) New wizard</p><p><a href=\"https://i.imgur.com/oncsOHM.png\" target=\"_blank\">https://i.imgur.com/oncsOHM.png</a></p><p>2) Index of proposals</p><p><a href=\"https://i.imgur.com/kAA8R4p.png\" target=\"_blank\">https://i.imgur.com/kAA8R4p.png</a></p><p>3) View as the author of an individual proposal</p><p><a href=\"https://i.imgur.com/H74ZIiH.png\" target=\"_blank\">https://i.imgur.com/H74ZIiH.png</a></p><p>4) View as the author of a collaborative proposal</p><p><a href=\"https://i.imgur.com/tGYIZfp.png\" target=\"_blank\">https://i.imgur.com/tGYIZfp.png</a></p><p>5) View as the contributor of a collaborative proposal (request access)</p><p><a href=\"https://i.imgur.com/KAFBGCw.png\" target=\"_blank\">https://i.imgur.com/KAFBGCw.png</a></p><p><strong>Does this issue could impact on users private data?</strong></p><p>No</p><p><strong>Additional context</strong></p><p>Note: as one of the people who originally participated in the design of this feature, the hypothesis was <strong>to have a space for co-creation of proposals</strong>, without time limitations to edit them and facilitate collaboration among participants. This actually presents time synchronization problems with the \"individual\" proposals (while individual proposals cannot usually be edited after 5', collaborative proposals have no time limit).</p><p>After 3 years probably it makes more sense to hypothesize that during the proposal creation phase there should be no time limit for editing proposals, whether they are individual or collaborative. This could be solved by modifying the current setting, and simply allow the editing or not of proposals in a phase.</p><p>This raises some issues, for example, <strong>should the collection of endorsements and/or supports be allowed while proposals are open for editing?</strong> In my opinion clearly not. But limiting this by code is very tricky because of legacy. Instead, a warning should be displayed explaining the risk of simultaneously editing proposals and collecting support/endorsements.</p><p><strong>Funded by</strong></p><p>No funding yet</p>"},"title":{"en":"Collaborative proposals"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data.

Share:

link-intact Share link

Share link:

Please paste this code in your page:

<script src="https://meta.decidim.org/processes/roadmap/f/122/proposals/16154/embed.js"></script>
<noscript><iframe src="https://meta.decidim.org/processes/roadmap/f/122/proposals/16154/embed.html" frameborder="0" scrolling="vertical"></iframe></noscript>

Report inappropriate content

Is this content inappropriate?

Reason

9 comments

Order by:
  • Older
    • Best rated
    • Recent
    • Older
    • Most discussed
Conversation with Oliver Azevedo Barnes
Avatar: Oliver Azevedo Barnes Oliver Azevedo Barnes
22/01/2021 11:47
  • Get link Get link

should the collection of endorsements and/or supports be allowed while proposals are open for editing? In my opinion clearly not. But limiting this by code is very tricky because of legacy. Instead, a warning should be displayed explaining the risk of simultaneously editing proposals and collecting support/endorsements.

That’s a tricky question, for sure. Maybe if endorsers are notified of each change, they’ll have the opportunity to change their minds through the process? It might become noisy, so perhaps it could notifications of batches of changes for a day, for example.

(Just a raw idea, haven’t thought it through.)

Avatar: Antti Hukkanen Antti Hukkanen
31/01/2021 14:22
  • Get link Get link

In our experience, this hasn't been problem. It is common that in discussion platforms people can vote comments which can be later edited.

The trust issue seems to be very specific to certain areas. E.g. in the Nordic countries it's really not an issue but I understand in some places of the world it can be an issue.

Conversation with Oliver Azevedo Barnes
Avatar: Oliver Azevedo Barnes Oliver Azevedo Barnes
22/01/2021 11:50
  • Get link Get link

There’s also the question if trolls. Would requiring collaborators to endorse a proposal from the beginning ensure the collaboration is productive? Raising the cost for a troll to disrupt the drafting process.

Avatar: Carol Romero Carol Romero verified-badge
22/01/2021 12:06
  • Get link Get link

Yep, here is the question of trust. We have always thought that this feature is primarily intended for collaboration in trusted environments (it is assumed that trust exists between the collaborators). And here is the difference with amendments, where no trust is assumed.

Avatar: Carol Romero Carol Romero verified-badge
22/01/2021 12:09
  • Get link Get link

And another question that is not resolved with the current collaborative drafts either. What happens if at the end of the collaborative phase, for whatever reason, I no longer want to appear as a co-author?

Avatar: Oliver Azevedo Barnes Oliver Azevedo Barnes
22/01/2021 12:47
  • Get link Get link

As an author I might like removing my name if I no longer like where it's going. There might be ramifications of this I'm not aware, though. And I think the removal should only happen before the proposal is gone through its life-cycle. Once it's been approved or rejected, there's an accountability issue there. My gut feeling is the author needs to own it. But not sure how that jives with right-to-be-forgotten, for instance

Avatar: Ivan Vergés Ivan Vergés verified-badge
22/01/2021 12:53
  • Get link Get link

There should be in place a mechanism to transfer the ownership of a proposal to another author, no only collaborative proposals but any kind.
As an author I could transfer ownership to another user (or group), when receiver accepts, complete the process (I'd would be able to cancel it meanwhile not accepted).

Conversation with Antti Hukkanen
Avatar: Antti Hukkanen Antti Hukkanen
31/01/2021 14:29
  • Get link Get link

[ ] ... have a single proposal creation wizard, with a checkbox at the last step where I can flag whether I leave the proposal open for collaboration.
[ ] ... filter by the proposals that are open to collaboration.

Regarding these points, I would rather like the collaboration options to be open by default without having an extra checkbox in the wizard. How about if the participant doesn't want to allow collaboration, they could disable it after publishing the proposal (on/off switch on the proposal page)?


[ ] ... request access to participate in a collaborative proposal.
For this, in real world use cases we have had two extra requirements for this:
For the current authors of the proposal, it was requested from us to add the ability to provide access directly to some participants. This happens through a similar popup that is used when you start a new conversation (search user => provide access => confirm view which lists the users and describes what you are about to do)
For admin users, it was requested from us to add the ability for admins to provide access to edit for any proposal for any user. This happened because the cities arrange collaborative events where these proposals could be worked on. And some of the original authors were not able to participate in these events.

should the collection of endorsements and/or supports be allowed while proposals are open for editing? In my opinion clearly not.
As I mentioned above for this point, this is very location specific how serious the trust issues are with this. I wouldn't see it becoming a problem around the Nordic countries that someone endorses a proposal that could be edited later on. I do understand that in some places of the world it could be problematic.


Avatar: Antti Hukkanen Antti Hukkanen
31/01/2021 14:31
  • Get link Get link

The comment formatting was messed up above. The last part is not a quote, the bullets 2 and 3 are comments for bullet 1.

The last part is a comment for the collection of endorsements/supports.

Add your comment

Sign in with your account or sign up to add your comment.

Loading comments ...

  • Terms and conditions of use
  • About the community
  • Download Open Data files
  • Metadecidim at Twitter Twitter
  • Metadecidim at Instagram Instagram
  • Metadecidim at YouTube YouTube
  • Metadecidim at GitHub GitHub
Creative Commons License Website made with free software.
Decidim Logo

Confirm

OK Cancel

Please sign in

decidim Sign in with Decidim
Or

Sign up

Forgot your password?