+1

On Fri, Jan 14, 2011 at 00:09, Michael MacFadden <
michael.macfad...@gmail.com> wrote:

> Alright unless there are objections, I recommend the Apache CMS for "basic
> web content" with a supporting confluence space for developer documentation.
>
> I will coordinate the set up of the confluence space.
>
> ~M
>
>
> On Jan 13, 2011, at 2:47 PM, Alex North wrote:
>
> > On 14 January 2011 09:08, Tad Glines <tad.gli...@gmail.com> wrote:
> >
> >> On Thu, Jan 13, 2011 at 1:55 PM, Michael MacFadden
> >> <michael.macfad...@gmail.com> wrote:
> >>> It seems like we are leaning towards the Apache CMS for several
> reasons:
> >>>
> >>> 1) It is being adopted by the larger apache community.
> >>> 2) The confluence based wiki is being phased out.
> >>> 3) It is better than managing raw HTML.
> >>>
> >>> The only two concerns I have with this system is that is a little
> >> cumbersome to use.  There is a graphical editor but building and
> maintaining
> >> the site is definitely not as easy to do as using the confluence user
> >> interface.  A lot of other projects use a standard maven style web site,
> >> this is another option we have not yet discussed.
> >>
> >> Confluence itself isn't being phased out. What's getting phased out is
> >> the use of Confluence for building the main site. So we can use the
> >> Apache CMS for the main site content (stuff that doesn't change much)
> >> and use Confluence for the more developer centric internal
> >> documentation type stuff.
> >>
> >>
> > My understanding is the same as Tad's, and it sounds good to me. My
> > hope/guess is that the majority of information will in fact be in the
> wiki,
> > perhaps with progressively more becoming static as the project matures.
> >
> > Do we have Confluence space yet? Do we need to file an INFRA request?
> Moving
> > WIAB developer stuff from waveprotocol.org to confluence is something we
> > should be able to start on now in either case. We can leave "protocol"
> stuff
> > behind at least temporarily while we decide where it should live.
> >
> > A.
>
>

Reply via email to