Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rt-pmc] Vert.x spare/extra projects
Jesse, one github eclipse repo was what was done initially simply because there is/was no good way of managing it (github is great in many ways, but sucks at these kind of things). Over time its just proven to hard for projects that like to have greater community involvement via github to be all bundled under on giant organization.
Thats why we (Red Hat) been pushing hard to try find a solution for it.
If it helps I'm visiting Denis Roy next week in Ottawa and will try bribe him with a beer or similar to move this bug forward to resolution.
/max

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx

On Wed, Jun 8, 2016 at 3:13 PM, Julien Viet <julien@xxxxxxxxxxxxxx> wrote:
no,

this has been agreed and there is a current work in progress for its implementation.

Vert.x shall be the first project to use it, but it should be made available to other projects using it I guess.

On Jun 8, 2016, at 10:00 PM, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:

I thought the idea of eclipse-* organizations had been squashed and everything had to be under github.com/eclipse/* ?



--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx

On Wed, Jun 8, 2016 at 2:50 PM, Julien Viet <julien@xxxxxxxxxxxxxx> wrote:
Hi,

in the current Vert.x stack we do have several components that are not released with the whole stack.

There are various reasons for this:

1/ a project that depends on something not ready, that something can be
- another open source bits that are not yet available when the release is done, the project would be released later
- the project does not have a maintainer, i.e the maintainer becomes inactive or not responsive
has not been upgraded to the latest standard by lack of time or contributor - that could be a project of the stack, parked there for a while until somebody contributes to it back

2/ an incubated project that is not yet ready

3/ a project that has not really sense to be released - like a GitHub repo that contains examples

in all case I’m qualifying these of “extra” / “spare”, I don’t know which qualifier is the best but both describe more or less that.

For the stack projects, we are going to have a dedicated eclipse-vertx organization, however for these other projects I would like to know if having another GitHub organization like eclipse-vertx-extra makes more sense or if we should have everything in the eclipse-vertx organization.

cheers

Julien

_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc

_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc


_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc

_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
/max

Back to the top