The idea by creating a non incubating repo is that the parties interested in the code will take it from the incubating status into a production ready one.
On 2012-08-23, at 12:51 PM, Wayne Beaton wrote:
You can make as many repositories as you'd like in with a project.
Divide the repositories up as much as you'd like (as much as makes
sense for you and the community). Having the functionality in a
separate repository in the incubator will certainly make it much
easier to move to the proper project when the time comes. Separating
different functional/experimental areas into separate Git
repositories makes a lot of sense to me. YMMV.
If somebody wants to use incubating code in production, that's their
choice. The incubation flag is your warning to the community; they
may choose to ignore those warnings.
My outsider opinion is that moving this functionality into a
separate repository is a net win if you can turn the adopters into
On 08/23/2012 07:54 AM, Pascal Rapicault wrote:
There is of course a matter of repo size, but more importantly is
the fact that the code is in an incubation repository where they
want to use it in production.
On 2012-08-23, at 1:47 AM, Ian Bull wrote:
No problem here, but is the issue that
the incubator repository (I assume it's a single repo) is too
large / complex? If so, then moving it to the p2 repo won't
help much (as you said) :-).
Thanks for your interest in p2CUDF. Moving it out
of where it is located should not be too much of an
I will discuss with the others if they prefer
having the code moved into a specific git repo or
merged with the existing p2 repo, and will check
with the foundation if any process needs to be
For the repo structure, given how large the p2
repository is (both in size and number of projects)
I'm in favour of creating a specific repo. Ian, Tom,
any problems with that?
On 2012-08-20, at 4:44 AM, Adrien
For an open-source project named DORM,
we would like to use the library p2cudf
from the incubation repository.
It would be great for this project to
be hosted in its own repository git or svn
so we could easily use it and maybe
contribute to it.
Thanks in advance!
Adrien Lecharpentier Consultant et