The cwiki seems to be best place for the time being, anyone wanting to
contribute let the mailing list know for writing permissions.
https://cwiki.apache.org/confluence/display/WAVE/A+Wavey+Future
On Sat, 19 Mar 2016 at 18:55 Evan Hughes wrote:
> Whats the best way we can collab on a protocol s
Hello developers!
We released our features to github repository
https://github.com/jorkey/Wiab.pro
The key features is indexed delta storage and new rendering mechanism.
Joseph,
I have used quill a bunch. Great editor. I think it would be close to what we
need.
Evan,
Yes, the editor really shouldn’t know anything about OT at all. Even if we
were to make an editor of our own, I would strongly suggest not letting the OT
internals make it all the way into th
There is at least one commercial successor - https://www.co-meeting.com/
There was also another commercial attempt, which failed but is now open
sourced - https://github.com/jorkey/Wiab.pro
On Fri, Mar 18, 2016 at 12:29 PM Adam Bielski
wrote:
> Hiya all!
> I am new to this mailing group and I wa
As for the differences to Pie...I cant tell because there seems to be
very little information on Pie online, nor a working copy.
Id guess however Pie is a closed, unfederated messaging system though.
Can previous messages be edited? is the conversation thread
non-linear?
The differences between a w
Whats the best way we can collab on a protocol spec.
On Sat, 19 Mar 2016 at 07:05 Thomas Wrobel wrote:
> As for the differences to Pie...I cant tell because there seems to be
> very little information on Pie online, nor a working copy.
> Id guess however Pie is a closed, unfederated messaging sy
Hi Kirill
Great news, thanks!
I think those were the main issues with Apache Wave. Hopefully your
contributions will allow us to fix those issues and make Apache Wave faster
and more stable.
On Wed, Mar 16, 2016 at 1:59 PM Kirill Kostyuchenko
wrote:
> Hello developers!
>
> We released our featur
