commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar" <rahul.akol...@gmail.com>
Subject Re: Proposal: Commons SAX
Date Wed, 31 Dec 2008 21:25:34 GMT
On Wed, Dec 31, 2008 at 8:55 AM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> Hi,
>
> Until we come up with consensus on where (Commons, Xerces or Cocoon)
> we should place this proposed library, I'd like to start putting some
> bits together in the Commons Sandbox.
>
> The Commons web page defines the Sandbox as "a place to try out new
> ideas and prepare for inclusion into the Commons portion of the
> project [*] or into another Apache project", which is exactly what I'm
> planning to do.
>
> [*] Is this wording a leftover from Jakarta days?
>
<snip/>

No, thats right. You can start in the Sandbox, consensus would be
needed if you propose addition to Proper (there are no releases out of
the Sandbox, so at some point you'd need to find the code a better
home).

For Commons, we're interested in (this is from the old charter [1],
but it still holds IMO):

  "Each package must have a clearly defined purpose, scope, and API --
Do one thing well, and keep your contracts."

The best place to capture the purpose and scope is probably via a
PROPOSAL document in SVN trunk, so I recommend new components have
one. See recent examples [2, 3].

-Rahul

[1] http://commons.apache.org/oldcharter.html (first FAQ)
[2] http://svn.apache.org/repos/asf/commons/sandbox/monitoring/trunk/PROPOSAL.html
[3] http://svn.apache.org/repos/asf/commons/sandbox/me/trunk/PROPOSAL.html



> BR,
>
> Jukka Zitting
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message