Great! Thanks to all of you. It would be ideal to host the docs with the code, and I'd be more than happy to help out myself. I'm in the process of implementing a Python desktop client which would work with WiaB, and would greatly appreciate any documentation made available. Having someone outside of the current Wave team would be really helpful too (ie someone from your team, Ian).
Thanks all, Nathanael Abbotts Email: [email protected] Wave: [email protected] Twitter: @natabbotts (http://twitter.com/natabbotts) On Sat, Dec 11, 2010 at 17:19, Hugh Dougherty <[email protected]>wrote: > I'm an editor with some technical skill. I'll help wherever needed. Just > let > me know what I need to do. > > As for where development takes place, I agree with Torben for what my > opinion is worth. While it is ironic to discuss/debate/develop Wave using > yesterday's methods, it may me dangerous to jump head-long into WiaB until > it's ready for prime time. > > -H > > On Sat, Dec 11, 2010 at 12:03 PM, Torben Weis <[email protected]> > wrote: > > > 2010/12/11 Juan Luis Chulilla <[email protected]> > > > > > Excuse me if I say something stupid, but why documentation is not > > > maintained inside a wave? Is it not feasible now to do that in a > > > instance of wave in a box? I mean, Google sites is fine, but using a > > > > > > > Unless we have a stable instance of WiaB with a very stable persistency > > layer it does not make much sense to switch to WiaB with the specs. > > > > The original version of the HTTP federation specs has been developed on > > Google Wave and wave is the right tool for this purpose (except for some > UI > > issues). However, GWave is close to death and WiaB not yet there, so in > the > > meantime we will have to do with SVN/Hg/Git. > > > > > > > set of waves would be great, specially in terms of morale. Think that > > > a lot of users were disappointed after Google's announcement of > > > discontinuation. > > > > > > Besides, Is there any way of know if a piece of documentation is > > > freezed? I mean, if a document still can change, translate it would > > > not be very productive > > > > > > > I can only speak for the HTTP federation spec which I am maintaining. > This > > is definitelty not frozen. The XMPP spec is quite stable for some time > now. > > However, there are plans to factor out things which are common to XMPP > and > > HTTP federation which means the XMPP fed spec might change as well in the > > future. > > > > Greetings > > Torben > > > > > > > > > > Greetings, > > > > > > Juan > > > > > > On Sat, Dec 11, 2010 at 5:36 PM, Torben Weis <[email protected]> > > > wrote: > > > > Currently we are editing and publishing specs on waveprotocol.org. > > > However, > > > > the editor on waveprotocol.org is not well suited for collaboration. > I > > > would > > > > even say it is a pain. > > > > > > > > Some of the specs exist as mark-up text in the repository and there > is > > a > > > > tool to generate HTML from this mark-up. > > > > I will move the HTTP federation specs to this format and commit it to > > the > > > > repository. Then multiple persons can edit the specs and submit their > > > > changes via the normal code review (or provide translations). > > > > > > > > Any work on improving/tanslating specs is highly welcome. > > > > > > > > Greetings > > > > Torben > > > > > > > > 2010/12/11 Juan Luis Chulilla <[email protected]> > > > > > > > >> Congratulations for the initiative. (Apache) Wave is so complex that > a > > > >> proper documentation is mandatory in order to helping new > developers. > > > >> > > > >> I would like to contribute to it if it is possible. I am not a > > > >> developer, but I can conduct QA tasks with it and translate it into > > > >> Spanish. > > > >> > > > >> Best regards, > > > >> > > > >> Juan > > > >> > > > >> On Sat, Dec 11, 2010 at 3:51 PM, Torben Weis <[email protected] > > > > > >> wrote: > > > >> >> > > > >> >> The blog post referenced is from someone on my team. If it help > > > clarify > > > >> >> details I can ask about also posting on Apache when things are > > setup. > > > >> >> > > > >> >> As for the new federation protocol - I'd like to are that too, > but > > > I'm > > > >> not > > > >> >> sure even torbin has finished an implementation yet. > > > >> >> > > > >> > > > > >> > Implementation for WiaB and Lightwave are ongoing. As far as I > know > > > the > > > >> WiaB > > > >> > implementation has no security implemented yet. Hopefully the two > > > >> > implementations will soon be able to discover each other and > > exchange > > > >> some > > > >> > deltas. > > > >> > > > > >> > Greetings > > > >> > Torben > > > >> > > > > >> > > > > >> >> > > > >> >> /Ian > > > >> >> > > > >> >> "Nathanael Abbotts" <[email protected]> wrote: > > > >> >> > > > >> >> >As the project plans to move to a new home at Apache, I feel > quite > > > >> >> strongly > > > >> >> >that it would be a very good idea to draft up some whitepapers > (or > > > >> >> similar) > > > >> >> >clarifying some things that there appears to be quite a bit of > > > >> confusion > > > >> >> >about. > > > >> >> >Good code requires good planning and good documentation, and so > > far, > > > I > > > >> >> >haven't seen much planning or documentation regarding a couple > of > > > very > > > >> >> >important things: > > > >> >> > > > > >> >> > - Operational Transformation > > > >> >> > - OT is one of the fundamental backends of the Wave > > Protocol, > > > but > > > >> >> the > > > >> >> > OT whitepaper is extremely lacking. For example, I got > more > > > >> >> >information on > > > >> >> > the subject from a blog > > > >> >> >post< > > > >> >> > > > >> > > > > > > http://www.codecommit.com/blog/java/understanding-and-applying-operational-transformation > > > >> >> >than > > > >> >> >from the whitepaper. > > > >> >> > - Detail is needed on the following: > > > >> >> > - The algorithms used by the project currently. > > > >> >> > - What still needs to be implemented. > > > >> >> > - Client implementation > > > >> >> > - More detail is needed on exactly what a client that > wants > > to > > > >> make > > > >> >> > use of the client-server protocol should do, e.g. > > > >> >> > - Encryption/Signing > > > >> >> > - Message protocols > > > >> >> > - Federation Protocol > > > >> >> > - Again, not just a 'how it works', but 'how you should do > > it > > > if > > > >> >> > implementing a server in a different language' > > > >> >> > > > > >> >> >I hope to see some of these appearing soon, and would be more > than > > > >> happy > > > >> >> to > > > >> >> >write them myself, if someone would kindly inform me on them. > > > >> >> >-- > > > >> >> >Nathanael Abbotts > > > >> >> > > > > >> >> >Email: [email protected] > > > >> >> >Wave: [email protected] > > > >> >> >Twitter: @natabbotts (http://twitter.com/natabbotts) > > > >> >> > > > > >> >> >-- > > > >> >> >You received this message because you are subscribed to the > Google > > > >> Groups > > > >> >> "Wave Protocol" group. > > > >> >> >To post to this group, send email to > > [email protected] > > > . > > > >> >> >To unsubscribe from this group, send email to > > > >> >> [email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > > > > > > > > > >> <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > > > > > > > > > >> > > > > >> >> . > > > >> >> >For more options, visit this group at > > > >> >> http://groups.google.com/group/wave-protocol?hl=en. > > > >> >> > > > > >> >> > > > >> >> -- > > > >> >> Sent from my Android phone with K-9 Mail. Please excuse my > brevity. > > > >> >> > > > >> >> -- > > > >> >> You received this message because you are subscribed to the > Google > > > >> Groups > > > >> >> "Wave Protocol" group. > > > >> >> To post to this group, send email to > > [email protected]. > > > >> >> To unsubscribe from this group, send email to > > > >> >> [email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > > > > > > > > > >> <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > <wave-protocol%[email protected]<wave-protocol%[email protected]> > <wave-protocol%[email protected]<wave-protocol%[email protected]> > > > > > > > > > > > > >> > > > > >> >> . > > > >> >> For more options, visit this group at > > > >> >> http://groups.google.com/group/wave-protocol?hl=en. > > > >> >> > > > >> >> > > > >> > > > > >> > > > > >> > -- > > > >> > --------------------------- > > > >> > Prof. Torben Weis > > > >> > Universitaet Duisburg-Essen > > > >> > [email protected] > > > >> > > > > >> > > > >> > > > >> > > > >> -- > > > >> > > > >> > > > >> Dr. Juan Luis Chulilla Cano > > > >> Director, Online and Offline, S.L. > > > >> Telf.: 91 1277356 > > > >> 650 461435 > > > >> Calle de la Paz, 8 - 28012 Madrid > > > >> > > > >> www.onlineandoffline.net > > > >> > > > > > > > > > > > > > > > > -- > > > > --------------------------- > > > > Prof. Torben Weis > > > > Universitaet Duisburg-Essen > > > > [email protected] > > > > > > > > > > > > > > > > -- > > > > > > > > > Dr. Juan Luis Chulilla Cano > > > Director, Online and Offline, S.L. > > > Telf.: 91 1277356 > > > 650 461435 > > > Calle de la Paz, 8 - 28012 Madrid > > > > > > www.onlineandoffline.net > > > > > > > > > > > -- > > --------------------------- > > Prof. Torben Weis > > Universitaet Duisburg-Essen > > [email protected] > > >
