Re: NodeJS for Sever-Side Wave Code

Alex, as I said, I'll be merging latest changes (held at a private repo) later. On May 31, 2013, at 11:04 AM, Alexander Harkness wrote: > Your year seems to be off, github thinks you did everything in 2012. > > But good to see progress anyway :) > > On 31 May 2013 09:23, Paulo Pires wrote: >

Re: NodeJS for Sever-Side Wave Code

Your year seems to be off, github thinks you did everything in 2012. But good to see progress anyway :) On 31 May 2013 09:23, Paulo Pires wrote: > Also, protoc must be version 2.4.1. > > On May 31, 2013, at 9:17 AM, Paulo Pires wrote: > > > Hi all, > > > > Right now, I have this https://github

Re: NodeJS for Sever-Side Wave Code

Also, protoc must be version 2.4.1. On May 31, 2013, at 9:17 AM, Paulo Pires wrote: > Hi all, > > Right now, I have this https://github.com/pires/wave > > I'll be merging latest changes during the day, but this is enough for you to > fiddle with. > > Cheers, > PP > > On May 30, 2013, at 5:5

Re: NodeJS for Sever-Side Wave Code

Hi all, Right now, I have this https://github.com/pires/wave I'll be merging latest changes during the day, but this is enough for you to fiddle with. Cheers, PP On May 30, 2013, at 5:51 PM, John Blossom wrote: > PP, > > Great comments, I agree that brilliance without maintainability can be

Re: NodeJS for Sever-Side Wave Code

And git is an option now. Upayavira On Thu, May 30, 2013, at 10:33 PM, Bruno Gonzalez wrote: > (uh, I had not read the other new thread, sorry for my redundant email) > > > On Thu, May 30, 2013 at 11:26 PM, Bruno Gonzalez > wrote: > > > > > > > > > On Thu, May 30, 2013 at 7:41 PM, John Blosso

Re: NodeJS for Sever-Side Wave Code

(uh, I had not read the other new thread, sorry for my redundant email) On Thu, May 30, 2013 at 11:26 PM, Bruno Gonzalez wrote: > > > > On Thu, May 30, 2013 at 7:41 PM, John Blossom wrote: > >> RE the right tool for some of the project communications, I have to say >> it, >> some of these proc

Re: NodeJS for Sever-Side Wave Code

hi Whitney you can unsubscribe by sending an email to wave-dev-unsubscr...@incubator.apache.org Thanks Angus Turner angusisf...@gmail.com On Fri, May 31, 2013 at 7:28 AM, Whitney Zoller wrote: > pls unsubscribe me > > > On Thu, May 30, 2013 at 5:26 PM, Bruno Gonzalez wrote: > > > On Thu, May 3

Re: NodeJS for Sever-Side Wave Code

pls unsubscribe me On Thu, May 30, 2013 at 5:26 PM, Bruno Gonzalez wrote: > On Thu, May 30, 2013 at 7:41 PM, John Blossom wrote: > > > RE the right tool for some of the project communications, I have to say > it, > > some of these processes might work really well in Wave...just sayin'. > > > >

Re: NodeJS for Sever-Side Wave Code

On Thu, May 30, 2013 at 7:41 PM, John Blossom wrote: > RE the right tool for some of the project communications, I have to say it, > some of these processes might work really well in Wave...just sayin'. > About this specific point, if you are suggesting to use wave as a discussion medium, I'm al

Re: NodeJS for Sever-Side Wave Code

Hi Alain, A great way to start would be to look at the wiki here. There are a number of TODOs at the top of most pages and if you could help out with those that'd be great! Thanks Angus Turner angusisf...@gmail.com On Fri, May 31, 2013 at 7:

Re: NodeJS for Sever-Side Wave Code

I'm reading since as per the Mailing Archive Mon, 13 Dec 2010 17:53:19 GMT And I'm still reading and now I realy want to be part of it I'll find a way to fit in believe me. Merci Apache dev-Wave John & all. On Thu, May 30, 2013 at 4:57 PM, Angus Turner wrote: > +1 for maven, happy to provide

Re: NodeJS for Sever-Side Wave Code

+1 for maven, happy to provide feedback on module names etc. Hopefully this helps make the code a little clearer as well... Thanks Angus Turner angusisf...@gmail.com On Fri, May 31, 2013 at 4:17 AM, Pratik Paranjape wrote: > +1 Michael. I think maven will turn out to be a big necessity in long

Re: NodeJS for Sever-Side Wave Code

+1 Michael. I think maven will turn out to be a big necessity in long run. We are going to have many modules eventually, starting on right track can be helpful. Also from marketing standpoint, its fashionable to provide just the artifact list to get going. I am not good with maven goals, but may b

Re: NodeJS for Sever-Side Wave Code

If we have some interests, I would be more than happy to re-engage with PP and get that maven transition done. While it's not a huge step I think it will entice developers. ~Michael On 5/30/13 10:41 AM, "John Blossom" wrote: >Thomas, > >Specific to my objectives RE your skills, I would appreci

Re: NodeJS for Sever-Side Wave Code

Thomas, Specific to my objectives RE your skills, I would appreciate a hand with making a kick-butt video for the Wave pitch. Not now, but at the right time. RE the right tool for some of the project communications, I have to say it, some of these processes might work really well in Wave...just s

Re: NodeJS for Sever-Side Wave Code

Bruno, I think that some of the urgency is that the future is now. While Wave was incubating, we now have robust HTML5 apps, mobile devices dominating the Web, the internet of everything as a reality and not a promise, things like Google Glass offering new modes of conversational experiences and m

Re: NodeJS for Sever-Side Wave Code

PP, On current release, if you're really that close to the goal line, I encourage the community to carry on, and let's hope that others on this list will get excited enough to dig in and help and start to get messy with the pieces a bit in the process. That will help in the long run. Agreed that

Re: NodeJS for Sever-Side Wave Code

On 30 May 2013 19:06, Upayavira wrote: > To quote Stefano Mazzocchi, "good ideas and bad code builds > communities". > > We need to have an inspiring vision for what this project can be. That's > something that has been lacking, IMO. Then we need some code that leads > us there, but doesn't do an

Re: NodeJS for Sever-Side Wave Code

Is there any suggested way to organize volunteers? I know the current method is basically a "todo" list isnt it? which is fine in itself. But possibly having a list of commiters together with notes of their skillset could also help. I can, for example do the following; * client side GWT coding.

Re: NodeJS for Sever-Side Wave Code

To quote Stefano Mazzocchi, "good ideas and bad code builds communities". We need to have an inspiring vision for what this project can be. That's something that has been lacking, IMO. Then we need some code that leads us there, but doesn't do an excellent job at it. That creates the opportunity

Re: NodeJS for Sever-Side Wave Code

PP, Great to hear on Maven Important step for sure. Thanks for sharing. Also true about how complicated the current state of the project is. Should be priority no 1. (I will refrain from asking if node.js is *still* wannabe ;) but yes, I agree not suitable for Wave in current state of affairs)

Re: NodeJS for Sever-Side Wave Code

@jblossom given the scarse resources, I too think that having a proper short/long term plan is essential, in order to try to direct efforts where they're the most needed. We can't force anyone to work on any particular issue, but we can certainly get better at showcasing the places where they're ne

Re: NodeJS for Sever-Side Wave Code

I haven't been actively involved in development of the project, but I have studied it extensively in past, including the code, and I enjoy answering new people coming to wave whenever I can. Having another pressing project in hands close to release, I am yet not able to contribute code wise, but I

Re: NodeJS for Sever-Side Wave Code

PP, Great comments, I agree that brilliance without maintainability can be risky. We need both. Here's hoping that we can set the right BHAGs with the right metrics and messaging that will excite the world as much as we're excited. One step at a time, but I think that we're getting there. Many t

Re: NodeJS for Sever-Side Wave Code

See inline. Cheers, PP On May 30, 2013, at 4:26 PM, Michael MacFadden wrote: > In my humble opinion we need: > > 1) A vision and marketing to attract people. It's hard to attract coders > if they don't know what they are coding. Forget node.js or any other "world-changer-wannabe" framework

Re: NodeJS for Sever-Side Wave Code

In my humble opinion we need: 1) A vision and marketing to attract people. It's hard to attract coders if they don't know what they are coding. 2) We need a road map. 3) We need a design. 4) Then we need coders. Mainly we need coders to help with the release. Potentially finish off the migrati

Re: NodeJS for Sever-Side Wave Code

Interesting remarks so far from everyone, thanks very much, keep them coming. I see others coming in. Here are some thoughts regarding your thoughts: - There seems to be a commitment to get a release out. If that's a near-term objective, then good, let's allow people to have pride in their work a

Re: NodeJS for Sever-Side Wave Code

On Thu, May 30, 2013, at 11:24 AM, Bruno Gonzalez wrote: > On Thu, May 30, 2013 at 11:54 AM, Christian Grobmeier > wrote: > > > On Thu, May 30, 2013 at 9:09 AM, Bruno Gonzalez wrote: > > > I agree, IMO efforts should be directed at getting more man power. Sadly, > > > ideas are mostly useless i

Re: NodeJS for Sever-Side Wave Code

On Thu, May 30, 2013 at 11:54 AM, Christian Grobmeier wrote: > On Thu, May 30, 2013 at 9:09 AM, Bruno Gonzalez wrote: > > I agree, IMO efforts should be directed at getting more man power. Sadly, > > ideas are mostly useless if there's no hands that will transform them > into > > actual code. I d

Re: NodeJS for Sever-Side Wave Code

On Thu, May 30, 2013 at 9:09 AM, Bruno Gonzalez wrote: > I agree, IMO efforts should be directed at getting more man power. Sadly, > ideas are mostly useless if there's no hands that will transform them into > actual code. I don't know... a solid business plan for a kickstarter, some > advertising

Re: NodeJS for Sever-Side Wave Code

Getting a release out is the #1 task here, helping newcomers have something to engage with. Upayavira On Thu, May 30, 2013, at 08:09 AM, Bruno Gonzalez wrote: > I agree, IMO efforts should be directed at getting more man power. Sadly, > ideas are mostly useless if there's no hands that will trans

Re: NodeJS for Sever-Side Wave Code

I agree, IMO efforts should be directed at getting more man power. Sadly, ideas are mostly useless if there's no hands that will transform them into actual code. I don't know... a solid business plan for a kickstarter, some advertising magic that will attract developers to devote their time for fre

Re: NodeJS for Sever-Side Wave Code

Niceness is in the eye of the beholder though - personally I'd much prefer Java then Javascript. ;) Theres nothing "better" about JS for server side stuff, its all just relative to peoples experience. People side with a language they know. If there was the manpower to do it, re-writing waves serve

Re: NodeJS for Sever-Side Wave Code

Nothing about it not being appropriate, everything about having the man power. Right now it's hard enough to maintain the code we've got. I personally would rather wave was written in a 'nice' language like JS or Python, but right now it's not worth the effort. Thanks Angus Turner angusisf...@gma