I've started putting up the new documentation under Wave In A Box. https://sites.google.com/a/waveprotocol.org/wave-protocol/wave-in-a-box
<https://sites.google.com/a/waveprotocol.org/wave-protocol/wave-in-a-box>A big thanks to Mark Kovacevich and Anthony Watkins for bringing the Windows stuff up to date by the way. James On Sat, Oct 30, 2010 at 11:48 AM, James Purser <[email protected]>wrote: > Actually if someone could do a quick and nasty "run wiab as a service under > linux" script that would be great. > > James > > > On Sat, Oct 30, 2010 at 3:26 AM, Matt Richards <[email protected]>wrote: > >> Sounds great, please let me know if there is anything I can do to help >> this along. >> >> >> On Fri, Oct 29, 2010 at 9:01 AM, Soren Lassen <[email protected]> wrote: >> >>> Sounds great. Go for it. >>> >>> Soren >>> >>> On Fri, Oct 29, 2010 at 11:15 PM, James Purser <[email protected]> >>> wrote: >>> > Okay having sparked off a bit of a discussion regarding the User Admin >>> > stuff, here's something more mundane. >>> > The other task I've set myself before the Summit is to re-organise the >>> > documentation that currently exists on the waveprotocol site, generally >>> to >>> > bring it up to date and clean it up a bit. Currently the instructions >>> for >>> > the setting up the server are carried under the Code page and are a bit >>> > haphazard. What I would like to do is replace the Code page with a Wave >>> In A >>> > Box page. This would explain what the WIAB project is in relation to >>> the >>> > wider Wave ecosystem, as well as present a Table Of Contents. Something >>> like >>> > below: >>> > >>> > Setting Up (Filling the requirements for building and running WIAB) >>> > Building Wave In A Box >>> > Running Wave In A Box >>> > >>> > Server (both in the foreground and as a service) >>> > Console >>> > Web Client >>> > >>> > Federation >>> > >>> > Certificates >>> > Ports and DNS >>> > Tested and True XMPP Servers >>> > >>> > How To Contribute >>> > >>> > Code >>> > >>> > Process for submitting new code >>> > Styleguide (if any) >>> > >>> > License (this is something that needs to get sorted at the summit I >>> think) >>> > Design and Testing (we want to give non super techs a way to contribute >>> as >>> > well) >>> > >>> > So that's my idea, let me know what you think and I can get started on >>> the >>> > first four top headings ASAP. >>> > James >>> > >>> > -- >>> > 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]> >>> . >>> > For more options, visit this group at >>> > http://groups.google.com/group/wave-protocol?hl=en. >>> > >>> >>> -- >>> 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]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/wave-protocol?hl=en. >>> >>> >> >> >> -- >> --Matt >> >> -- >> 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]> >> . >> For more options, visit this group at >> http://groups.google.com/group/wave-protocol?hl=en. >> > > -- 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]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
