ThomasWaldmann
commented
10 years ago Original comment by Thomas Waldmann (Bitbucket: thomaswaldmann, GitHub: thomaswaldmann).
https://togetherjs.com/ maybe interesting
Open ThomasWaldmann opened 11 years ago
ThomasWaldmann
commented
10 years ago Original comment by Thomas Waldmann (Bitbucket: thomaswaldmann, GitHub: thomaswaldmann).
https://togetherjs.com/ maybe interesting
ThomasWaldmann
commented
11 years ago Original comment by Thomas Waldmann (Bitbucket: thomaswaldmann, GitHub: thomaswaldmann).
fossrox suggested: http://sharejs.org/
ReimarBauer
commented
6 years ago recently I looked up some collab editors,
collabora
sharelatex
hackmd
any can go to a docker addon. collabora integrates currently with nextcloud.
ThomasWaldmann
commented
5 years ago Maybe look at whether we could use/integrate cryptpad (not because of the crypto, but rather because of concurrent/collab editing).
There was a nice talk about cryptpad at GPN19 (it's the successor of etherpad for the pirate party's collab editing).
Original report by Thomas Waldmann (Bitbucket: thomaswaldmann, GitHub: thomaswaldmann).
for editing wiki items (esp. text-based items), we could use some collaborative multi-user editor that synchronizes editor contents in realtime. for many use cases, this avoids conflicting edits and having to merge stuff afterwards.
the usual problems (I have looked at a lot of such stuff over the last years and about everything failed for some reason or the other):
we don't want to maintain the editor code ourselves, so we need some usable 3rd party code und a GPL v2+ compatible license.
it shouldn't be too slow.
it needs to be actively maintained.
it should be easily integratable, not requiring exotic additional stuff.
even better would it be if we could easily do the server component within the moin wsgi app.
it shouldn't be overbloated with stuff we don't need / can't use.
it should solve the "collab editing" problem in a generalized way (do it can be used for ANY text, not being specialized to some own or single markup).
it should work reasonably well.
transformations markup -> html, html -> markup shall stay server-side and in python. having to reimplement / duplicate all converters in javascript (or other languages) is not wanted.