I'm not sure how any of this works apache/organisation wise, but
someone on my group (arwave.org) could contribute some simple set up
instructions for Ubuntu.
We planned to set up a wiab server for our project anyway - it would
be nice to have a apache sever to federate with too.

On 8 December 2010 19:00, Paul Lindner <[email protected]> wrote:
> Thirded.
>
> I suggest that someone with knowledge of how to get wiab up and running on
> solaris/ubuntu/freebsd create an INFRA ticket with a step-by-step guide on
> what needs to be done.  Then offer to work with the infrastructure to get it
> done.
>
> If you want help structuring the request I highly recommend dropping by
> #asfinfra on freenode.  Nice folks that are happy to help you get stuff
> done.
>
>
> On Wed, Dec 8, 2010 at 8:05 AM, Jeff Larkin <[email protected]> wrote:
>
>> Seconded.  There's a certain irony to developing Wave from a
>> traditional mailing list.  =)
>>
>> On Wed, Dec 8, 2010 at 10:17 AM, Daniel Page <[email protected]>
>> wrote:
>> > Obviously, we need to get an Apache Wave server for the dev list and move
>> the conversations over there!
>> >
>> > Daniel Page
>> > Sent from my Verizon Wireless BlackBerry
>> >
>> > -----Original Message-----
>> > From: Mike Mabey <[email protected]>
>> > Date: Wed, 8 Dec 2010 08:13:06
>> > To: <[email protected]>
>> > Reply-To: [email protected]
>> > Subject: A Comment on Cosmetics
>> >
>> > I don't know how many other people subscribe to the list as a digest, but
>> I
>> > must say that I'm really going to miss the format of the Google Group
>> digest
>> > email, which was very easy to read and easy to pick out discussions of
>> > interest to me.  In stark contrast, the Apache Incubator digest is just a
>> > long, text-only, really long concatenation of emails, that is somewhat
>> > painful to read through.
>> >
>> > Does anyone else feel the same way?  Is there anything that can be done
>> > about it?
>> >
>> > So long, beautiful, colorful digest.  You will be missed!
>> >
>> > Mike M
>> >
>> >
>> >
>>
>
>
>
> --
> Paul Lindner -- [email protected] -- linkedin.com/in/plindner
>

Reply via email to