Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of brian.leroux@gmail.com
 designates 209.85.161.175 as permitted sender)
MIME-Version: 1.0
Sender: brian.leroux@gmail.com
In-Reply-To: 
 <CAOFYJNZ--G+hoAouYWCra2-BzKLSoa4nKVmOn39fimfE__jqfQ@mail.gmail.com>
References: 
 <CADVgkyNuWsXzrruSe3YZD3YHAQHe1GU1ZE+GMOYvghEqoK=S0w@mail.gmail.com>
	<CB7A8F15.EF6%fil@adobe.com>
	<CADVgkyM7QDCV8YxpTa9LVSp5U+b=zLQkHs0acMCETvWyfDzz8g@mail.gmail.com>
	<CAOFYJNZ--G+hoAouYWCra2-BzKLSoa4nKVmOn39fimfE__jqfQ@mail.gmail.com>
Date: Tue, 13 Mar 2012 15:22:32 -0700
Message-ID: 
 <CADVgkyNiHeRHYECeefb2K4QJps0VhWeD6Z2jc0mqrBU=yS5AdA@mail.gmail.com>
Subject: Re: [REVIEW] Re: Incubator PMC/Board report for Mar 2012
From: Brian LeRoux <b@brian.io>
To: callback-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

> It's taking a bit longer than expected to produce an official Apache
> release of Cordova. What do you feel are (and have been) the biggest
> problems along the way?

Oh just the usual overconfidence and optimism of a software developer! =)

I do find the Apache documentation a little scattered and verbose.


> AFAICT at least the IP review part has been a bit complicated. Do you
> think better documentation of the requirements, more active
> involvement by us mentors, or something else could have helped here?

Our mentors have been super responsive and helpful so I couldn't ask
for more there. Better docs would be the biggest thing in my mind.


> Do you think some of the requirements were too strict and should
> perhaps be challenged? Other feedback on how we could make the process
> smoother?

No, I like the formality of a release. I would not challenge this part
of the Apache practice though I would encourage more cadence be a part
of The Apache Way. Regular releases are absolutely a driver for
adoption and confidence in our committers.


> Another area of some confusion are the packaging and distribution bits
> that especially Steven was looking at. The related ASF documentation
> is arguably a bit fragmented and at times perhaps too verbose.

Yup

> Similarly to the above questions, any ideas on how we could/should
> simplify these things?

Actually, and I have no idea how we can do this, I think Apache could
really use a solid IxD/UX person fulltime rework the docs to the
benefit of all. The information is all there but parsing it is the
tricky part.