commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilles <gil...@harfang.homelinux.org>
Subject Re: [ALL] how to move a project out of the sandbox?
Date Wed, 04 Jan 2017 00:44:30 GMT
On Wed, 4 Jan 2017 00:40:43 +0100, Emmanuel Bourg wrote:
> IMHO this concept of promoting components from the sandbox to proper
> looks a bit obsolete (any Apache committer has access to our
> repositories now)

I don't see any relationship.

AFAIK, the "sandbox" was a place where developers could "play"
(without "disturbing" the official tree).

This could be deemed being made obsolete by git branches (for
already established components, hence by definition, not in
"sandbox" state...).

> and it just makes the introduction of new components
> more complicated.

It is certainly not what most complicates the introduction
of new components...

>
> We could consider that any unreleased component is in a "sandbox" 
> state,
> and it's first release promotes it automatically out of the sandbox. 
> No
> need to vote just for promoting the component, this is implicit with 
> the
> first release vote.

It is just not what has been answered to Rob (as being the
proper way to proceed).

I agree that in this case, the double vote will be redundant
because [Text] already has its own git repository.
For another would-be component (for example, "SigProc" has been
recently discussed), the vote would be an indication that the PMC
agrees to create a specific git repository.

Alternative would be that any committer is allowed to ask INFRA
to create a git repository. Is it that which you advocate for?

Gilles

>
> Emmanuel Bourg
>
>


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


Mime
View raw message