Re: Incubation

this work is required for the PPMC is because it is one of > the primary responsibilities of members of an Apache PMC, and is one of > the skills that projects must learn during incubation. > > Upayavira > > On Thu, Oct 8, 2015, at 03:58 AM, Ali Lown wrote: > > Upayavira, &g

Re: Incubation

arn during incubation. Upayavira On Thu, Oct 8, 2015, at 03:58 AM, Ali Lown wrote: > 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&#

Re: Incubation

moving towards being >> >> fully fledged ASF projects. Wave has been >> >> incubating since 2010, and in that time it has not yet been able to >> >> build a community that is likely to sustain itself as an ASF >> >> project. >> >&g

Re: Incubation

The Apache Incubator exists to facilitate projects moving towards > being > > >> fully fledged ASF projects. Wave has been > > >> incubating since 2010, and in that time it has not yet been able to > > >> build a community that is likely to sustain itself as

Re: Incubation

gt;> > >> It does, therefore, seem to me that it is time for us to retire as a > >> podling, and allow people here to continue in a location more fitting > >> with the current level of effort, without the expectation that it needs > >> to meet some specific set of incubation requirements. > >> > >> Note that all of the source code is Apache Licensed, meaning it can be > >> forked elsewhere - the only discussion required is the name that the > >> relocated project would take. > >> > >> Thoughts? > >> > >> Upayavira > >> > > > >

Re: Incubation

that is likely to sustain itself as an ASF >> project. >> >> It does, therefore, seem to me that it is time for us to retire as a >> podling, and allow people here to continue in a location more fitting >> with the current level of effort, without the expectation th

Re: Incubation

d allow people here to continue in a location more fitting > with the current level of effort, without the expectation that it needs > to meet some specific set of incubation requirements. > > Note that all of the source code is Apache Licensed, meaning it can be > forked elsewhere

Incubation

itself as an ASF project. It does, therefore, seem to me that it is time for us to retire as a podling, and allow people here to continue in a location more fitting with the current level of effort, without the expectation that it needs to meet some specific set of incubation requirements. Note

Re: Wave and Incubation

Ali, I don't know off any concrete event. But I know for sure it is possible. Basically, the project would need to find another set of mentors/champion is it needed to do with this incubation. I can imagine people may ask what is the difference from the previous incubation trial. A projec

Re: Wave and Incubation

Christian, This seems to be the age-old Wave problem. Regarding your last comment, is there any precedent for a project leaving Apache and returning at future point - it does seem like a strange set of circumstances would be needed to trigger it? Ali On 23 March 2015 at 14:06, Christian Grobmei

Re: Wave and Incubation

Hi, if Wave moves out this list, Jira etc will be read only, but available. Same for the current source code. I agree with 1: in the end Apache is a strong brand and also shows that you can rely on a few things. However at this point we know the benefits of Apache, but can this project also fulf

Re: Wave and Incubation

> Also, is there a general repository for all the contributions that have > been done so far from the Community? More than git: http://incubator.apache.org/wave/source-code.html maybe the reviews: https://reviews.apache.org/groups/wave/

Re: Wave and Incubation

El 17/03/15 a las 18:41, Yuri Z escribió: > I agree that from the point of view of adding to the source/experimenting - > there's no advantage to staying with Apache. However, there are other > reasons. > 1. Doing a release will signify that the code base is free of legal issues > and thus encourag

Re: Wave and Incubation

Yuri, Please know that there’d be no reason (as far as I am aware) that current data would be removed from JIRA/Wiki/etc. It would simply be marked read-only. I don’t know whether it’d be possible to add a forwarding message to the top of such pages. Upayavira On Tue, Mar 17, 2015, at 05:41 PM,

Re: Wave and Incubation

I concur with Yuri. One thing I would add is that a lot of knowledge is actually dispersed in this mailing list. It would not be bad to have a forum on which to engage at least a mainstream part of the community. Information would be searchable and more accessible. Also, is there a general rep

Re: Wave and Incubation

I agree that from the point of view of adding to the source/experimenting - there's no advantage to staying with Apache. However, there are other reasons. 1. Doing a release will signify that the code base is free of legal issues and thus encourage adoption of it by other parties, like wiab.pro, co

Re: Wave and Incubation

Hi, I guess this is my first post to this list, even though I am subscribed for a year or so know and "following" the discussions here. The technology in Wave seems quite amazing to me (in particular the federation part, which hardly any commercial entity would add to their product out of a busin

Re: Wave and Incubation

gt;> I would like to highlight that retirement does not mean end of life. > >>>>> There is a chance thing will get easier once on GitHub. Don't > >>>>> forget, Apache is not only a great community, it's also a set of > >>>>> rules,

Re: Wave and Incubation

t;>>> community. But the Wave community hardly is able to allocate time to >>>>> do that final step with the release. No offense, I know for myself >>>>> how hard it is to allocate time. >>>>> >>>>> In a GitHub environment, Wav

Re: Wave and Incubation

, Wave would have done that release already (or most likely). I agree, that protocols may have a good place at Apache. But just because retirement is not successful​ this time does not mean it's not successful another time. If Wave can build up a community, it can always come back to incubatio

Re: Wave and Incubation

b environment, Wave would have done that release already > > > (or most likely). > > > > > > I agree, that protocols may have a good place at Apache. But just > > > because retirement is not successful​ this time does not mean it's > > > not successfu

Re: Wave and Incubation

> > because retirement is not successful​ this time does not mean it's > > not successful another time. If Wave can build up a community, it > > can always come back to incubation. > > > > However my feeling says, you need to make access easier to Wave. This >

Re: Wave and Incubation

one that release already > (or most likely). > > I agree, that protocols may have a good place at Apache. But just > because retirement is not successful​ this time does not mean it's > not successful another time. If Wave can build up a community, it > can always come back to

Re: Wave and Incubation

have done that release already (or most likely). I agree, that protocols may have a good place at Apache. But just because retirement is not successful​ this time does not mean it's not successful another time. If Wave can build up a community, it can always come back to incubation. However

Re: Wave and Incubation

ut just because retirement is not successful​ this time does not mean it's not successful another time. If Wave can build up a community, it can always come back to incubation. However my feeling says, you need to make access easier to Wave. This means also the full power of pull requests,

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 coll

Re: Wave and Incubation

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

Re: Wave and Incubation

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 b

Re: Wave and Incubation

"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

Re: Wave and Incubation

All, Just because Wave would be potentially retired as an apache incubator project, does not mean that it is any more or less viable as an open source project. It just means that the project is not right for the apache software foundation. The code could be, will be, moved to a github reposit

Re: Wave and Incubation

I've been interested on Wave since almost one year, first as Kune contributor and lately in a separated project trying to reuse Wave technology in general way. I agree, the issue is the lack of separation between server and client and other components, the handicap to develop on top of Wave unless

Re: Wave and Incubation

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 s

Re: Wave and Incubation

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 disjoi

Re: Wave and Incubation

Guys, I'm a newbie too and we are thinking of building an entire app over wave. It sounds really bat that the community is willing to give up. On 3/15/2015 3:14 AM, ujadatron wrote: It sounds bad. I'm a "few days newbee" in this mailing list. (I'm looking for a flexible open source collaborat

Re: Wave and Incubation

It sounds bad. I'm a "few days newbee" in this mailing list. (I'm looking for a flexible open source collaboration framework). Do you suggest any of them? (if the Wave will retire) thanks in advance adatron 2015.03.14. 22:28 keltezéssel, James Keener írta: I was going to write almost exactly

Re: Wave and Incubation

I was going to write almost exactly the same email and decided not to. I found wave and wanted to use it, but it's dependence on the GWT and how intertwined the Client and Server were made it very difficult for me to understand and I moved to share.js because I could more easily comprehend it's inn

Re: Wave and Incubation

I'll just sadly from my little lurker corner repeat what I have been saying for 3 years or so now; I wanted to work on a client, despite trying, I lacked the ability to understand the server side code. There was never a clear separation of client and sever that I feel would have allowed less skill

Re: Wave and Incubation

he's dead jim .. On Mar 14, 2015 9:56 PM, "Upayavira" wrote: > Wave has been incubating for some years now, and, unfortunately, has not > shown a level of growth that, in my opinion, would suggest that it is > likely to reach graduation from the Incubator. > > Unfortunately, I think it is time w

Wave and Incubation

Wave has been incubating for some years now, and, unfortunately, has not shown a level of growth that, in my opinion, would suggest that it is likely to reach graduation from the Incubator. Unfortunately, I think it is time we accept that Wave is unlikely to reach graduation, and should retire. T

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

having to divert potential > > coding time into non-important stuff. I don't know how much time, but > > surely > 0. > > For that, I'd vote in favour of leaving apache. > > > > > > > > All in all, and unless things can be done in a different way

Re: Incubation status

ving apache. > > > > All in all, and unless things can be done in a different way while still > staying at Apache, my opinion is that we would prolly be better off > outside Apache at this point (in the future maybe it'd be better to go > back, but I don't see how thing

Re: Incubation status

be better off outside Apache at this point (in the future maybe it'd be better to go back, but I don't see how things could get worse by leaving Apache now). On 11/28/13 11:02, Christian Grobmeier wrote: I believe it makes sense to discuss if the incubator is the right place. Incubati

Re: Incubation status

is that we would prolly be better off outside Apache at this point (in the future maybe it'd be better to go back, but I don't see how things could get worse by leaving Apache now). On 11/28/13 11:02, Christian Grobmeier wrote: > I believe it makes sense to discuss if the incubat

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

; > Wave a bit more easily then it would be easier to focus, no doubt. But > life > > goes on, and I know that Wave will always go on. If there are team > members > > who feel that I can contribute positively in this transition, feel free > to > > stay in touch. >

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

w that Wave will always go on. If there are team > members > > who feel that I can contribute positively in this transition, feel free > to > > stay in touch. > > > > > > All the best, > > > > John Blossom > > > > email: jblos...@gmail.com &

Re: Incubation status

that Wave will always go on. If there are team members > who feel that I can contribute positively in this transition, feel free to > stay in touch. > > > All the best, > > John Blossom > > email: jblos...@gmail.com > phone: 203.293.8511 > google+: google.com/+JohnB

Re: Incubation status

ks, > > it seems as the first steam with the new people is gone. > > I believe it makes sense to discuss if the incubator is the right place. > Incubation has a specific goal: forming a team which can do releases and > is - in a way - active. > > I see there is little activi

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

t; > > Sad :-| > > > > > > Do you folks believe the incubator can ever be completed as it is now? > >>> If you believe yes, please let me know why or how we can achieve that > >>> goal. > >>> Otherwise my recommendation is to move Wave to GitHu

Re: Incubation status

the last month asking the same questions > >>> about the future of Wave. > >>> > >> > >> Sad :-| > >> > >> > >> Do you folks believe the incubator can ever be completed as it is now? > >>>> If you believe yes, ple

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

th isn't enough. -J On Thu, Nov 28, 2013 at 2:02 AM, Christian Grobmeier wrote: > Hi folks, > > it seems as the first steam with the new people is gone. > > I believe it makes sense to discuss if the incubator is the right place. > Incubation has a specific goal: forming a

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,

  1   2   >