Re: Incubation

How do i unsubscribe from this mailing list? On 8 October 2015 at 08:07, Upayavira wrote: > Remember, this is a release for legal reasons, not technical. Do not let > *any* technical concern block its release. If a valid legal concern > (e.g. it doesn't pass a RAT run) then fix and reroll immedi

Re: Incubation

Remember, this is a release for legal reasons, not technical. Do not let *any* technical concern block its release. If a valid legal concern (e.g. it doesn't pass a RAT run) then fix and reroll immediately. The only thing that could take dev work is the removal of non-compliant dependencies. But i

Re: Incubation

Upayavira, I do concede that after watching over Wave here for the last 3 years the project doesn't appear to have progress hugely far in terms of new user-visible functionality, but I don't think that this means the end, as there has been a slow-but-steady set of work on more underlying things -

Re: Incubation

Does seem reasonable, I would like to know yuri's and ali's opinion on the matter as they have been the care takers of wave for some time in the daily sense. I willing to put in more work to build up the Apache Wave community and would greatly appreciate the help from the Apache committers (as I am

Re: Incubation

That is a reasonable response, Evan. So, let's look at what graduation might look like, then we can see about what goals might be reasonable: A podling must have: 1. proven its ability to produce legally correct releases 2. demonstrated its ability to vote in new committers and PPMC members 3. a

Re: Incubation

maybe instead of deciding the end instead you and Christian set goals that must be completed by the next checkpoint aka have x amount of submits, have x more active contributors to help gain momentum. If the tasks are not completed sufficiently or dismally fail then sure maybe its for the best. On

Re: Incubation

Well as the video discussion we had earlier this year, the main problem has been the complexity. We have been taking steps in this direction with; * reducing technical debt (removing updating dependencies), can bee seen from patches last week and there has been work in a gradle or sbt build system

Re: Incubation status

Please do NOT use Google Groups - that interface is virtually impossible to work with - PINTA - please use a real listserver. If moving to Github, try Octopress +1 Thx - Ed On Fri, Nov 29, 2013 at 7:35 PM, Joseph Gentle wrote: > We should keep a mailing list (on incubator.apache.org or on google

Re: Incubation status

Just a random thing that might help wave in a small way; StackOverflow still only has a tag for "Google-Wave". Surely this should be changed? or someone with a high enough rank create a new tag? Just try to help as much as possible greese the wheels for people finding wave related technical info.

Re: Incubation status

Good points, Bruno, I think that you summed it up very well. I'd only add that in theory the broader Apache community should act as a draw for the project, but the social infrastructure for Apache doesn't seem to amplify that value for Wave. A more flexible approach might help to get a core group o

Re: Incubation status

Hi Bruno, On 5 Dec 2013, at 16:09, Bruno Gonzalez (aka stenyak) wrote: Technical point of view: A big point for staying at Apache is that we have a big infrastructure already in place: issue tracker, code repository, wiki, mailing list, possibility to use virtual machines for free, etc. However,

Re: Incubation status

Hi all, sorry to reply this late, but here's my point of view. Legal point of view: >From my understanding, being at Apache, and following its strict policies, should in theory attract serious companies to invest money into the project, being reassured that the legal risks are minimal. Unfortunat

Re: Incubation status

It sounds as though the project has momentum on two or more compatible fronts. I'm most interested in the mavenization effort and would be happy to help test. -R On Sun, Dec 1, 2013 at 7:46 PM, Michael MacFadden < michael.macfad...@gmail.com> wrote: > I would still be more than happy to press

Re: Incubation status

@Thomas Wrobel. This is probably a matter of discussion for another time in terms of what the consensus is, especially since I haven't been an active part of that consensus for a long time. But I would agree that not enough talent willing to focus on Wave is a big problem. It's not clear that Gith

Re: Incubation status

It sounds as though the project has momentum on two (or more?) compatible fronts. I'm personally very interested in the mavenization effort and would be happy to help test. -R On Sun, Dec 1, 2013 at 7:46 PM, Michael MacFadden < michael.macfad...@gmail.com> wrote: > I would still be more than

Re: Incubation status

On 2 December 2013 18:57, Fleeky Flanco wrote: > i think the most usefull reason to move to github, is that one of the only > active coders feels like doing it .. hence we should support that person :) +1 Provided none of the other active coders disagree, I think thats pretty much the only argu

Re: Incubation status

i think the most usefull reason to move to github, is that one of the only active coders feels like doing it .. hence we should support that person :) On Mon, Dec 2, 2013 at 5:01 PM, Thomas Wrobel wrote: > "But for > that commitment, we need more consensus about what Wave should try to be " > >

Re: Incubation status

"But for that commitment, we need more consensus about what Wave should try to be " Is there really a lack of consensus here? I think , imho, we have a consensus, just not the skill/time. ~~~ Thomas & Bertines online review show: http://randomreviewshow.com/index.html Try it! You might even feel

Re: Incubation status

Christian, Although I support the incubator's goals, it seems that there is probably a fundamental mismatch between the state of Apache Wave and where and how Wave needs to develop. I am one of the people who had to stand back from Wave a while back. I was enthusiastic about the possibility of Ap

Re: Incubation status

Hi Guys, I don't normally say very much on this list but I keep a keen eye on what is going on, because I have over the last 12/18 months been trying to bring my knowledge of GWT, Java and eclipse up to a point where I can use these tools and potentially use WIAB as part of a project I'm working on

Re: Incubation status

Personally, I'd say do anything that helps people work. The release is important in Apache terms, but right now, we're looking at how to have a community at all. A release with no community to back it wouldn't give the world much. So, if folks think that Mavenization helps, and will ease developm

Re: Incubation status

I would still be more than happy to press through the mavenization, but it seemed like people were some what against the idea until we got the release out the door historically. Thoughts? On 12/1/13, 5:37 PM, "Frank R." wrote: >It'll get slim once mavenized. > > >On Mon, Dec 2, 2013 at 6:06 AM,

Re: Incubation status

It'll get slim once mavenized. On Mon, Dec 2, 2013 at 6:06 AM, Angus Turner wrote: > It is quite a large repo :) > > Thanks > Angus Turner > angusisf...@gmail.com > > > > On Mon, Dec 2, 2013 at 9:05 AM, Thomas Wrobel wrote: > > > No problem, at the moment its still checking out. > > I'll note

Re: Incubation status

Thank you. I got it. Email bridge bot On Mon, Dec 2, 2013 at 1:04 AM, Ali Lown wrote: > Christian is referring to > CAORBtqwYOCXJK3r2QqFhqP+YQ0fas_m4

Re: Incubation status

It is quite a large repo :) Thanks Angus Turner angusisf...@gmail.com On Mon, Dec 2, 2013 at 9:05 AM, Thomas Wrobel wrote: > No problem, at the moment its still checking out. > I'll note down any other issues other then those two as I get any. > (Actually still on WindowsXP here ;) ) > > ~~~

Re: Incubation status

No problem, at the moment its still checking out. I'll note down any other issues other then those two as I get any. (Actually still on WindowsXP here ;) ) ~~~ Thomas & Bertines online review show: http://randomreviewshow.com/index.html Try it! You might even feel ambivalent about it :) On 1 Dec

Re: Incubation status

Or a wave ;) On a more serious note this is something that needs doing - and something I've been meaning to do for a while. Start with a clean slate on each major OS (Mac OSX, Ubuntu, Win8 and possibly WinXP) and write down exactly what needs doing or what errors come up. If you begin to do this i

Re: Incubation status

ora wave? ;) It is sort-of on-topic to the earlier discussion as to "how to get more activity". But yes, it might be getting too sidetracked. ~~~ Thomas & Bertines online review show: http://randomreviewshow.com/index.html Try it! You might even feel ambivalent about it :) On 1 December 20

Re: Incubation status

A wiki page or a new thread might be better for this - kind of off topic... Thanks Angus Turner angusisf...@gmail.com On Mon, Dec 2, 2013 at 8:34 AM, Thomas Wrobel wrote: > ok, svn checkout; > > Note #1: Get an > "Error validating server certificate for https://svn.apache.org:443: > Unknown c

Re: Incubation status

ok, svn checkout; Note #1: Get an "Error validating server certificate for https://svn.apache.org:443: Unknown certificate issuer. Fingerprint: bc:5f:40:92:fd:6a:49:aa:f8:b8:35:0d:ed:27:5e:a6:64:c1:7a:1b Thawte, Inc., US" I accept once and proceed. (I am just documenting anything that might put

Re: Incubation status

cheers :) ~~~ Thomas & Bertines online review show: http://randomreviewshow.com/index.html Try it! You might even feel ambivalent about it :) On 1 December 2013 21:35, Yuri Z wrote: > The latest source code: > http://incubator.apache.org/wave/source-code.html > > > On Sun, Dec 1, 2013 at 8:19

Re: Incubation status

The latest source code: http://incubator.apache.org/wave/source-code.html On Sun, Dec 1, 2013 at 8:19 PM, Thomas Wrobel wrote: > On 29 November 2013 16:05, Fleeky Flanco wrote: > > > https://cwiki.apache.org/confluence/display/WAVE/Building+Wave+in+a+Box > > > > https://cwiki.apache.org/conflu

Re: Incubation status

On 29 November 2013 16:05, Fleeky Flanco 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 Ok, trying to follow this guide to setup for client development. Stu

Re: Incubation status

Christian is referring to CAORBtqwYOCXJK3r2QqFhqP+YQ0fas_m4U0oHX7AZiswm6CwPyQ By 'search the archives' - yes, you can sometimes use Google for the task. But sometimes, it is easier to simply manually look through them for a subject that describes what you are searching for. (In this case 'email br

Re: Incubation status

Thanks for the response. But, I don't think it can be a trivial task to find the old mails. Because all the key words I can think of are too commonly seen: wave, mail list, communication. e.g. site:mail-archives.apache.org/mod_mbox/incubator-wave-commits/ communication - Google Search

Re: Incubation status

On 1 Dec 2013, at 15:35, Frank R. wrote: Perhaps, we can have a temporary robot, say incubator-bot, to publish waves for a wave in a box server back to the mail list. That should be too difficult to have. Please search older mails in the archive. Somebody actually did some work in that direc

Re: Incubation status

On 1 Dec 2013, at 15:33, Frank R. wrote: Where to read the requirements? And, the status of the works against them? Here is some information you might find useful: http://www.apache.org/foundation/how-it-works.html Please see the "communication" section in special. So far I have seen the pro

Re: Incubation status

Perhaps, we can have a temporary robot, say incubator-bot, to publish waves for a wave in a box server back to the mail list. That should be too difficult to have. On Sat, Nov 30, 2013 at 6:44 AM, Fleeky Flanco wrote: > christian, from my observations of the project i would have to answer no, >

Re: Incubation status

Where to read the requirements? And, the status of the works against them? Thanks. On Sat, Nov 30, 2013 at 4:41 AM, Christian Grobmeier 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 communicat

Re: Incubation status

On Sat, Nov 30, 2013 at 12:10 AM, Fleeky Flanco wrote: > ok , what i would like to know. > > who among you on this mailing list is actually using wave in some capacity > ? and for what ? do you run your own wave server ? if not why ? > I have 30 waves on my own server. The others in my team have

Re: Incubation status

What is the username of the participant that I should invite? Thanks. On Fri, Nov 29, 2013 at 11:05 PM, Fleeky Flanco 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.freeno

Re: Incubation status

Brilliant! I created an event. I'll share my limited experience. Everyone is welcomed to join. On Fri, Nov 29, 2013 at 10:23 PM, Robert Brumbelow wrote: > Or, it might be worthwhile to do a 'hangout on air' video or a screen > cast of i

Re: Incubation status

Will the problem get solved if the delta store is built on mongodb? I've created an issue for this. [WAVE-399] Mongodb delta store - ASF JIRA https://issues.apache.org/jira/browse/WAVE-399 On Thu, Nov 28, 2013 at 11:32 PM, Fleeky Flanco wrote: > @Fleeky: > >lets finally have discussion for deve

Re: Incubation status

Hi Ali Please invite me to the discussion wave. My wave id is fr...@wave-dev.alown.co.uk Regards, Frank On Fri, Nov 29, 2013 at 12:15 PM, Ali Lown wrote: > For those calling for a new place to both > a) dogfood the product > b) discuss the next development stage > at the same time! > > Regist

Re: Incubation status

We should keep a mailing list (on incubator.apache.org or on google groups) until we can host these discussions in wave itself. We can arrange google hangouts just as easily. -J On Fri, Nov 29, 2013 at 5:56 PM, Evan Hughes wrote: > By moving to github will the community there be able to communic

Re: Incubation status

By moving to github will the community there be able to communicate as easily as we do here. I have no experience working on any long term gothic projects but in asf we can easily arrange for hangout debates which would need to be recorded for public view. Tbh I agree with deadlines and emails lik

Re: Incubation status

very simple workaround, have everyone reply to everything in one blip, but to append there name to things they say. this way you keep blip count low. the state of wave imo is that its a blank slate, you have to impose your own organizational structure onto each wave, and how you do that dictates h

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

Re: Incubation status

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 wr

Re: Incubation status

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

Re: Incubation status

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

Re: Incubation status

I totally agree. - We should move to github - I agree that there isn't enough work devoted to WIAB to keep it alive in its current state - We should move discussion to WIAB, once its ready for that I'd love to throw more time and energy into WIAB - I really would, but the reality is that I'm work

Re: Incubation status

People, I love you all :) Chill out. Och aye! Sent from my BlackBerry® smartphone -Original Message- From: "Christian Grobmeier" Date: Fri, 29 Nov 2013 21:41:17 To: Reply-To: wave-dev@incubator.apache.org Subject: Re: Incubation status On 29 Nov 2013, at 16:40, Fle

Re: Incubation status

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 th

Re: Incubation status

Fleeky, Plonk On Fri, Nov 29, 2013 at 11:10 AM, Fleeky Flanco wrote: > ok , what i would like to know. > > who among you on this mailing list is actually using wave in some capacity > ? and for what ? do you run your own wave server ? if not why ? > > personally i run my own wave server, and use

Re: Incubation status

ok , what i would like to know. who among you on this mailing list is actually using wave in some capacity ? and for what ? do you run your own wave server ? if not why ? personally i run my own wave server, and use it mainly as a google doc replacement. robert, first off which people are you ta

Re: Incubation status

Fleeky, "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." [sic] Probably because you have flawed presuppositions. I assume people who have never seen Wave have never seen Wave, not that they know

Re: Incubation status

I would guess people dought the maturity of wave rather then the usefulness. Is it stable with large numbers of blips? large numbers of commentators? Not saying it isn't - but the principle of wave I think we are all for. I think the only questions are if it can be used to an acceptable standard r

Re: Incubation status

robert if using wave to learn wave is self defeating , i think wave the purpose of wave has been lost. wave is a communications platform, if it cant communicate how to use itself doesnt that seem a bit silly? an ideal situation would be publicly viewable waves that are potentially read only , or

Re: Incubation status

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 wrote: > https://cwiki.apache.org/confluence/display/WAVE/Building+Wave+in+a+Box > > h

Re: Incubation status

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? a

Re: Incubation status

Thomas, Hangouts on air are the recorded versions of Google Hangouts, they are streamed and recorded via Youtube. Screencasts, I thought, also defaulted to being recorded. I know during my years of teaching, video was often preferred by students simply because even in step by step instruction

Re: Incubation status

If its done that way it really would need to be recorded too. I am not too keen on video tutorials myself, as it brings in time-zone issues, and I prefer to go at my own pace. But, really, that's just my personal preference. For this sort of thing its always whatever the tutors preference is. ~~~

Re: Incubation status

Or, it might be worthwhile to do a 'hangout on air' video or a screen cast of installation / config / admin use. On Fri, Nov 29, 2013 at 9:14 AM, Jon wright wrote: >> So, it appears that I could do with running some 'tutoring' sessions >> with people to cover >> a) Running a server >> b) Advance

Re: Incubation status

+1 to all that. I think some basic guides online to "getting it working enough to get started coding" would help a lot. (and client coding specifically for us GWT-ers) After the basics are written, and I myself use them to get myself started, I could tidy them up/flesh them out a bit. I wouldn't w

Re: Incubation status

> So, it appears that I could do with running some 'tutoring' sessions > with people to cover > a) Running a server > b) Advanced server admin: a) SSL, b) Federation > c) Codebase overview - with a focus on the client side for all the GWT > coders around. > > Ali That would be really useful and we

Re: Incubation status

Ali , YES do all of that , and make a post about it on your wave server :) im tensy on there btw, actually ive been running a wave server for a while and the one thing im still hung up on is ssl and federation.. i think the biggest thing Everyone on this list could do is to get a wave server up an

Re: Incubation status

@Christian: You have summarised it well for me, in the despite repeated attempts to get a community, Wave has been unable to sustain active development here. @Thomas, Jon Am I the only person who is actively still setting up wave servers? (Correct me if I am wrong on this). Setting up RC4 to run,

Re: Incubation status

> > Perhaps if other "potential coders" gave reasons for their lack of commits > it would help paint a picture of whats holding Wave back? > For me personally its the learning curve that comes with a massive codebase and little documentation or even overview of how the classes etc relate to each o

Re: Incubation status

On 29 Nov 2013, at 14:28, Thomas Wrobel wrote: ". No need to discuss if somebody has experience in GWT or not. IF you want to contribute, just DO it. Checkout code, send patches. Its open to all." I think the point was that having experience with GWT does not necessarily give you the experience

Re: Incubation status

Hello All. I think its important to consider whether staying at Apache is even a choice at this juncture. This is the second time Christian has raised question about incubator being a suitable place for Wave. It appears that Apache expects given amount of activity/progress for a project to be cons

Re: Incubation status

". No need to discuss if somebody has experience in GWT or not. IF you want to contribute, just DO it. Checkout code, send patches. Its open to all." I think the point was that having experience with GWT does not necessarily give you the experience enough to make contributions. I could easily don

Re: Incubation status

On 29 Nov 2013, at 13:50, Raphael Bircher wrote: Hi Upayavira Am 29.11.13 13:24, schrieb Upayavira: The way open source communities such as this one work, the road map needs to be defined by the people doing the work. It would be easy for some of us to come up with a cool roadmap, but if code

Re: Incubation status

Hi Upayavira Am 29.11.13 13:24, schrieb Upayavira: The way open source communities such as this one work, the road map needs to be defined by the people doing the work. It would be easy for some of us to come up with a cool roadmap, but if coders aren't behind it, it will be pointless effort. Th

Re: Incubation status

The way open source communities such as this one work, the road map needs to be defined by the people doing the work. It would be easy for some of us to come up with a cool roadmap, but if coders aren't behind it, it will be pointless effort. If folks are interested in coding Wave, whether at Apac

Re: Incubation status

Wave really lacks a roadmap? Surely that's something that could be hammered out, at least in rough, in this mailing list? Seems to be some agreement on the need to separate client/server. And I guess with that comes the need for a documented protocol between the two. Is there other prerequests for

Re: Incubation status

Hi Im on vacation & am writing from my phone... I really just wanted to add that I have been lurking on the mailing list to try & get a feel for the project. I am Looking forward to working on it irrespective of org form. Jeff Ali Lown wrote: >@Christian: >>Playing the devils advocate I ask you

Re: Incubation status

Hi Ali Am 28.11.13 15:18, schrieb Ali Lown: I am still massively enthusiastic about WFP as a communication method, and making a good reference client and server is the way to push it. This I agree with, but it also tells us what our actual aim should be: A clearly separated library for using

Re: Incubation status

For those calling for a new place to both a) dogfood the product b) discuss the next development stage at the same time! Register an account on https://wave-dev.alown.co.uk, and join the discussions. (Shameless plug) Ali On 28 November 2013 15:32, Fleeky Flanco wrote: > @Fleeky: >>lets finally

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 tha

Re: Incubation status

On 28 November 2013 15:41, Frank R. 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

Re: Incubation status

@Fleeky: >lets finally have discussion for development happen on a public wave ;) I agree that the dogfooding should really have been a thing, but it hasn't been possible here. (Though I hestitate to say whether Wave is stable enough for multiple users heavily editing a Wave - my anecdotal data sa

Re: Incubation status

Hi, On 28 Nov 2013, at 15:18, Ali Lown wrote: @Christian: Playing the devils advocate I ask you (again): Is this still Devil's advocate though? I have had a very similar email sitting in my drafts for the last month asking the same questions about the future of Wave. Sad :-| Do you folks

Re: Incubation status

I put some inline comments. Hope it won't be too hard to read. On Thu, Nov 28, 2013 at 10:18 PM, Ali Lown wrote: > @Christian: > >Playing the devils advocate I ask you (again): > > Is this still Devil's advocate though? I have had a very similar email > sitting in my drafts for the last month a

Re: Incubation status

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 My available hours should be flexible. Maxim

Re: Incubation status

@Christian: >Playing the devils advocate I ask you (again): Is this still Devil's advocate though? I have had a very similar email sitting in my drafts for the last month asking the same questions about the future of Wave. >Do you folks believe the incubator can ever be completed as it is now? >I

Re: Incubation status

> > move it away from incubation Will it make any difference? I'm working at a company where Google Drive, Evernote, and other third party cloud applications are forbidden. I found Wave in a Box a good replacement. Recently, I made some effort on full text search

Re: Incubation status

Hi, I joined the mailing list a couple of months ago with every intention of contributing but unfortunately life & work has got in the way. >From my perspective what would really help would be some kind of developer "on boarding" process. Have one of the more established developers reach out to

Re: Incubation status

Speaking as someone unable to contribute code to the client as its too heavily tide into the server (which I cant make heads not tails of), how will any move effect things? how will it help? wont it just be rearranging things again that have little, if anything, to do with getting anything actually

Re: Incubation status

also if we move it to github, lets finally have discussion for development happen on a public wave ;) On Thu, Nov 28, 2013 at 2:23 PM, Fleeky Flanco wrote: > i completely agree to move it away from incubation, i think we should move > it out of github make federation easier and then market it o

Re: Incubation status

i completely agree to move it away from incubation, i think we should move it out of github make federation easier and then market it on places like reddit. my 2 cents as someone who has been happily using this for sometime but sad at the lack of progress. thanks for the devs who do work on it th

Re: Incubation status

Hi Evan You already have it - wave on github. Here, https://github.com/apache/wave Glad to know someone like you is still interested in wave :) Frank On Thu, Nov 28, 2013 at 8:09 PM, Evan Hughes wrote: > As a student I first experienced Google wave back when I was in grade 8 and > at the time

Re: Incubation status

+1 github, it will be a better context for both the project and community. Sent from my iPhone > On 28-11-2013, at 9:09, Evan Hughes wrote: > > As a student I first experienced Google wave back when I was in grade 8 and > at the time couldn't contribute or really take advantage of the system.

Re: Incubation status

As a student I first experienced Google wave back when I was in grade 8 and at the time couldn't contribute or really take advantage of the system. I followed it to 'wave in a box' and to the incubator but only just learning the programming skills to contribute in development. I was looking forward