Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Received-SPF: pass (athena.apache.org: domain of rgardler@opendirective.com
 designates 74.125.82.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4EBA2611.7000204@gmail.com>
References: <4EBA2611.7000204@gmail.com>
Date: Wed, 9 Nov 2011 11:47:37 -0800
Message-ID: 
 <CAKQbXgBzVoEgd_z5=UpbEFFnncQ-won=NaaDf-X-CxjcD255zA@mail.gmail.com>
Subject: Re: Apache Governance: PMCs - blog post
From: Ross Gardler <rgardler@opendirective.com>
To: dev@community.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 8 November 2011 23:04, Shane Curcuru <shane.curcuru@gmail.com> wrote:
> I don't see this as replacing the apache.org/dev site, i.e. the official
> "How to be a committer / How to do PMC things" information, rather a more
> approachable way to see why these guidelines are the way they are, and to
> provide links to those more specific procedural documents.
>
> Sound good? =A0Other ideas?
>

This is pretty much the strategy that I outlined in the most recent
board report:

"ComDev website is slowly growing to include very high level
information about how ASF communities work. Rather than duplicating
content held elsewhere on the a.o site we are seeking to provide a
minimum fuss entry point leading towards the appropriate detail heavy
documents." [1]

This has been fairly organic so far with no real forward planning. I
recently restructured the site to provide entry points for each of
newbies, contributors and committers. We are in no way fixed to this,
but if your content fits this model then I'd love to see you adding
your content directly to the site (which is CMS managed). If it
doesn't fit nicely lets think about a better structure.

Ross

[1] http://community.apache.org/comdevboardreports.html


--=20
Ross Gardler (@rgardler)
Programme Leader (Open Development)
OpenDirective http://opendirective.com