On Fri, 16 Mar 2001, Morgan Delagrange wrote:

> 1) Costin, Ignacio, etc. are concerned that the
> Commons committers will incorrectly shoot down
> legitimate components.  

No, the concern is that the "commons" will "aprove"
or vote on  decisions made by jakarta projects. 

And the other concern is that the code developed by
jakarta projects in the shared workspace is treated
in the same way as experimental code that 
is not supported by any jakarta entity.


> 2) Craig, David, Gier, etc. believe that we need
> oversight, or subprojects may introduce components
> that don't meet the Commons charter.

I do believe we need oversight - but not commons 
oversight over code aproved and supported by projects.
And the "commons" charter is to provide support 
for projects and facilitate development of common components,
not to supervise the component developed in projects 
 ( it's the PMC who can do that ).



> Let's keep in mind that the core Commons committers
> are _us_ (well, "we" :), and we'll be guiding the
> evolution of this project.  I don't think any of us
> are going to reject a component that we don't
> understand or that is only used by one subproject.  I
> myself would entertain any good contribution, even if
> it was sponsored by _no_ subproject.

Contributions that are not sponsored by a subproject are 
not the subject here. 

"We" can't make decisions for code we don't write or
support - we can vote on components developed by 
commiters in the playground, but if a component is supported
and developed by a jakarta project - "we" have no 
authority or knowledge to judge their decision. The PMC can,
but this is not the PMC.



> Some Commons components may be promoted from the
> sandbox to Commons.  Others, if they display
> sufficient promise and maturity, may be able to bypass
> the sandbox entirely.  And once the component is

That's exactly my point - "promoted from sandbox to
commons" or "bypass the sandbox" or "move them from
sandbox into commons", "beeing accepted into commons"

That's perfect for playground and experimental stuff - 
but for code that is supported and developed by one 
or many top level jakarta projects I don't think moving 
them to commons will be an evolution. 

Costin

Reply via email to