Re: [NOTICE] Wave is Retired - What's next?
I do not recall getting an answer to this before: do we still have access to the old (pre-Apache) mailing list? Zachary Yaro On Jan 27, 2018 10:53, "Upayavira" <u...@odoko.co.uk> wrote: On Sat, 27 Jan 2018, at 2:34 PM, John D. Ament wrote: > Hi all, > > I missed sending the notice to this list, apologies. The vote to retire > Wave has passed. > > I'm going to begin the process of marking source code as read only, as well > as shutting down the lists. John, Would it be possible to schedule the list shutdown at a fixed point in the future? e.g. 1week? Then those that remain here have that time to arrange a new venue for communication. If no such discussion happens - so be it, but at least there was a window for that discussion. Upayavira
Re: Resigning as mentor: what next?
If possible, I think it would be better to hold off on the vote until we know what the new homes for the mailing list, code repo, and documentation will be, and ensure we can update waveprotocol.org with those details. Zachary Yaro On 29 November 2017 at 04:41, Yuri Z <vega...@gmail.com> wrote: > So, if we have a consensus, I will send the retirement vote email in a few > days. > > On Wed, Nov 29, 2017 at 11:35 AM Yuri Z <vega...@gmail.com> wrote: > > > Yeah, I think I still have admin permissions for waveprotocol.org > > I can add you as admin in can you want to start working on it. > > > > > > On Mon, Nov 27, 2017 at 10:53 PM Zachary Yaro <zmy...@gmail.com> wrote: > > > >> Just so I understand, what would be the criteria for the project > rejoining > >> the Apache Incubator in the future? > >> > >> For instance, we have had several people (myself included) comment that > >> they would become more frequent contributors to the project once the > >> server > >> and client were sufficiently decoupled that a JavaScript client could be > >> worked on separately from the Java GWT client. Should that happen, and > >> regular work on the project continue, could the project easily rejoin, > or > >> would there be a higher barrier to reentry? > >> > >> > >> And on another note, if the project is retired, what happens to the > >> documentation and mailing list archives from Apache, and would anything > be > >> done to help migrate that elsewhere? > >> > >> (On a related note, do we still have access to waveprotocol.org and the > >> related mailing list? That would seem to be the logical place to > migrate > >> to.) > >> > >> Zachary Yaro > >> > >> On 27 November 2017 at 14:43, Dustin Pfannenstiel < > >> dustin.pfannenst...@nth-estate.com> wrote: > >> > >> > I've set up a repo and organization for the code base on github. > >> > https://github.com/TimaeusWave/WaveServer > >> > > >> > Thanks for the years of support and, well, just everything. > >> > > >> > DMP > >> > > >> > > On Nov 27, 2017, at 11:33 AM, Upayavira <u...@odoko.co.uk> wrote: > >> > > > >> > > > >> > > > >> > > On Mon, 27 Nov 2017, at 04:46 PM, John D. Ament wrote: > >> > >> The in depth "incubator required stuff" is at > >> > >> https://incubator.apache.org/guides/retirement.html for review > >> > >> > >> > >> Basically, > >> > >> > >> > >> - We have this conversation. Ensure that there's consensus on the > >> > future > >> > >> of the project. > >> > >> - Call a vote. When we call a vote, one of us will send notice to > >> > >> incubator. > >> > >> - Vote again on general@incubator. > >> > >> > >> > >> I do want to make sure there are two things abundantly clear: > >> > >> > >> > >> - Retirement isn't failure. Wave didn't fail as a project. > >> > >> - It's better to describe it as "this isn't a good fit as an Apache > >> > >> project." Apache projects tend to have at least three people > >> available > >> > >> at all times, either making changes, merging in changes, or able to > >> cut > >> > >> releases. > >> > > > >> > > What John described above is the process from Apache's side. > >> > > > >> > > The code is publicly available under an Apache License. Any of you > can > >> > > push your local repo up to GitHub and share it with whoever you > like, > >> > > using a name that includes the word "Wave", so that would be a step > >> > > alongside the more ASF-focussed administrative tasks above. > >> > > > >> > > Upayavira > >> > > >> > > >> > > >
Re: Resigning as mentor: what next?
Just so I understand, what would be the criteria for the project rejoining the Apache Incubator in the future? For instance, we have had several people (myself included) comment that they would become more frequent contributors to the project once the server and client were sufficiently decoupled that a JavaScript client could be worked on separately from the Java GWT client. Should that happen, and regular work on the project continue, could the project easily rejoin, or would there be a higher barrier to reentry? And on another note, if the project is retired, what happens to the documentation and mailing list archives from Apache, and would anything be done to help migrate that elsewhere? (On a related note, do we still have access to waveprotocol.org and the related mailing list? That would seem to be the logical place to migrate to.) Zachary Yaro On 27 November 2017 at 14:43, Dustin Pfannenstiel < dustin.pfannenst...@nth-estate.com> wrote: > I've set up a repo and organization for the code base on github. > https://github.com/TimaeusWave/WaveServer > > Thanks for the years of support and, well, just everything. > > DMP > > > On Nov 27, 2017, at 11:33 AM, Upayavira <u...@odoko.co.uk> wrote: > > > > > > > > On Mon, 27 Nov 2017, at 04:46 PM, John D. Ament wrote: > >> The in depth "incubator required stuff" is at > >> https://incubator.apache.org/guides/retirement.html for review > >> > >> Basically, > >> > >> - We have this conversation. Ensure that there's consensus on the > future > >> of the project. > >> - Call a vote. When we call a vote, one of us will send notice to > >> incubator. > >> - Vote again on general@incubator. > >> > >> I do want to make sure there are two things abundantly clear: > >> > >> - Retirement isn't failure. Wave didn't fail as a project. > >> - It's better to describe it as "this isn't a good fit as an Apache > >> project." Apache projects tend to have at least three people available > >> at all times, either making changes, merging in changes, or able to cut > >> releases. > > > > What John described above is the process from Apache's side. > > > > The code is publicly available under an Apache License. Any of you can > > push your local repo up to GitHub and share it with whoever you like, > > using a name that includes the word "Wave", so that would be a step > > alongside the more ASF-focussed administrative tasks above. > > > > Upayavira > >
Re: new committer: Pablo Ojanguren
Welcome! Thank you for helping move Wave forward! Zachary Yaro On Thursday, 12 January 2017, Yuri Z <vega...@gmail.com> wrote: > The Project Management Committee (PMC) for Apache Wave has invited Pablo > Ojanguren to become a committer and we are pleased to announce that he has > accepted. > Pablo is an active contributor of high quality code and is active within > community. He is also one of the main SwellRT developers. > Please join me in welcoming Pablo in his new role. > -- Zachary Yaro
Re: Bad links to waveinabox.net
WaveInABox.net used to host an Apache Wave demo instance, but presumably the domain expired and someone else bought it up. Those links were correct at the time they were added, but they should probably be removed now. Zachary Yaro On Tuesday, 4 October 2016, Philip McGrath <phi...@philipmcgrath.com> wrote: > I'm not sure if this is the right place to report this, but I wanted to let > you know that http://waveinabox.net doesn't currently appear to have > anything to do with Wave. I found links to it from > http://incubator.apache.org/wave/about.html and > http://incubator.apache.org/wave/demo-servers.html > Hope this is useful. > Philip > -- Zachary Yaro
Re: ALL HANDS - 9/28 10am EST
I do not mean to upend plans you might already have in place, but is there a reason not to use a Hangout or Hangout On Air? That would allow people like Thomas and myself to join in the text chat even though we cannot join via voice/video. Zachary Yaro On Wednesday, 28 September 2016, Adam John <a...@sterlingsolved.com> wrote: > This is the doc I have open for notes and agenda; > https://docs.google.com/document/d/11j_WQGYAtDlN8Wqx8jJglPpw6tJznvMGf > dLOvQu96i0/edit > > Thanks, and talk soon! > > AJ > > Adam John > (914) 623-8433 > Google+ <http://google.com/+AdamJohn1> | LinkedIn <http://mradamjohn.com/> > > On Tue, Sep 27, 2016 at 10:47 PM, Adam John <a...@sterlingsolved.com > <javascript:;>> wrote: > > > Thanks for all the confirmations folks! Kindly review the documents > > linked/sent previously in advance of the meeting. > > > > If we need to screenshare we can use a Hangout or my Join.me; > > https://join.me/mradamjohn > > If you expect to present, please install the application in advance. > > While you can observe with the web application or mobile app, you can > only > > present with the installed program. > > > > The Join.me has a conference line with international local numbers. > > Find more here: https://join.me/intphone/ > > I've listed a few I have used down below. > > > > *This is the Conference ID: 268-833-957* > > > > *Feel free to join early* - you should be able to talk as soon as 2 > > people are on the line. > > > > Talk soon! > > > > Adam > > > > Select numbers: > > Argentina - Buenos Aires +54.11.5352.8217 > > Australia - Sydney +61.2.9191.6319 > > Bahrain - national +973.1619.9273 > > Brazil - Rio de Janeiro +55.21.3500.1441 > > Canada - Montreal +1.514.800.1233 > > France - Paris +33.1.8288.3590 > > Germany - Berlin +49.30.2240.3071 > > Greece - Athens +30.21.1198.2986 > > Hong Kong - national +852.5808.1760 > > Ireland - Dublin +353.1.531.4868 > > Ireland - Dublin +353.1.513.4791 > > Israel - Tel Aviv +972.3.763.0434 > > Italy - Rome +39.06.8339.9900 > > Latvia - Riga +371.6616.3227 > > Lithuania - Vilnius +370.521.40705 > > Russian Federation - Moscow +7.495.777.3554 > > South Africa - Johannesburg +27.10.590.4610 > > Spain - Barcelona +34.93.220.1484 > > Ukraine - Kiev +380.443.92.0739 > > Ukraine - national +380.893.23.9951 > > United Kingdom - London +44.20.3582.4515 > > United States - Hartford, CT +1.860.970.0010 > > United States - Los Angeles, CA +1.213.226.1066 > > United States - New York, NY +1.646.307.1990 > > United States - San Francisco, CA +1.415.655.0381 > > United States - Tampa, FL +1.813.769.0500 > > United States - Washington, DC +1.202.602.1295 > > > > Thanks, and talk soon! > > > > AJ > > > > Adam John > > (914) 623-8433 > > Google+ <http://google.com/+AdamJohn1> | LinkedIn < > http://mradamjohn.com/> > > > > On Mon, Sep 5, 2016 at 12:39 PM, Adam John <a...@sterlingsolved.com > <javascript:;>> wrote: > > > >> I'm a Navy Vet, please forgive the use of this term if it bears a little > >> explanation. > >> It simply means there is a meeting - and everyone needs to be there. > >> (please) > >> > >> > >> *Wednesday September 28 at 10:00am EST* > >> > >> If you haven't seen the thread, there was a question of project > >> retirement recently discussed. While not answered conclusively, I > think it > >> is safe to expect the retirement will be held off *for now*. > >> > >> This meeting is about the future of Wave. > >> If you care about the project *at* *all*, *please join us*. > >> > >> Requested attendees: > >> > >>1. > >> > >>Price Clark > >>2. > >> > >>Thomas Wrobel > >>3. > >> > >>Evan Hughes > >>4. > >> > >>Zachary Yaro [cannot attend] > >>5. > >> > >>**Everyone on this list!** > >> > >> Confirmed: > >> > >>- > >> > >>Andreas Kotes > >>- > >> > >>Greg Cochard > >>- > >> > >>Jonathan Leong > >>- > >> > >>Pablo Ojanguren > >>- > >> > >>Michael MacFadden > >>- > >> > >>Adam John > >> > >> > >> Purpose: &
Re: Retirement
I am excited to see all this. It is unlikely I can join the call during work hours—is there any chance it could be recorded (e.g., done as a Hangout On Air) so I can catch up later? Thank you, Zachary Yaro On Sep 5, 2016 11:16, "Adam John" <a...@sterlingsolved.com> wrote: > @pablo that is great that you are working with the Complutense University > of Madrid! ... I'm adding an agenda item to give you a chance to talk about > the results of the contest if that is okay? > > If we can make progress on the peer review before the meeting, that would > be great as well.. also added a discussion item to the agenda for it. ( > https://github.com/Waqee/incubator-wave) > > --- > > @andreas awesome, I've added you to the informal attendees list. > > Since Docker and Kubernetes both use Golang, I've been toying with them > lately as well. This highlights one of my earlier point about making > adjustments to this project that will best leverage other open source work. > > I had not found SOLID yet, but quick review and it seems intriguing... it > is related to good+interesting W3C work (https://www.w3.org/TR/ldp-primer/ > ) > > --- > > @all ... I'll be starting 2 new threads, this one goes well beyond > 'Retirement' imho > Please join them as you deem appropriate. > > Thanks! > > Adam John > (914) 623-8433 > Google+ <http://google.com/+AdamJohn1> | LinkedIn <http://mradamjohn.com/ > > > > On Mon, Sep 5, 2016 at 8:25 AM, Andreas Kotes < > count-apache@flatline.de> > wrote: > > > hi, > > > > On Thu, Sep 01, 2016 at 11:08:23AM +0200, Thomas Wrobel wrote: > > > Server folk get that gwt away from me! > > > Gwt folk; get that server stuff away from me! > > > > everyone, get that Java away from me ;) > > > > *sigh* .. I've noticed that I've been moving on - towards Golang-based > > stuff. > > > > btw, you've see https://github.com/solid/solid ? > > > > Cheers, > > > > count > > > > P.S: I hope to be able to make it on the 28th .. > > > > -- > > Andreas 'count' Kotes > > Taming computers for humans since 1990. > > "Don't ask what the world needs. Ask what makes you come alive, and go do > > it. > > Because what the world needs is people who have come alive." -- Howard > > Thurman > > >
Re: Retirement
I think these are good priorities, as the open protocol is the #1 advantage Wave has over other real-time communication platforms. Rewriting the protocol could even open the door for algorithms developed since the original OT Wave protocol (IIRC, Joseph Gentle suggested as much a few years back). That said, the original Google Wave took two years to develop with a full dev team and support from a large corporation. I am concerned restarting from zero might not be as feasible with the small team we have here. Zachary Yaro On Aug 31, 2016 09:47, "Thomas Wrobel" <darkfl...@gmail.com> wrote: > ""an entirely new Wave codebase"" > > Or even the first building block that would become that. > If wave goal is defined as something like, "some sort of open > federated protocol to selectively share informative securely between > users" > > Would the first steps be too; > a) define how data is synced between servers.Presumably from > exchanging the changes. > i) OT still I assume? > b) define how data is synced between clients.Presumably from > exchanging the changes. >i) OT again? maybe closely related to above? > c) How to identify users? (existing standard usable here?) > > d) Then start implementation of a reference server. > e) Then start implementation of a completely separated reference client. > f) THEN work on user interface aspects of the (various!) clients. > > This is all just spitballing. Feel free to put yay, nay or "hell no" > next to any of the above. > I just think if there is _any_ hope to survive outside apache we need > small, manageable steps - hopefully each one useful in itself. > > -- > http://lostagain.nl <-- our company site. > http://fanficmaker.com <-- our, really,really, bad story generator. > > > On 31 August 2016 at 13:53, Upayavira <u...@odoko.co.uk> wrote: > > Adam, > > > > Whilst I appreciate that you are trying to help with the ApacheWave > > repos, I really don't want us to go that way. Wave is already available > > on Github as https://github.com/apache/incubator-wave. If this project > > folds, and the code goes to live on on github, it must be called > > something other than *apache* wave, as to call it Apache XYZ would be a > > misuse of a trademark. > > > > Let's decide whether or not the project continues here, and if it > > doesn't, then we'll discuss what happens with the various parts of the > > project once that decision is made. > > > > I still think that the best course of action is for a few people to get > > together and produce an entirely new Wave codebase. We've tried, and > > failed with the codebase we have. > > > > Upayavira > > > > On Wed, 31 Aug 2016, at 08:25 AM, Adam John wrote: > >> Created a GitHub organization, added each of the available repos: > >> https://github.com/ApacheWave > >> > >> I think I invited everyone on this thread - however there are many > others > >> on the list. > >> All are welcome. > >> > >> Loss of Apache incubator status is significant as it means also > >> organizational loss, tools lost, and would effectively put a nail in the > >> coffin for the project. > >> > >> WebCMS, Jira, Jenkins, and Travis are all valuable tools, and part of > >> Incubator status. > >> > >> Quality code review (thanks, vega and wisebaldone etc) and an > established > >> process for the inclusion of new contributions by people familiar with > >> existing approaches and the work in progress... all of this is > >> significant. > >> > >> The people on this list - and even the list itself - both a service and > >> an > >> organization that would be a significant loss in any transition... > >> > >> I think the safety of the incubator is important, for these reasons and > >> more; and there needs to be improved communication, planning and > >> coordination... here again, just my opinion. > >> > >> AJ > >> > >> Adam John > >> (914) 623-8433 > >> Google+ <http://google.com/+AdamJohn1> | LinkedIn > >> <http://mradamjohn.com/> > >> > >> On Tue, Aug 30, 2016 at 4:01 PM, Upayavira <u...@odoko.co.uk> wrote: > >> > >> > The best future for Wave at Apache would, I think be to start an > >> > entirely new project at GitHub, and implement a Wave system that > people > >> > can actually understand. Once that gains traction, come back to the > >> > Incubator and ask to resurrect Apache
Re: Retirement
I am in a similar boat. I have front-end development skills, but I struggle to fully understand the back-end functionality or begin separating the client from the server. Zachary Yaro On Aug 30, 2016 11:51 AM, "Thomas Wrobel" <darkfl...@gmail.com> wrote: > I have tried on 3 separate occasions to understand the server. Its > simply not in my skillset and I don't have the time to learn. I don't > wish to sound arrogant there, theres learning needed for anything of > course. But its too much investment - I want to apply skills that I > already have. Last time I tried to get into wave development (which > was I admit a few years back) it took me 3 days to even compile the > server. Which is frustrating for someone that just wants to work on a > client. > > So I am certainly not waiting for permission, I am waiting for a > prerequisite of a server/client split. I understand I can neither > demand or expect such a thing. Developers on a project like this just > have to jump in on what they feel like. Nothing can really be expected > and I accept that. > I simply am informing there's "lesser" developers like me that could > work on bits if certain other things happen. >
Re: New committer - Evan Hughes
Congratulations! Welcome, Evan, and thank you for contributing your time and skills to Apache Wave! Zachary Yaro On May 11, 2016 11:59, "Yuri Z" <vega...@gmail.com> wrote: > The Project Management Committee (PMC) for Apache Wave > has asked Evan Hughes to become a committer and we are pleased > to announce that he has accepted. > In fact that happened a few months ago, but I forgot to send the > announcement email. > Evan already made significant contributions - like moving Wave to use the > Gradle build system, improving the Jenkins CI process, adding Travis CI > configuration for the Github etc... > He is also proved himself being active community member. > I want to thank Evans for his contributions and looking forward working > with him in the future. > Please join me in welcoming Evan in his new role. >
Re: A Wavy Future
I am inclined to agree with Yuri—if the alternative implementation can be developed in parallel around the same protocol, that would seem to be the best scenario, but the existing codebase should be kept because it is (AFAIK) the most functional implementation of the protocol. Zachary Yaro On Mar 14, 2016 15:05, "Yuri Z" <vega...@gmail.com> wrote: > I think that more "wavy" projects are nice, but IMO it doesn't mean we > should abandon Apache Wave as it is now. I agree there are a lot of issues > with current code, but I think there's still value as people can see what > Wave can potentially be. > > On Sun, Mar 13, 2016 at 8:46 AM Evan Hughes <wisebald...@apache.org> > wrote: > > > The link for those who wish to join, Ill also add this link onto the new > > website. > > > > https://www.hipchat.com/gsModF8CY > > > > On Sun, 13 Mar 2016 at 12:12 Michael MacFadden < > > michael.macfad...@gmail.com> > > wrote: > > > > > Yeah. Chatting is fine and beneficial. We just need to make sure we > > > capture key decisions and rationale back in the list for all to see. > > > > > > ~Michael > > > > > > > On Mar 12, 2016, at 6:07 PM, Evan Hughes <wisebald...@apache.org> > > wrote: > > > > > > > > It does not so as Ive seen other projects state this motto "If its > not > > on > > > > the mailing list it didnt happen at all", but allows for non formal > > talk > > > > and back and forth discussion realtime. The Monthly reports that we > > > talked > > > > about back when we did the hangout session should probably be picked > up > > > > again, ill add it to the monthly todo's. > > > > > > > > On Sun, 13 Mar 2016 at 11:58 Michael MacFadden < > > > michael.macfad...@gmail.com> > > > > wrote: > > > > > > > >> One follow up question though. Does hip hat store conversations in a > > > >> publicly accessible manner? If not, we need to make sure key > > decisions > > > >> that come out of chats are captured and discussed on the mailing > list > > > for > > > >> all to see. > > > >> > > > >> ~Michael > > > >> > > > >>> On Mar 12, 2016, at 7:15 AM, Evan Hughes <wisebald...@apache.org> > > > wrote: > > > >>> > > > >>> I would get infra to make us a hipchat channel so we have some > place > > to > > > >>> talk casually web interface / irc, but seesm the jira's down. > Looking > > > to > > > >>> getting this rolling in some way or another by mid week. > > > >>> > > > >>> ~ Evan > > > >>> > > > >>>> On Fri, 11 Mar 2016 at 19:48 Evan Hughes <wisebald...@apache.org> > > > >> wrote: > > > >>>> > > > >>>> The client-server protocol would define a protobuf and json rest > > > >> services > > > >>>> so any language that support protocol buffers would be able to > make > > a > > > >>>> client or fallback to the json rest. > > > >>>> > > > >>>> > > > >>>> On Fri, 11 Mar 2016 at 19:24 Andreas Kotes < > > > >> count-apache@flatline.de> > > > >>>> wrote: > > > >>>> > > > >>>>> FWIW, > > > >>>>> > > > >>>>> I also consider the idea pretty good and would want stronger > > > decoupling > > > >>>>> of server/client. I'd be interested in a python client > > > implementation, > > > >>>>> mostly for CLI and bot integration. > > > >>>>> > > > >>>>> Not sure whether doing a client-side C implementation of the > > > >>>>> communication protocol would be best here (so wrapper for more > > > >> languages > > > >>>>> can follow), or whether native Python would be better. We need > > > >> something > > > >>>>> for non-Java folks in any case, I think. > > > >>>>> > > > >>>>> Cheers, > > > >>>>> > > > >>>>> count > > > >>>>> > > > >>>>>> On Fri, Mar 11, 2016 at 10:52:34AM +1000, Evan Hughes wrote: > > > >>>>>> Thankyou all for your feedback and expressions of interests, > seems > > > >> like > > > >>>>> we > > > >>>>>> may be able to develop some teams together to make this a faster > > > >> reality > > > >>>>>> than just I. Hopefully we can get some more people to express > > > >> interests > > > >>>>> in > > > >>>>>> this way forward. > > > >>>>> > > > >>>>> -- > > > >>>>> Andreas 'count' Kotes > > > >>>>> Taming computers for humans since 1990. > > > >>>>> "Don't ask what the world needs. Ask what makes you come alive, > and > > > go > > > >> do > > > >>>>> it. > > > >>>>> Because what the world needs is people who have come alive." -- > > > Howard > > > >>>>> Thurman > > > >> > > > > > >
Re: Web Designers
I am interested in helping with this. What are the associated deadlines? Zachary Yaro On Jan 30, 2016 11:17, "Michael MacFadden" <michael.macfad...@gmail.com> wrote: > I agree. I did the initial design of the site we have many years ago, and > we really haven’t done much with it since than. Should we perhaps put an > “advertisement” on the current web site letting folks know we are looking > for help with a new design? If so, I could add that to our current site. > > ~Michael > > > > > On 1/30/16, 2:10 AM, "Evan Hughes" <wisebald...@apache.org> wrote: > > >Hello all, > > > >We need a new website for our homepage and a new docs template design, > >surely we have a few designers here that would be willing to spend some > >time designing a new website. Just to be clear I'm not asking for people > to > >also implement it but we need a designer. > > > >The new design should also use the new Apache logo if people have not > >already seen it. > > > >http://www.apache.org/img/asf_logo.png > > > >If you would like to implement it after a design is made then go for it, > >but first things first, designers. > > > >~ Evan > >
Re: Wave App mockups
I doubt that can be copyrighted. Plenty of other apps—including Rizzoma—do that. I think some apps even did that before Google did. Zachary Yaro On Jun 21, 2015 19:10, John Blossom jblos...@gmail.com wrote: This looks very, very nice so far. Are there any copyright issues with the use of the leading alpha for the non-photoed user icons? Google uses that in Gmail... All the best, John Blossom email: jblos...@gmail.com phone: 203.293.8511 google+: google.com/+JohnBlossom On Fri, Jun 19, 2015 at 4:06 PM, Roshan Lakmal roshan.2013...@iit.ac.lk wrote: Hi All Here I have created the App mockups. Can you all please look into this App mockups and give me your feedback's. 1. Loading screen [1] https://drive.google.com/file/d/0B_tP-jjki90QMzhpTVVFNTRVeWM/view?usp=sharing 2. Sing In screen [2] https://drive.google.com/file/d/0B_tP-jjki90QaTVCaVVUaHUyWHM/view?usp=sharing 3. Sing up screen [3] https://drive.google.com/file/d/0B_tP-jjki90QcV9Wb1FncmJoeE0/view?usp=sharing 4. Wave Inbox screen [4] https://drive.google.com/file/d/0B_tP-jjki90QblBQSDFieGdvbW8/view?usp=sharing 5. Chat page [5] https://drive.google.com/file/d/0B_tP-jjki90QMlNHTEd5Vmk2cXc/view?usp=sharing 6. Create Wave page [6] https://drive.google.com/file/d/0B_tP-jjki90QdTZiVFpCRDdEYjA/view?usp=sharing Regards Roshan
Re: Wave App mockups
I like the overall idea, though there are a few ways you could better adhere to the Material Design guidelines that I think might improve the app's look and feel. Namely: - Make the user avatars (and avatar placeholders) circles instead of squares, or at least give them a little bit of padding so their visual weight is not so disproportionately high. Also, Android in general has moved in the direction of circular cropping for profile pictures. - Have the app bar and floating action button “float above” (have a higher z-value) than the other content so the FAB catches the user's eye. - Use a more simple wave icon on the reply bar so it is less visually busy, or maybe swap it for a reply icon since that is really the function the user is going to perform there. You may also wish to make your back button and “Sign up” button more consistent with other Material apps, but that is just nitpicking. Overall these seem like pretty good designs, and I look forward to seeing them implemented in an app :) Zachary Yaro On 19 June 2015 at 16:06, Roshan Lakmal roshan.2013...@iit.ac.lk wrote: Hi All Here I have created the App mockups. Can you all please look into this App mockups and give me your feedback's. 1. Loading screen [1] https://drive.google.com/file/d/0B_tP-jjki90QMzhpTVVFNTRVeWM/view?usp=sharing 2. Sing In screen [2] https://drive.google.com/file/d/0B_tP-jjki90QaTVCaVVUaHUyWHM/view?usp=sharing 3. Sing up screen [3] https://drive.google.com/file/d/0B_tP-jjki90QcV9Wb1FncmJoeE0/view?usp=sharing 4. Wave Inbox screen [4] https://drive.google.com/file/d/0B_tP-jjki90QblBQSDFieGdvbW8/view?usp=sharing 5. Chat page [5] https://drive.google.com/file/d/0B_tP-jjki90QMlNHTEd5Vmk2cXc/view?usp=sharing 6. Create Wave page [6] https://drive.google.com/file/d/0B_tP-jjki90QdTZiVFpCRDdEYjA/view?usp=sharing Regards Roshan
Re: Wave and Incubation
I think it is helpful that the wave standard be maintained by an established organization like the Apache. Yes, other tools with wave-y features, such as Google Docs, Rizzoma, and Slack, exist, but one of the most exciting promises of Wave was the open protocol for real-time communication and collaboration, and I really want to see that kept alive. Zachary Yaro On 15 March 2015 at 11:46, Thomas Wrobel darkfl...@gmail.com wrote: Thanks for that I'll look into both your Javascript API and your Android one. Is your communication between client and server just between your forked one or the standard wave server as well? If your approach is functional and everyone could agree to use it I feel a lot of progress could be made. ~~~ Thomas Bertines online review show: http://randomreviewshow.com/index.html Try it! You might even feel ambivalent about it :) On 15 March 2015 at 16:31, Pablo Ojanguren pablo...@gmail.com wrote: I’d like to clarify a bit more my work during the last year and a half, as I think it can respond to the needs that are being raised in this thread: - Wave storage based on Database - Server-Client separation - Reduce code complexity or cover it up - No dependency to GWT / Ability to build clients in modern frontend frameworks - Mobile support I’ve addressed basically all that: - Provided MongoDB storage for Waves - Discarded GWT client and replaced by a JavaScript API. Anyone can build Web apps in new frontend frameworks like AngularJS… - Extended Wave model to support general collaborative content: maps, lists and strings. You can use the Wave to store your own data. - The API is being adapted to work for Android and Java, although still experimental Some of them have been added to the original Wave project, but others are available in my forked version of Wave: The Wave platform including the general JavaScript API: https://github.com/P2Pvalue/incubator-wave Experimental port of the Wave API to Android: https://github.com/Zorbel/swell-android I will keep contributing to Wave... 2015-03-15 16:24 GMT+01:00 Thomas Wrobel darkfl...@gmail.com: Splash is an old client but looked like it was quite split from the server architecture. What am I missing? That its almost certainly not compatible with the current Wave sever code. Back when it was Google wave there was 4-5 clients, including prototype mobile ones. All died pretty soon after the transfer to Apache. I admit I havnt checked on Splash recently though, if its had a update in the past year to make it compatible again I wouldn't know. On 15 March 2015 at 12:09, Francesco Rossi f...@schermaontc.com wrote: Yuri suggested me in PVT some interesting open alternatives although I think they would still lack the options that Wave has. Just to name 2 of them: share.js rizzoma of course they have different functions, but at least they would share some Wave dna. the point is that coding on top of those solutions seemed a lot of work just to catch up with the features Wave has. but I'd be glad to be disputed at this point. Still, I'm a bit perplexed about the client/server conversation. I looked around and just for example, Splash is an old client but looked like it was quite split from the server architecture. What am I missing? On 3/15/2015 3:51 AM, Bruce Hellstrom wrote: The problem is technology keeps marching on while the wave project has remained mostly stagnant. I wanted to setup an internal wave server at our company and try to get it adopted as the company standard for our communications. I hate trying to manage email threads that get so long and disjointed. Wave was such a good solution. I wanted to wait until the db storage of waves support was put in, which is there now I believe. However, the company has started using Slack and I have to say it's hard to argue against that with a beta of Wave in it's current state. Slack has a lot of the features I was looking for in wave as well as clients that work on almost all mobile devices now. The downside is, the data storage resides with Slack and not on our own internal company servers, but that doesn't seem to be an issue. I think Wave is still an awesome product that was ahead of it's time, but now it would just take too much effort to bring it up-to-date. It needs to support all the latest incarnations of the browsers, which is a moving target now that almost all are on fast release cycles. It needs full mobile support apps. I just don't think there's enough people who have enough time to devote to all that needs to be done. On 03/15/2015 03:23 AM, Francesco Rossi wrote
Re: New committer: Andrew Kaplanov
I honestly thought he was already, but welcome, Andrew! I am a big fan of the work you have done over on wiab.pro and look forward to all the ways I am sure you will improve WIAB :D Zachary Yaro On 19 July 2014 17:57, Yuri Z vega...@gmail.com wrote: Wavers, Please join me in welcoming Andrew Kaplanov as the newest committer for the Apache Wave Incubator project. Andrew has been an active community member for the Apache project as well as working on wiab.pro fork. We are excited to have him on the team and look forward to his continued contributions. Welcome Andrew!
Re: [VOTE] Move Wave to a true 'git' repository at Apache
Move to git at Apache. —Zachary Yaro On 14 December 2013 01:37, Basavaraj K N [MaGE] basavaraj...@manipalglobal.com wrote: Mov to git -Original Message- From: Angus Turner [mailto:ad...@theangus.org] Sent: Saturday, December 14, 2013 6:56 AM To: wave-dev Subject: Re: [VOTE] Move Wave to a true 'git' repository at Apache Move to git Thanks Angus Turner e: h...@theangus.org m: 0424972516 On Sat, Dec 14, 2013 at 12:19 PM, Ali Lown a...@lown.me.uk wrote: As one of the main contention points, lets get Wave moved off the git-svn life support, and in to a true git repository. Since this would affect everyone (especially the other developers), I am just going to run a quick check here... This vote is open for 72 hours. [ ] Move to Git at Apache [ ] Retain Subversion I vote to move to true git. Ali Mailgate Notification - Note: Our email domain has moved to @manipalglobal.com DISCLAIMER - This email is for the sole use of the Manipal Group its Entities and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of the original message. MailGate uses policy enforcement to scan for known viruses, spam, undesirable content and malicious code. -- -
Re: Wave Kickstarter
@Thomas, if you like Java and GWT, you are in luck because there is already a wave project using those (I refer, of course, to WIAB). I think having Joseph's project be done in pure JavaScript (and I do prefer writing my JS directly rather than using another language that “compiles” into JS) is a great idea because it gives those of us who do *not* prefer Java a bigger way to contribute to the wave ecosystem. —Zachary Yaro On 1 December 2013 06:47, Thomas Wrobel darkfl...@gmail.com wrote: I still want a web client, but it should be written in pure javascript. GWT is already pure javascript. Writing Directly rather then via Java doesn't give any real advantages in the end result - it just means you rule out code sharing between client and server, an give yourself more work in terms of writing around browser differences and having to optimize for the web. There's things other then GWT that can do that, but raw javascript just adds a tone more work to web client development. That said, I pretty much agree with everything else. I would suggest, however, you need a few people ready to work on specific goals for a specific amount. And what can be achieved is kept very clear. Unfortunately no one will understand a kickstarter talking about OT. (or, not enough to get the money I think). It all needs to be put into real terms. Multiple clients and use's with a single federate realtime protocol is still a very big deal - no one has experience of that at the moment. The hard part is getting across all the use-case's for it. Or, rather, the specific ones you plan to make possible with the kickstarter. For my part, I am happy again to contribute (for free) whenever there is a separation of the GWT client. Or even a clean client/server protocol to build a new web client from stretch. Additionally, I have an Augmented Reality specific client application I wrote, coded for Android phones. The idea was anyone could annotate anything anywhere, and share it with whoever they want. The app is working (mostly)...except it has no sever to connect too. Nothing at the moment forfills the requirement. Once theres a client/server protocol to a wave server I could very quickly put out this (imho) rather cool Android client and I think it will attack a fair bit of attention. ~~~ Thomas Bertines online review show: http://randomreviewshow.com/index.html Try it! You might even feel ambivalent about it :) On 1 December 2013 06:09, Angus Turner ad...@theangus.org wrote: That's actually a really good idea. Id be happy to help out with organising. It sounds perfect for Wave, as there's tonnes of interest but not much programming ability. I would be interested in helping out with the actual programming but my expertise is in python not Java. On Sunday, 1 December 2013, Joseph Gentle wrote: I still really want to make the wave platform we've been talking about for awhile. I just don't have any time because I need to work to eat. So I've spent the last month thinking about running a kickstarter to fund the work. Christian's email was really timely. I want arbitrary JSON documents, or arbitrary embedding like we talked about a few months ago. I want a protocol based on real P2P algorithms rather than the hacky mess we have at the moment with trees of servers connecting via an XMPP extension I want the same fundamental protocol to work server-server or server-client. The OT stuff should work like git. No single person can maintain our 500k of legacy java code. I want to write a better version with much cleaner separation of OT protocol and application specifics. I still want a web client, but it should be written in pure javascript. Messages should be cryptographically secure from snooping. The way I see it, there's fundamentally three pieces that make up wave: 1. A set of OT primitives which allow peers to generate interpret operations 2. A platform on top of (1) for exchanging operations between networked peers 3. An application on top of (2) which is trying to replace email These pieces should be separate from one another, and usable in other contexts. I have a clear idea of how we can make (1) and (2) work. The OT part we've talked about on the list and I've been slowly prototyping out here: http://github.com/josephg/tp2stuff I have a bunch of applications I want to build on top of a platform like this. For example, I want my text editor, compiler unit tests to all talk to one another so my text editor doesn't need language-specific completion or syntax checking, and so my friends can jump in and help me code. I don't know what the best way to build (3) is - but I'm more than happy to build the platform that a new kind of email could be built on top of. Maybe the current WIAB design is totally fine for that part
Re: Incubation status
FWIW, I agree with Fleeky. Most of the extensions I have developed for Rizzoma have been because a bug or missing feature annoys me regularly. If people used WIAB regularly, I think they would start to notice glaring and subtle usability problems and be more inclined to fix them. —Zachary Yaro On 29 November 2013 17:55, Fleeky Flanco fle...@gmail.com wrote: thomas, i dont think there has even been enough testing of wave to prove this one way or the other but the main point is that if we are all using wave for something that matters, it will piss someone off enough to actually start to fix things. On Fri, Nov 29, 2013 at 11:53 PM, Thomas Wrobel darkfl...@gmail.com wrote: So are you confirming then that Wave as it stands can (stably) take very long discussion threads with lots of comments? I wasn't even aware the storage format of the current Wave builds was final. Maybe more has progressed in the last year then I was aware of. ~~~ Thomas Bertines online review show: http://randomreviewshow.com/index.html Try it! You might even feel ambivalent about it :) On 29 November 2013 23:44, Fleeky Flanco fle...@gmail.com wrote: christian, from my observations of the project i would have to answer no, its not working out ? pardon my passion on this subject (@mailing list) but ive kept quiet for too long. id rather get an argument started on this rather then let wave die the slow death that it is currently facing. passion is what wave needs right now, not patience. i dont think moving wave to github or getting everyone to actually use wave will magically make everything better, but i think that is a step in the right direction that Should have been taken a long time ago. theres no reason that moving discussion to a wave server reduces the open nature of the discussion, as stated previously, its trivial to make an anonymous account to grant anyone access to this discussion if it was on a wave server. also anyone can register on a wave server and participate in the discussion if the wave has been setup properly, theres even a patch somewhere for rendering wave files as html files which would make it searchable by google and everyone esle. federation should make propogating this data to multiple servers possible, using wave as the main discussion area maintains the openness , searchability, and also longevity of the discussion. On Fri, Nov 29, 2013 at 9:41 PM, Christian Grobmeier grobme...@gmail.com wrote: On 29 Nov 2013, at 16:40, Fleeky Flanco wrote: i really dont understand why i have to be explaining the usefullness of using wave to communicate with the people on this list. its kindof amazing. If you don't understand why we operate on a mailing list then you probably have not understood that the ASF tries to develop in an open way. All discussions must held public and must be archived for a long time. The only solution so far is mailing lists. Wave is simply not that far to provide that at the moment. Of course there is an opportunity to bring Wave to the ASF. But there are a lot of requirements to meet. If you want to develop here, you need to fulfill these requirements. We have discussed that several times. Every of the committers understood these requirements and were working against them. However Wave is not there yet. This doesn't answer the question which was initially asked: is the ASF the right place? Or more precise: can we as a project ever succeed the incubator and become an ASF project? This has nothing to do with the great technology behind Wave nor the willingness of people. It is: is there enough manpower to live the ASF way or not. Christian fleeky On Fri, Nov 29, 2013 at 4:19 PM, Robert Brumbelow rkbrumbe...@gmail.com wrote: Fleeky, those are fine for us, they will do little for outside exposure. I would suspect having to use wave in order to learn to use wave might be self defeating. On Fri, Nov 29, 2013 at 10:05 AM, Fleeky Flanco fle...@gmail.com wrote: https://cwiki.apache.org/confluence/display/WAVE/Building+Wave+in+a+Box https://cwiki.apache.org/confluence/display/WAVE/Home also there is #wiab on irc.freenode.net also Ali just a few emails up mentioned that you could start a discussion on his wave server , why not try those things first? and if there is a problem, go to Ali's wave server and simply start a problems wave add the participant @domain to the wave and everyone inclduing Ali on that server should be able to see your problem wave, and maybe attempt to answer your problem. -fleeky On Fri, Nov 29, 2013 at 4:01 PM, Robert
Re: Incubation status
It seems like this sort of discussion comes up whenever Apache asks us about our status. Suddenly people who have not commented in months bring up how they can support the project. Having Apache give us deadlines seems to be the greatest source of motivation. If we move to GitHub, where will that motivation come from? I will join the “here is what I can do” party by saying my best skills remain JavaScript(+HTML+CSS) and Python, so I will happily work on a client once the server and client are separated and other clients can be developed, but there is relatively little I can do right now on the main WIAB project. I continue to work on gadgets, the WEGhttp://waveextensions.org, and wave-related Chrome extensions. —Zachary Yaro On 28 November 2013 11:36, Thomas Wrobel darkfl...@gmail.com wrote: On 28 November 2013 15:41, Frank R. renfeng...@gmail.com wrote: Hi Ewan I agree with you. Here are my skills. - Competent in GWT, i.e. Java + HTML + CSS + JS. The UI of wave is built with GWT, right? - Basic understanding in XMPP. - More on my Google+ profile https://plus.google.com/u/0/+FrankR/about My available hours should be flexible. Maximum, 10 hours. Yes, the client is GWT based. For what its worth I am much the same. - GWT Java + HTML/CSS/ (a little) Javascript. - Java for Android (if the client was separated, I am confident enough to make at least a basic Android client). - Php/MySQL. - Some flash/actionscript but Id rather not. - Commodore Basic 3.1 Could contribute about 10 hours a week easily. -Thomas Wrobel
Re: Why does nobody vote on the release? (was: Fwd: Re: [VOTE] Release Wave 0.4 based on RC4)
Yes, thank you, I really appreciate the additional clarification. Should I send such a vote to the RC4 vote thread, or is there going to be a later RC5 thread I should wait for? —Zachary Yaro On 14 September 2013 04:26, Ali Lown a...@lown.me.uk wrote: Also, don't assume you need to be a committer to vote. I thought I had to be. So can any member of the community vote? How much do I need to know about the code to submit a vote? For instance, I do not know much about how federation works behind-the-scenes, but I can give my opinion on the UX... It is slightly more subtle than that. Whilst the voting documentation states that only committers/PMC can vote - it really means that they have binding votes (so if we had lots of +1 from the community, but a PMC voted -1, their vote would 'override' the community votes). However having lots of community votes is a good sign to the incubator - since it shows that the project's community is active - and it is even plausible that the community might find things that we don't (due to trying the release in lots of different ways). If you can only review part, that is still fine. Place your vote and simply state that you were only able to review the UX. Does this clarify it a bit? (I agree that perhaps I hadn't been clear in the past) Ali
Re: Why does nobody vote on the release? (was: Fwd: Re: [VOTE] Release Wave 0.4 based on RC4)
Also, don't assume you need to be a committer to vote. I thought I had to be. So can any member of the community vote? How much do I need to know about the code to submit a vote? For instance, I do not know much about how federation works behind-the-scenes, but I can give my opinion on the UX... —Zachary Yaro On 13 September 2013 14:00, Upayavira u...@odoko.co.uk wrote: Bruno, You are kinda right, and kinda not :-) I guess the thing is, it is perhaps best to say that this release *ISN'T* about code, it is about everything else. And that everything else includes licensing, but also includes the communities ability to self manage. Therefore, I'd suggest that everyone review the release as best they can, from both a licensing and a code perspective. You can state in your vote what you checked and what you didn't. All you are stating is that you checked to the best of your abilities. Over time, I hope we'll all get better at knowing what to look for. That's why we pass the release vote on to the Incubator PMC - to have folks more experienced also give it a once-over, so that we don't yet need to worry too much about knowing what we are doing. Also, don't assume you need to be a committer to vote. I'd love to be able to forward this vote to the incubator PMC saying we had 15 +1 votes :-) Upayavira On Fri, Sep 13, 2013, at 06:13 PM, Bruno Gonzalez (aka stenyak) wrote: I was under the (maybe incorrect) impression that these releases are not focused on the code per se, but rather on getting the release process right: solve copyright and licensing issues, correct packaging of third party libraries, and similar issues. If that assumption is correct, at the moment I can not be of much help; Ali and veteran Apache members know heaps more than I do, so I wouldn't be able to provide a *meaningful* vote without first carefully studying the Apache requisites. However, if code is (very) relevant, I may have time to test it later this weekend. (holidays, real life issues, and three hard disks failing in almost-consecutive days, have been stopping me from testing the RC). For the record, I've tested Ali's federation patches in the past, since most of them had been in his github repo for weeks already: they do improve the stability, and is a very nice and welcome improvement over the previous status of wiab federation. Only for that, I'd provide a +1 vote. Though as I mentioned, I have not really tested those patches in the exact form as they are included in the latest RC4. On Thu, Sep 12, 2013 at 8:36 PM, Christian Grobmeier grobme...@gmail.comwrote: Am 12.09.13 20:35, schrieb Ali Lown: It seems nobody else is able to give feedback at this point. Christian raised some things that are worth doing, so I may as well start again with RC5, which I will push up in a few weeks time. [It is a bit too busy for me ATM.] Hopefully, by being a bit later, people won't be on holiday, so will be able to review it. :P I would say save the time for now. It has been 2 weeks time for voting. This project has seen messages. It's september, not mid of august. We got 1 (!) community vote. Vincente mentioned he is away (thats fine) and John is not so much into gory technical details (accepted so far). But where were the others? Is it really holidays which prevents the vote? Do we ALL have holidays at the same time? Before we move on with a new RC, i would like to know from the people listed here: http://people.apache.org/committers-by-project.html#wave why they didn't vote.** Was it really holidays? No interest? No time? It has been *a lot* of work for Ali to deal with the ASF release procedures and kick out multiple RCs. It would be worth to know if he should continue and if there will be any voters in the future. If there is nobody who is willing to open a zip file, look into it and send out a +1, then its really alarming. It took me 30 minutes or so to check the release. This is not so much. I have hoped the excitement in the project after John and a few others appeared was so big that we would have managed to get a new release out for review. If others, maybe Incubator Shepherds* look at this project now, they would think: no community. Please let me - us - know what you who are on the list above prevented to vote**. Cheers*** Christian * Incubator Shepherds are Incubator PMC people, who look independently from the mentor on the activity of the project and provide a second insight for the report ** Of course I don't want you to speak out anything which should be kept private - remember this is a public list. I just want to know: is there a realistic chance that we ever get more than 3 votes? 3 are required to get it out, but given the huge list of committers we should get more votes
