Hi all,

is there any update on this subject?

It is just to confirm that we could use the code at it is in the incubation
repository but the p2cudf comes to a point that it is not really an
incubation project anymore.
Also, the project could have a release deployed on Maven Central to make it
easier to use in other project.

Thanks in advance.

-- Adrien

2012/8/24 Pascal Rapicault <[email protected]>

> 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
> contributors/committers.
>
> Wayne
>
> 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) :-).
>
>  cheers,
> ian
>
> On Wed, Aug 22, 2012 at 3:36 PM, Pascal Rapicault <[email protected]>wrote:
>
> Thanks for your interest in p2CUDF. Moving it out of where it is located
> should not be too much of an issue.
> 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 followed.
> 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?
>
>  Pascal
>
>
>   On 2012-08-20, at 4:44 AM, Adrien Lecharpentier wrote:
>
>   Hello,
>
>  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
>
>  --
>
>         * Adrien Lecharpentier *
> Consultant et Formateur
> Zenika, Paris             Tél: +33 (0)6 28 55 08 51
> Email: [email protected]
>  Skype: adrien.lecharpentier
>
>   _______________________________________________
> p2-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/p2-dev
>
>
>
>
>
>  --
> R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
> http://eclipsesource.com | http://twitter.com/eclipsesource
>
>
>
> _______________________________________________
> p2-dev mailing 
> [email protected]https://dev.eclipse.org/mailman/listinfo/p2-dev
>
>
> --
> Wayne Beaton
> The Eclipse Foundation
> Twitter: @waynebeaton
> Explore Eclipse Projects <http://www.eclipse.org/projects>
>  _______________________________________________
> p2-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/p2-dev
>
>
>
> _______________________________________________
> p2-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/p2-dev
>
>


-- 

*Adrien Lecharpentier*
Consultant et Formateur
Zenika, Paris Tél: +33 (0)6 28 55 08 51
Email: [email protected]
Skype: adrien.lecharpentier
_______________________________________________
p2-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/p2-dev

Reply via email to