Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: =?iso-8859-1?q?Andr=E9_Malo?= <nd@perlig.de>
Organization: TIMTOWTDI
To: docs@httpd.apache.org
Subject: Re: Proposal to move docs to Apache CMS
Date: Wed, 2 May 2012 23:40:22 +0200
User-Agent: KMail/1.9.10
References: <201204242006.24835@news.perlig.de> <4F9EB17D.30909@cord.dk>
 <CAKDPwQYQhNTDPVKaSCeYC4=psnx=KVsY_8AJq+RELYt8hw=NoQ@mail.gmail.com>
In-Reply-To: 
 <CAKDPwQYQhNTDPVKaSCeYC4=psnx=KVsY_8AJq+RELYt8hw=NoQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <201205022340.22467@news.perlig.de>

* N=F3ir=EDn Plunkett wrote:

> On Mon, Apr 30, 2012 at 8:36 AM, Daniel Gruno <rumble@cord.dk> wrote:
> > Hi all,
> >
> > Joe Schaefer has proposed that we move our documentation to the Apache
> > CMS(?) system (or at least try it out with a copy of trunk). From what
> > I have gathered with my discussion with Joe, this move would allow for
> > certain different ways of managing our documentation:
>
> I, for one, welcome our new CMS overlords :-)
>
> Seriously though, the hassle of checking out the docs tree, finding
> the build tree, remembering where I'm meant to check that out to, ...
> is, well, a hassle.

Well. There's not effort needed for *that* hassle. It's documented on the=20
docs-project pages (since ever). [1] [2]

http://httpd.apache.org/docs-project/docsformat.html

OTOH, remembering where the CMS is and how it works, would actually be a=20
hassle for *me* (and I'd guess, various developers trying to write=20
documentation while writing code, too [which should be encouraged!]).

More thoughts on this (unsorted):

=2D Also it's a nice thing to check in documentation together with code. Fr=
om=20
  time to time patches arrive that way. In fact, I'd rather support more of=
=20
  those.

=2D Oh, patches. How does the CMS deal with those in general? Do I need to=
=20
  apply them manually then in a browser window?

=2D Which leads to the next point: I've never used the CMS. How does it pla=
y=20
  together with my own editor?

=2D How does the CMS play along with the other build targets (CHM, tarball)=
=2E I=20
  guess, it does not at all (CHM needs windows in very specific=20
  configurations). So we still need a separate build system then?

=2D How does the CMS handle the build output? (e.g. ./build.sh de emits the=
=20
  outdated de-translations at the end)

nd

[1] *Sigh* I'm wondering, why so many people here don't know about OUR=20
    docs-project pages.

[2] Not everybody needs to run the build system (some people don't even hav=
e=20
    java on their box). Someone else will run it then at the next=20
    opportunity. In fact, it's encouraged that you run it only on languages=
=20
    you understand enough.

=2D-=20
If God intended people to be naked, they would be born that way.
  -- Oscar Wilde

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org