Forking topics

@jonlemmon could you screenshot them and post them here?

Any progress on this feature? We really need a way to move replies to another thread. Deleting is not an option if you want to keep the plurality of voices. Moving is much better :-)

Neat that this feature is live now.
I wonder if a less techie way of talking about it would be 'split' rather than 'fork'?
I'd love to be able to move proposals, not just comments.

I agree, this is a feature I started clamouring for when the Loomio team were still using Yammer, and it's fantastic to see it go live.

@matthewbartlett 's concern about using terms from Ancient Geek is totally valid, but IMHO fork is a fairly self-evident metaphor, given that most people are familiar with a fork as a piece of cutlery, and as a way of describing what tree branches do, or "a fork in the road". I also think using it for discussions could help people better understand the way the term is used in tech.

I'm with Strypey - Fork is jargon, and it's good to share the languages of skilled trades, they enrich our awareness of how stuff is done, and they're poetry. Anyway, fork is a pretty ordinary notion for road users and walkers, and it is a path that we're waymarking.

I find the 'Fork Thread' function to be very useful, to pull a selection of comments to start a new thread with.
However, it would be very useful to also be able to transfer comments into a pre-existing thread, where perhaps the subject is more relevant.
Also, it would be good to be able to merge two threads, while keeping the chronology of the comments. On occasion different threads are started by two members on the same topic, and it would be good to bring the conversations together.
Is there a way to achieve these things, or is this in development?
Thanks

Hi Gerard, the current plan is to rename "Fork" to "Move comments" and enable people to move selections of comments between threads (either new or existing)

Right now we're finishing our rewrite of the Loomio frontend rewrite (switching from AngularJS 1 to Vue). Once we've switched to the new client we can make functionality changes again.

Expect to see a beta release announcement in the next few weeks.

That's excellent, thank you.

Robert . . When the change to Vue comes, does this brings changes in searchability of comments?

No, it brings in almost no new user facing features - except a WYSIWYG editor with much better file and image handling.

The intent is to reach feature parity, as both clients need to work against the same server until the new one is ready to replace the old one. Then new feature dev can resume once we've moved everyone to the new client.

The benefits of the the new framework include
- ongoing support (Angular.JS and Angular Material are both discontinued libraries)
- faster to develop features with and better existing components (such as Vuetify)
- much better mobile support (we're able to introduce mobile apps built on this shortly after beta begins)

I hear you about the need for greater search support though.