Again, I am pretty sure that we cannot move components from SF
directly to the sandbox.  Code developed outside of the ASF framework
needs to pass through the incubator.  My understanding is that this
rule is non-negotiable.

The sandbox is not a substitute for the incubator.  It is for
components that are developed *here* within the myfaces community. 
Non-committers will have to submit files, patches to the dev list to
be committed.  This is the way its done on jakarta-commons.  The
standard for committing something to the sandbox will obviously be
less but the development and development discussions need to take
place in house on the dev list.

I would *not* do any serious development in SF and expect that the
components can be part of the sandbox.  Please be patient, we will
have the sandbox shortly and IMO there is no need to go the SF route.

This is my take on the ASF rules.  My personal views differ somewhat
from the rules but the rules are there for a reason.  I'm sure Ted and
other ASF veterans can clarify.

sean
 

On 5/13/05, Jesse Alexander (KBSA 21) <[EMAIL PROTECTED]> wrote:
> If you want a step before that, the jsf-comp-project on sf.net is
> activated.
> 
> There the committer-rights could be given freely to everybody who's
> interested. When a component is ready, it could be promoted to
> the sandbox for refinement, tests and final documentation by an
> approved myfaces-committer. And upon a final vote then promoted
> to the component-toolbox.
> 
> just my 2cents
> Alexander
> 
> -----Original Message-----
> From: Grant Smith [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 11, 2005 8:42 PM
> To: MyFaces Development
> Subject: Sandbox
> 
> I'd like to kick off the whole sandbox debate again. Yes, I'm a sucker
> for punishment..
> 
> If I recall correctly, the consensus was to have a "sandbox subproject"
> for new components. I would like to propose a simpler solution: Why not
> have the sandbox as a subdirectory of the existing project. Then we can
> just specify all "s:" components as sandbox components until they are
> completely accepted by the community. At that time they can become "x:"
> components.
> 
> Would this satisfy the ASF's requirement for "All New Components Must Go
> Through the Incubator" ? Hopefully...
> 
>

Reply via email to