Hi Pablo, I have to admit that I don't recall seeing your fork announced/discussed much on this list, nor raised as something to bring in as a development branch under the Apache Wave umbrella - hence I am not surprised it hasn't attracted much attention here.
Perhaps making a standalone announcement of your fork is something that you would be interested in doing - to find others willing to contribute towards the development of your fork here? As when we have made announcements on this list - e.g. the discussions on a new p2p framework, or the announcement of an 'unofficial' hangout, etc. there has been reasonable response. I do think that Upayavira's points on using this opportunity to remove some of the barriers to entry here are still valid, and that despite agreeing in the past that we (as a community) want to separate out the Wave Protocol(s) from WIAB, we have not really done so.... Ali On 21 March 2015 at 18:44, Pablo Ojanguren <[email protected]> wrote: > Upayavira, > > Regarding your question, does it stand for the project/community vision? > I have worked on decouple server and client code from GWT one and it seems > it hasn't attracted attention. > > If the mentor must represent the community, then it must have clear idea of > project's aim and next steps. > > > > 2015-03-20 20:07 GMT+01:00 Upayavira <[email protected]>: > >> I think your last question is the most important one - is there someone >> here prepared to be a mentor, according to the terms specified by >> Google? >> >> If you have read the recent archives of Wave, you’ll see that there >> hasn’t been much activity here. >> >> My question is, could Roshan, working on Wave, resolve some of the >> technical issues that the project has that prevent it from gaining >> additional developers? From my outside perspective, removing, or >> separating out the client/server, removing the GWT code/etc could be >> steps that could help make the codebase more palatable, and make the >> obvious benefits of the Wave protocol more accessible to newcomers via >> this codebase. >> >> That would be the perspective I’d want us to take with GSoC - not add a >> nice bit on the side for the project, but look to make some fundamental >> fixes to the accessibility of the codebase. >> >> Thoughts? Mentor volunteers? >> >> Upayavira >> >> On Fri, Mar 20, 2015, at 04:50 PM, Roshan Lakmal wrote: >> > Hi all, >> > >> > I stared to read about Wave architecture and protocol. >> > >> > Can I still continue this project for GSoC 2015 or Is there any other >> > task >> > that I can contribute. >> > Is there anyone to mentor me for GSoC 2015? >> > >> > Cheers, >> > >> > Roshan. >> > >> > >> > On Fri, Mar 20, 2015 at 2:54 PM, Pablo Ojanguren <[email protected]> >> > wrote: >> > >> > > Hi Roshan, >> > > >> > > I have re-engineered part of the original GWT webclient and port core >> code >> > > to Android [1]. With the app you can connect to a Wave server and >> operate >> > > at Wavelet-level with the original Java code. A new UI for the >> > > conversational model could be added on top of it. >> > > >> > > As long as original code is Java it mostly works on Android, except >> > > specific GWT parts that have been replaced. >> > > >> > > Pablo >> > > >> > > >> > > [1] https://github.com/Zorbel/swell-android >> > > [2] >> > > >> http://p2pvalue.eu/blog/awakening-decentralised-real-time-collaboration >> > > >> > > >> > > 2015-03-19 19:53 GMT+01:00 Ali Lown <[email protected]>: >> > > >> > > > Hi Roshan, >> > > > >> > > > You will probably be interested to read about the Client-Server >> > > > Protocol[1], and its associated protobuf implementation[2], as this >> is >> > > > what currently defines the 'split' between the WebClient and the >> > > > Server parts of WIAB. >> > > > >> > > > As this protocol works entirely with deltas, you to retrieve the >> > > > 'content' for display in your client, you will need to understand the >> > > > Conversation Model[3], which defines how create the familiar Wave >> > > > structure on top of the underlying federateable delta-backed >> protocol. >> > > > You should be able to re-use most of the model code[4] in your >> client. >> > > > >> > > > I hope these pointers give you somewhere to start from, feel free to >> > > > ask me any further questions whilst navigating the wave codebase. >> > > > >> > > > Also, whilst not directly applicable - as I started at the federation >> > > > end, you may find my 'rave'[5] codebase useful as a way of wrapping >> > > > your head around the conversation model. >> > > > >> > > > Ali >> > > > >> > > > [1]: >> > > > >> > > >> https://svn.apache.org/repos/asf/incubator/wave/whitepapers/client-server-protocol/ >> > > > [2]: src/org/waveprotocol/box/common/comms/waveclient-rpc.proto >> > > > [3]: >> > > > >> > > >> https://svn.apache.org/repos/asf/incubator/wave/whitepapers/conversation/ >> > > > [4]: src/org/waveprotocol/wave/model/* >> > > > [5]: https://github.com/alown/rave >> > > > >> > > > >> > > > On 19 March 2015 at 18:14, Roshan Lakmal <[email protected]> >> > > wrote: >> > > > > Hi Michael, >> > > > > >> > > > > I'm interested to working on Native Android Client [1] because I >> think >> > > it >> > > > > will help to boost the Wave project again. In my side this will be >> a >> > > > great >> > > > > opportunity understand about the Wave Protocol [2]. >> > > > > >> > > > > As a starting point I successfully build the project in my local >> > > machine >> > > > > [3]. >> > > > > >> > > > > cheers, >> > > > > >> > > > > [1] - https://issues.apache.org/jira/browse/WAVE-400 >> > > > > [2] - http://www.waveprotocol.org/protocol >> > > > > [3] - >> > > > > >> > > > >> > > >> https://drive.google.com/a/iit.ac.lk/file/d/0B_tP-jjki90QckNsUHBSbnZDaGs/view >> > > > > >> > > > > On Thu, Mar 19, 2015 at 11:40 PM, Roshan Lakmal < >> > > > [email protected]> >> > > > > wrote: >> > > > > >> > > > >> Hi Michael, >> > > > >> >> > > > >> I'm interested to working on Native Android Client [1] because I >> think >> > > > it >> > > > >> will help to boost the Wave project again. In my side this will >> be a >> > > > great >> > > > >> opportunity understand about the Wave Protocol [2]. >> > > > >> >> > > > >> As a starting point I successfully build the project in my local >> > > machine >> > > > >> [3]. >> > > > >> >> > > > >> cheers, >> > > > >> >> > > > >> [1] - https://issues.apache.org/jira/browse/WAVE-400 >> > > > >> [2] - http://www.waveprotocol.org/protocol >> > > > >> [3] - >> > > > >> >> > > > >> [image: Inline image 1] >> > > > >> >> > > > >> >> > > > >> On Thu, Mar 19, 2015 at 9:48 PM, Michael MacFadden < >> > > > >> [email protected]> wrote: >> > > > >> >> > > > >>> Roshan, >> > > > >>> >> > > > >>> There are plenty of tasks within Wave that could be worked on. >> Do >> > > you >> > > > >>> have any particular interest? UI, Backend work, etc.? I am >> sure we >> > > > could >> > > > >>> find you something. >> > > > >>> >> > > > >>> ~Michael >> > > > >>> >> > > > >>> >> > > > >>> >> > > > >>> >> > > > >>> On 3/19/15, 5:33 AM, "Roshan Lakmal" <[email protected]> >> > > wrote: >> > > > >>> >> > > > >>> >Hi all, >> > > > >>> > >> > > > >>> >I'm Roshan Lakmal, an Undergraduate student from Informatics >> > > > Institute of >> > > > >>> >Technology - Sri Lanka. Last year I participated Gsoc for Apache >> > > > Software >> > > > >>> >Foundation (Apache SIS) [1]. >> > > > >>> > >> > > > >>> >For this summer I would like to work with Apache Wave for GSoC >> 2015. >> > > > Is >> > > > >>> >there any suitable task available for me. >> > > > >>> > >> > > > >>> >[1] - >> > > > >>> > >> > > > >>> >> > > > >> > > >> http://www.google-melange.com/gsoc/project/details/google/gsoc2014/roshanrox911/5668600916475904 >> > > > >>> > >> > > > >>> >Cheers, >> > > > >>> > >> > > > >>> >Roshan >> > > > >>> >> > > > >>> >> > > > >> >> > > > >> > > >>
