ICLAs from original copyright owners of SwellRT source code has been signed and sent to Apache. This implies, AFAIK that Wave community is free (libre) to use SwellRT's source code entirely or parts of it without risks of raising any IP issues. This makes safer, legally speaking, any collaboration between communities involving the source code.
This doesn't imply any commitment from Wave taking over SwellRT source code, roadmap...and in particular SwellRT brand, that is a separated matter. How SwellRT source code can be exploited by Wave is a community choice. I think those more technically involved in the project should address the discussion. My email is a part of this aim. I expect your point of view so we can define a tech road map. 2017-03-20 15:04 GMT+01:00 Evan Hughes <wisebald...@apache.org>: > Thanks for all the info but doesn't quite answers some of the more pressing > questions. > > Has swellrt been donated to the incubator as in the incubator is now where > the official swellrt development will happen? Does this include the > branding asset's? How do we want to handle publishing of the swellrt as a > sub part of this project. > > ~ Evan > > On 20 Mar 2017 11:22 PM, "Pablo Ojanguren" <pablo...@gmail.com> wrote: > > Hi all, > > My apologies for the late update on SwellRT. I hope this email could help > to clarify the ongoing discussion. > > As summary SwellRT objective is to make Wave generic... > > Instead of Wave Conversations it provides generic Collaborative Objects. > Instead of a GUI it provides an API. > > *Current status:* > > *JavaScript Beta client* > > - Based on the original Web client. > - No dependencies with GWT UI components. > - No dependencies with JSNI thanks to JSInterop. > - It allows to mutate and sync Javascript objects (ES6 Proxies). > - This implementation is expected to ease generation of Android and iOS > clients. > - Basic features are in place but some others are still not migrated > from alpha. > > Check out README[1] and Wiki[2] for usage details. To dive into the code, > see package *org.swellrt.beta,* and the classes > *ServiceFrontendEntryPoint* > and *SObjectRemote* > > > > *Collaborative Editor Component* > > Task to provide the Wave text editor as a separated component, so > eventually it could be replaced. So far, it exposes following features as > API > > - Annotations > - User presence > > Currently I am debugging it for mobile browsers. > Widgets API coming soon. > > Package org.swellrt.beta.client.js.editor [3] > > *Federation with Matrix.org* > > Testing the proposed implementation [4] from GSoC'16 student. We would like > to provide a PR asap. > > > > *JetPad* > We are developing SwellRT together with a real application of it, > jetpad.net > [5] a collaborative text editor. > > > > *Google Sumer of Code 2017* > We are also participating in GSoC17 thanks to the support of Universidad > Complutense de Madrid and Berkman Klein Center (Harvard) > Please encourage any students to send proposals, not limited to our > suggestions [6]. Deadline is April 3. > For example, we are considering a proposal of e2e encryption based on [7] > > > > *Wave + SwellRT* > I guess the question to answer in the community is whether SwellRT can be > used as is, or adapted, or part of it, to provide a new Wave UI. > > > Thank you, > > Pablo > > > > [1] https://github.com/P2Pvalue/swellrt/blob/master/README.md > [2] https://github.com/P2Pvalue/swellrt/wiki > [3] > https://github.com/P2Pvalue/swellrt/tree/master/wave/src/ > main/java/org/swellrt/beta/client/js/editor > [4] https://github.com/Waqee/incubator-wave/blob/master/ > MATRIX-FEDERATION.md > [5] https://jetpad.net/ > [6] https://cyber.harvard.edu/gsoc/SwellRT > [7] http://www.tara.tcd.ie/bitstream/handle/2262/68179/ > paper.pdf?sequence=1 >
