Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@httpd.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <4FA1BA92.40002@cord.dk>
References: <201204242006.24835@news.perlig.de>
	<201205022340.22467@news.perlig.de>
	<CAKDPwQZXr=rdx-razBCEOLLVSe3xrv03xjQOH=L+6zSQzDSD-w@mail.gmail.com>
	<201205030007.04364@news.perlig.de>
	<CAKDPwQZgWM64LPKr1W3s8iJdJ4pCbCD4Oeb_BUSWg13XcbGtQQ@mail.gmail.com>
	<4FA1B51F.3060206@cord.dk>
	<4FA1BA92.40002@cord.dk>
Date: Wed, 2 May 2012 20:46:08 -0400
Message-ID: 
 <CAD6VretCzBfyRCODe6TO+-MedjMA4U1g_nQ=nhJLsKPWuhYSMw@mail.gmail.com>
Subject: Re: Proposal to move docs to Apache CMS
From: Rich Bowen <rbowen@rcbowen.com>
To: docs@httpd.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff1ca5c29288104bf172191

--e89a8ff1ca5c29288104bf172191
Content-Type: text/plain; charset=ISO-8859-1

On 2012 5 2 18:52, "Daniel Gruno" <rumble@cord.dk> wrote:
>
> Clean slate here, because this is just some free thoughts:
>
> I am for moving both the site and the documentation to the CMS system if
> it indeed works as Tony explained. I'm also in favor of Noirin's
> suggestion about making how to contribute to documentation clearer

Not that, as mentioned elsewhere, these changes are in the process of being
made and will be made tomorrow. But if the process is too hard, all the
documentation in the world doesn't help.
>
> My train of thoughts as I start from the front page is:
>
> 1) Where can I contribute to documentation? I don't see it
> 2) I'm a newbie, what or who is SVN?
> 3) How do I write a patch or check out a repo? (I see a LOT of bugs on
> the docs bugzilla where people obviously don't know what a patch is)
> 4) Okay, I wrote something - why doesn't it show? I need to rebuild?
> 5) What's XSLT, I just wanted to help with a translation?!
> 6) Will everything blow up when I commit something?
> 7) I can't make Java or Perl or insert-process-here work!
>

Let's talk more tomorrow about writing exactly those docs.

But,  yeah, I'd like to see what's involved in getting a demo going in the
cms. Lets do that.

--e89a8ff1ca5c29288104bf172191
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p><br>
On 2012 5 2 18:52, &quot;Daniel Gruno&quot; &lt;<a href=3D"mailto:rumble@co=
rd.dk">rumble@cord.dk</a>&gt; wrote:<br>
&gt;<br>
&gt; Clean slate here, because this is just some free thoughts:<br>
&gt;<br>
&gt; I am for moving both the site and the documentation to the CMS system =
if<br>
&gt; it indeed works as Tony explained. I&#39;m also in favor of Noirin&#39=
;s<br>
&gt; suggestion about making how to contribute to documentation clearer</p>
<p>Not that, as mentioned elsewhere, these changes are in the process of be=
ing made and will be made tomorrow. But if the process is too hard, all the=
 documentation in the world doesn&#39;t help. <br>
&gt;<br>
&gt; My train of thoughts as I start from the front page is:<br>
&gt;<br>
&gt; 1) Where can I contribute to documentation? I don&#39;t see it<br>
&gt; 2) I&#39;m a newbie, what or who is SVN?<br>
&gt; 3) How do I write a patch or check out a repo? (I see a LOT of bugs on=
<br>
&gt; the docs bugzilla where people obviously don&#39;t know what a patch i=
s)<br>
&gt; 4) Okay, I wrote something - why doesn&#39;t it show? I need to rebuil=
d?<br>
&gt; 5) What&#39;s XSLT, I just wanted to help with a translation?!<br>
&gt; 6) Will everything blow up when I commit something?<br>
&gt; 7) I can&#39;t make Java or Perl or insert-process-here work!<br>
&gt;</p>
<p>Let&#39;s talk more tomorrow about writing exactly those docs.</p>
<p>But,=A0 yeah, I&#39;d like to see what&#39;s involved in getting a demo =
going in the cms. Lets do that.<br></p>
<p> </p>

--e89a8ff1ca5c29288104bf172191--