etherpad

My bet would be that people confuse it with Etherpad https://github.com/ether/etherpad-lite which is quite old stable project so probably not that exciting.

https://github.com/ONLYOFFICE https://github.com/dream-num/univer https://github.com/ether/etherpad-lite https://github.com/firebase/firepad https://github.com/prosemirror https://github.com/CollaboraOnline/online https://github.com/hedgedoc/hedgedoc https://github.com/gobby/gobby

I remember that I self hosted an EtherPad instance https://github.com/ether/etherpad-lite There was something like that for spreadsheets too but I can't remember what. The only collaborative projects I had to work on were with customers so we always used Google Docs, nothing self hosted.

Actually, both dependencies are specified: 1. https://github.com/ether/etherpad-lite 2. https://plantuml.com/ -> go to the bottom, there is an editor that renders the diagram, collabuml uses such a public api. I'm happy to provide details about running etherpad if necessary. > I can put a little backend for this. Not too difficult. Etherpad is the collaborative backend, plantuml is the uml renderer (there is a way to run a server with this).

Same here -- I use Jitsi to have meetings with friends sometimes (fun fact you can just go to https://meet.jit.si/<any random string here>), and the web app has gotten a lot better over the years (it was never "bad" IMO). I am not sold on the necessity of GTK/QT clients over Electron applications -- I think the development/packaging ease of Electron is exactly why it's where it is today and what works for users generally is not wins so I view it with dispassion. Doesn't matter how much better GTK/QT is (they can't be that good, devs are choosing to "shoot themselves in the foot" with Electron just over there!). Also the nice thing about web is that phones will at least have a chance (even if overheating during the call). I was more wondering about what it took to run -- Jitsi's server requirements always seemed a bit too heavy weight -- i

I'm perfectly ok with a maintainer reserving to himself the right to modify or even force-push a PR. If feature-wise the PR has value, but there are other requirements that have to be meet in order for it to be mergeable, I see no problem in the maintainer making his hands dirty. This contributor's work is recognized, and the maintainer can keep growing the project the way he wants. Not every occasional contributor will become a project member, so it makes no sense to impose too much burden on him. Maybe he only wants an interesting feature added. Some of them will eventually become interested in becoming regular contributors, and that is even better, but every one should be left freedom of choice. In my experience as Etherpad maintainer (1.6.5 through 1.8.4) this approach worked very well. For example https://github.com/ether/etherpad-li

Etherpad lite is still alive: https://github.com/ether/etherpad-lite

Etherpad has been open source since 2009, when it was bought by Google and immediately re-licensed. It stayed open source ever since. It was written in a mix of Scala & JS. Etherpad Lite (https://github.com/ether/etherpad-lite) is a port to javascript, is backed by the Free Software Conservancy and is not owned by any corporation. Yes, if you do not mind using Google's infrastructure, Google Docs is easier & more featureul. There are some cases in which running on premises may make a difference, and Etherpad strives to fill that palce.

There is also https://github.com/ether/etherpad-lite

MoPad is still running the old etherpad version[1], the release is etherpad-lite[2]. Is there some easy way to migrate from the old etherpad installations? [1] https://github.com/ether/pad [2] https://github.com/ether/etherpad-lite

The source is available at https://github.com/ether/etherpad-lite

There are many.. https://github.com/ether/etherpad-lite/wiki/Sites-that-run-E...