From firstname.lastname@example.org Tue May 1 09:46:25 2012
I have applied your suggestion and added a note that the URL-path of the
incoming request is matched in the first rewriterule or until a substitution
takes place, and that rules that follow are matched against the substituted
Do give it a read-through and tell me what you think of this new wording.
I have read the responses from = people on both the mailing list, off it,
and via other channels, as = well as made a small non-scientific survey
among the users@ people = that showed a big approval (93%) of adding
highlighting to the = documentation, and it makes me quite happy that
people are = enthusiastic about this project and the proposed changes.
I would = therefor like to propose, that we apply these changes to the = 2.4
branch as well, so the community can benefit from this = highlighting when
visiting /current/. It is my belief that it would = ease the process of
reading example configurations and source code, = enabling users to
quickly get the information they need, without = having to "mentally
highlight" it themselves.
As we have a = certain saying about our mailing lists, I would ask that
people that = are both for and against this speak up on this list, so we
can see if = there is a general consensus for backporting these = changes.
> > = http://httpd.apache.org/docs-project/docsformat.html
> Except that that page is a nightmare to find, and only tells me what > to do after I'm already on step three.
> It might not seem like much hassle to you, but it's enough to blow=
> away my motivation to fix anything.
For whatever it's worth (noting much yet) Humbedooh and I have been = working to improve that page and others in that general vicinity over the l= ast two weeks. Hopefully it's better now and will be even better next w= eek.
I share Andre's concerns, mostly,=A0 I'm sure, due to ignorance = about how this all works. But I'm willing to give it a try. Whats the p= rocedure?--e89a8f234c276a721b04bf16f6de-- From email@example.com Thu May 3 00:41:19 2012 Return-Path:
> Damn. Because this one looks at the bold "Documentation" link that's
> above the fold, clicks there, keeps navigating on for a bit and can't
> find what she wants. I'm glad that you're able to find them, but
> Subprojects isn't a heading that makes me think "oh, yeah, that's how
> I contribute" or even "oh, yeah, documentation", and when clicking on
> "Documentation" has failed, the plain, below-the-fold "Docs" link is
> not where I go.
In the trunk version of this stuff there are links to "help us with the docs" from all over the place. Tomorrow there will be links on the live site. I agree, we make it too hard to find. I'll fix that.--047d7b10cb152bf1a304bf170edd-- From firstname.lastname@example.org Thu May 3 00:46:36 2012 Return-Path:
On 2012 5 2 18:52, "Daniel Gruno" <email@example.com> 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 be=
ing 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 i= s)
> 4) Okay, I wrote something - why doesn't it show? I need to rebuil= d?
> 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,=A0 yeah, I'd like to see what's involved in getting a demo =
going in the cms. Lets do that.
--e89a8ff1ca5c29288104bf172191-- From firstname.lastname@example.org Thu May 3 00:49:46 2012 Return-Path:
<= span style=3D"font-weight:bold;">From: Rich Bowen <rbowen@rcb= owen.com>
To: docs@= httpd.apache.org
Sent: Wednesday, May 2, 2012 8:46 PM
Subject: Re: Proposal to move docs to Apache CMS
=0A<= meta http-equiv=3D"x-dns-prefetch-control" content=3D"off">
=0AOn 2012 5 2 18:52, "Daniel Gruno" <email@example.com> wrote:
=0A> Clean slat= e here, because this is just some free thoughts:
=0A> I am= for moving both the site and the documentation to the CMS system if
=0A= > it indeed works as Tony explained. I'm also in favor of Noirin's
= =0A> suggestion about making how to contribute to documentation clearer<= /div>=0ANot that, as mentioned elsewhere, these changes are in the pro= cess of being made and will be made tomorrow. But if the process is too har= d, all the documentation in the world doesn't help.=0A
=0A> = My train of thoughts as I start from the front page is:
=0A&g= t; 1) Where can I contribute to documentation? I don't see it
=0A> 2)= I'm a newbie, what or who is SVN?
=0A> 3) How do I write a patch or = check out a repo? (I see a LOT of bugs on
=0A> the docs bugzilla wher= e people obviously don't know what a patch is)
=0A> 4) Okay, I wrote = something - why doesn't it show? I need to rebuild?
=0A> 5) What's XS= LT, I just wanted to help with a translation?!
=0A> 6) Will everythin= g blow up when I commit something?
=0A> 7) I can't make Java or Perl = or insert-process-here work!
=0A>Let's talk more tomorr= ow about writing exactly those docs.=0ABut, yeah, I'd like= to see what's involved in getting a demo going in the cms. Lets do that.=0A=0A