WEBSITE, IN GENERAL

I traded some mails with Gavin Baumanis about website design stuff
yesterday.  We had indeed suffered a miscommunication about who was forging
ahead on the plan.  Gavin is hoping to start submitting patches next week on
this.

WIKI USAGE

The general sense I got from some members of the Apache community about
using a Wiki has led me to believe that the barrier to entry for community
contribution is just going to be too high to bother with.  It appears that
we *can* get a Wiki, but contributors would need to be CLA-covered.  And as
with the sentiment around posting our doxygenized docs, I expect that we
would have to somehow advertise the Wiki as "for developer usage only"
(work-in-progress, use-at-your-own-risk, etc).  So, far too restricted to
see meaningful usage as a part of our primary website.  That, plus the fact
that it would be harder to get patches against wiki-ized material, means
that I'm backing off the idea for now.

Maybe we'll start using a dev-only Wiki in the future, though.  (I'd
certainly enjoy seeing the entirety of our notes directory moved to such a
thing.)

<rant>I realize that the ASF needs to dot its I's and cross its T's,
legally, but so far my experience herein has been not so glowingly positive
from a community building perspective.  "No nit left unpicked", or somesuch.
 I'm choosing for now to just trust that this is ultimately beneficial to
everyone -- that perhaps the result of all of this is that the ASF refines
some of its otherwise vague guidelines around such apparently disputable
topics like "releases".</rant>

-- 
C. Michael Pilato <cmpil...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to