Editing Proposals
Remove 'edit proposal' feature
proposal by Richard D. Bartlett Closed Mon 6 Aug 2012 9:53PM
The 'edit proposal' button should be disabled once the first votes have been cast.
[I just edited the proposal as a test.]
Results
| Results | Option | Votes | % of votes cast | % of eligible voters | |
|---|---|---|---|---|---|
| Agree | 4 | 57 | 0 | ||
| Abstain | 2 | 29 | 0 | ||
| Disagree | 1 | 14 | 0 | ||
| Block | 0 | 0 | 0 | ||
| Not voted | 893 | 99 |
I can live with either disabling it or just having the alert aaron mentioned.
To me this seems quite harsh on the users and potentially frustrating if someone made a typo or just wants to make a couple sentences more clear. It doesn't seem like a black-and-white issue to me. I'm happy for someone to change my mind though.
This needs to happen, otherwise people will be shown as having a position on something they haven't had a chance to consider because it's been changed since they voted
Definitely keen for this to happen! But very open to hearing alternative ideas for getting the same result
feels like we are putting a huge amount of energy into a 'high risk' low liklihood of happening category. Seems to me everyone agrees its just priioritising it
As long as the change is recorded and transparent. I dont see this removing admin functionality as an issue
Rethink
Make edits more prominent
proposal by Richard D. Bartlett Closed Tue 7 Aug 2012 11:22AM
When a proposal has been edited, the changes should be announced in some way, e.g. in the timeline, in the proposal itself, as a notification, and/or optional email.
Results
| Results | Option | Votes | % of votes cast | % of eligible voters | |
|---|---|---|---|---|---|
| Agree | 2 | 33 | 0 | ||
| Abstain | 1 | 17 | 0 | ||
| Disagree | 3 | 50 | 0 | ||
| Block | 0 | 0 | 0 | ||
| Not voted | 893 | 99 |
This is okay; but I prefer Josh's 15-minute suggestion.
Hmm, sounds like you're not actually happy with this proposal. Why not Josh's idea about a 15 minute time-limit? I'd be happy to compromise with that.
I think a better solution is to not allow edits at all after a certain time or after someone has voted
+1 to disabling edits after a certain time limit or after someone has voted.
best interim solution before forking is developed
I am feeling users need to be notified or a new proposal started
That the 'edit proposal' feature be disabled once the first person has stated their position
proposal by Benjamin Knight Closed Fri 10 Aug 2012 10:16PM
Context: At the moment, the person making a proposal can edit it right up until it closes, without any notifications or visibility in the discussion.
This means that people might agree to one thing, then come back to the discussion to find that the proposal has substantially changed, possibly into something they wouldn't have agreed with.
This has already been problematic in some of the 19 Tory St discussions, despite the pop-up warning that's already implemented.
Allowing proposal editing up until the first person has stated their position is proposed as an interim solution, until we can figure out a smooth way of forking proposals.
This seems less arbitrary than a 15-minute cut-off, and more relevant to the process (since it's only problematic/misleading to edit the proposal after a position has been stated), and allows for the fixing of typos or addition of context soon after the proposal has been put up.
Results
| Results | Option | Votes | % of votes cast | % of eligible voters | |
|---|---|---|---|---|---|
| Agree | 4 | 36 | 0 | ||
| Abstain | 4 | 36 | 0 | ||
| Disagree | 3 | 27 | 0 | ||
| Block | 0 | 0 | 0 | ||
| Not voted | 889 | 99 |
I'm thinking that pop-up+visibility is a pain to implement and still isn't enough - I think this is the best interim solution
can we move on now?
Happy with this but would prefer we remove it entirely til we've built a proper feature
I support this as a short-term fix. Sounds like it will be fairly trivial to implement, and incorporates most of the points raised in the discussion.
Sounds like a plan, just consider the use case where an admin clicks edit, someone votes, then admin clicks save.
See my latest comment. (Sorry for being such a stick in the mud!)
KILL THE FEATURE
I agree with JL
See my latest comment
See Aaron's last comment
Happy for others to decide
Happy for others to decide.
Kill the feature
proposal by Alanna Irving Closed Mon 13 Aug 2012 11:51PM
Proposing we simply remove the edit proposal feature all together until we can consider and test it properly and re-implement something that addresses all the issues brought up in this discussion.
If people need to change a proposal, they can simply close it and raise a new one as a workaround for now.
Results
| Results | Option | Votes | % of votes cast | % of eligible voters | |
|---|---|---|---|---|---|
| Agree | 7 | 100 | 1 | ||
| Abstain | 0 | 0 | 0 | ||
| Disagree | 0 | 0 | 0 | ||
| Block | 0 | 0 | 0 | ||
| Not voted | 892 | 99 |
Muhahahah
Burn it and respec
Keen for the feature to die, and a glorious preview button to emerge from its ashes
Here is some more information to hold along side this proposal.
- I have added a popup warning message to highlight the effects of this action and the preferred method of starting a new proposal if the change is significant.
- The edit proposal feature is only available to the Admin/Author.
Seems to me that being able to evolve a proposal in response to discussion is crucial to finding consensus. Can I suggest instead replacing the 'edit proposal' button available only to admin/ author with a 'fork proposal' button available to all participants in the group?
That way the original proposal and any votes on it would still be visible, and the new proposal could be voted on in parallel. So to take this proposal as an example, I would be able to 'fork' this proposal to add my suggestion about 'fork proposal' button (oh dear this is getting recursive ;).
Ideally, there would be a 'merge proposal' feature too. Again, using this thread as an example, Richard's proposal and my proposal could be merged into a third proposal:
"remove edit proposal button and replace with merge proposal button"
Not sure how you'd visualise all this though :)
Love the forking proposals idea, in theory it's not too difficult to implement but UI wise it could be a mess.
There is an interim workaround where you could just start another discussion and consider it a subdiscussion and the proposal a subproposal. (Which hints as to how this could be implemented)
Addressing the initial proposal though I think anything that changes a proposal's story (/history) is the wrong approach. Disabling an edit button after a proposal has votes would be fine short term.
The interface is the challenge alright ;)
One way to simplify things would be to reduce the number of options. Saying 'no' is effectively abstaining unless you block, and abstaining is effectively saying 'no but I won't block', otherwise you'd say 'yes', right? I suggest removing the 'block' vote, leaving:
Yes (I agree)
Abstain (don't agree, but will go with the group)
No (I don't agree, and wish to discuss further or suggest something else)
There are two main styles of consensus, one of which allows blocks, the other does not. For example, the Permaculture in NZ Constitution says:
"Consensus is an agreement to reach agreement. If a person does not agree he/she must [be at work with] an alternative proposal. Consensus is not to be used as a veto or as an obstruction to business."
With these three options, a group like PINZ could interpret a 'no' as a strong objection suggesting the need for further discussion or modification of the proposal. Groups which allow blocks could treat a 'no' as a block, and those not wishing to block could abstain.
If the goal of Loomio is to facilitate inclusive consensus, it occurs to me that a person making a 'no' vote should be required to fork the proposal, and a person making an 'abtain' vote should be encouraged to fork the proposal. A possible ways to visualize this:
1) A 'block' vote comment is a link to the fork proposal created by the person blocking (the same for any forked proposal created by a person abstaining).
2) Links to fork proposals could be included in the pie chart in place of 'block' votes. If a second person blocks, they can either add their support to the first person's fork proposal, or create their own (perhaps as a merge of the original and the fork?)
I would also suggest ordering the vote comments under the pie chart from, starting with 'no', then 'abstain', then 'yes'. This emphasizes the nature of any dissensus around the issue which needs to be dealt with in order to find full consensus.
Note: as I've said before, it would be a handy feature to be able to configure Loomio for different group processes. Now we have identified:
1) consensus - no blocks
2) consensus - allowing blocks
3) majority rules - usually no blocks
and potentially
4) majority rules - allowing blocks (probably not worth implementing until a group who uses such a process comes along)
There may be other group processes Loomio could work with.
I love what you are saying Strypey, Some customer feedback I have received is exactly on this idea that if you are blocking you shuld also be working on providing a solution,or working with others to find improvements in what is suggested,
I would love to see us define 4 cards like this<
yes
abstain, I have questions, and need more information before deciding
no, I disagree but OK with going with the group decision
block, dont agree, and wish to discuss further or suggest something else.
I suspect this is not exactly on topic but great it came up
+1 to forcing someone to create a new proposal if they block
I think a pop-up warning and strong group culture around when to edit/not-edit proposals is a better way of doing things than enforcing something harsh like this. What about when someone makes a typo? I'd say a better solution would just be to make it very obvious that the author has edited the proposal, along with version history so you can see what the changes were.
Process point: there are a lot of other conversations regarding bigger issues being brought into discussion which is meant to be focused specifically on editing proposals. Maybe those other topics deserve their own discussion thread? I have a lot to say in response to Strypy's comments but I don't think they belong in this thread.
Regarding editing proposals, I think the best solution would be to remove the edit feature and force people to create new proposals. Otherwise it's very unfair to people who stated a position based on one thing, but are being represented by something different after editing. If the proposal needs to change, there should be a new one.
I think issues such as clarifications and typos can be fixed by making comments in the discussion or editing the context panel (when we have that). If a proposal is poorly formed (unclear, incorrect info, etc) people should not say yes on it and it should fail so a better one can be raised.
Forking and merging proposals is an interesting idea, but one that will require a lot more thought and discussion to implement well.
With the feature as it is right now, we are introducing bad process to group decision making. There have been a couple examples lately in the 19 Tory St group of proposals changing significantly after I've stated my position on them.
I'm sure there is a good way to do editing, I'm just suggesting that the way he have it set up right now does more harm than good and should be disabled until we've found a better one.
Alternatively, if people think it would be better to keep the Edit Proposal function but add an Alert feature so that it's super obvious and highlighted when the proposal is edited (and maybe sends a notification to everyone who's already stated their position). Thoughts?
So there currently is a pop-up warning already (implemented a few days ago).
Ben is going to edit the text of it. I personally think this could suffice until we improve the edit functionality (make it very obvious that the proposal has been edited and potentially email everyone who has already stated their postion).
But if you guys would rather remove the functionality for now I'm happy to go along with it. Consider my "no" to be soft and flexible. =)
I think keeping the edit history clear in the timeline and notifying everyone who's voted will keep the proposal story in tact and is a good solution.
Does make for a nicer way to add clarification etc.
I still don't like the idea that a proposal could be changed in the last few minutes and everyone's votes remain in tact. Short term could you atleast disable the edit button for the last x amount of time?
I think long term Strypey's idea would be amazing to see in action.
The popup is better than nothing but IMHO inelegant like a poke in the eye. At very least if we're keeping this feature I think having a notification in the timeline is a prerequisite.
I would suggest that we allow editing for the first 15 minutes after a proposal is created to catch any typos obvious errors and then disable it after that - clean simple solution for now.
If I could fork the current proposal I would...
@Viv, this is something that's already been problematic at Tory St, so will definitely be a problem for other groups.
I agree with Paul that just making it super obvious when a proposal is edited (highlighted in the discussion thread, edited text is highlighted in the proposal details, and a notification is sent out) is the best solution.
Can I suggest closing the current proposal and reopening it with this idea?
I feel we are suffering from the tyranny of the status quo on this one: the feature exists so we are keen to let it stay, even though the UX is bad.
I made a new proposal as per suggestions.
I think it is dumb and we should just kill the feature until we have specced it out properly but I'd be happy if we at least get this change made.
Being allowed to edit proposals seems to be more doing more harm than good, in my experience. There may be a way to rebuild the editing feature later on down the track but right now it contributes to bad process.