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 and running on whatever computer they have.. and just run it and play with it , and have them all federated / talking to eachother. Lets all use wave, i know im sounding like a broken record here but its amazing how few people actually go ahead and setup a wave server even ? On Fri, Nov 29, 2013 at 3:05 PM, Ali Lown <a...@lown.me.uk> wrote: > @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, is now about as simple as possible to make Wave > function - given the complexity assosciated with what it can do, and > the variation in set-ups people seem to want. > > 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 > > (Hop on to wave-dev.alown.co.uk and we can discuss this... :p) > > On 29 November 2013 13:41, Jon wright <jon.wright1...@gmail.com> wrote: > >> > >> 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 other. Comprehending that takes time in itself and > > you need to do that before you can actually start contributing in a > > meaningful way. > > > > If I were to tackle wave in the same way I've tackled other projects > > with massive code bases. I would start with a skeleton, basic > > functionality. Then build it up by taking components that have already > > been developed and documenting it as I go connecting it all together. > > > > I know you cant do that with Wave but better documentation on how to > > get the client/server up and running in a consistent way locally, will > > help people, whoever setup the demo servers on the incubator page > > could probably do that. You can expand on it form there. >
