[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [technology-pmc] Nexus project
|
> Hmm... so why not just get the ball rolling and start the projects now.
> Would this leave enough time for DTP and WTP to develop and adopt the
> project for Galileo? It seems that the discussion for a permanent home
> of these projects needs a bit more time. Maybe the picture becomes
> clearer once the projects launched successfully and are included in a
> release. Maybe it is Tool, maybe Runtime or maybe something new
> (Nexus?). After all, we have the flatten namespace now and that makes it
> a lot easier to move projects into a different top level project once
> that is proven to be a good option.
That's exactly what I intend to do. Expect two or three proposals very soon. These projects aren't blocked right now on finding the solution for the permanent home problem, but we shouldn't stop talking about that either.
> But making it easier for new micro-projects by providing them a home as
> sub-sub-projects doesn't seem the right solution. Your idea about the
> "Register New Project Wizard" sounds like a better option to make it
> easier for proposing/creating a new project.
Two different aspects of the problem. One is making it easier for projects to get started (the automation, etc). The other is finding a way to house them once they graduate.
> Also, I do feel that there is some overlap with the Technology project.
I think we are in agreement that the startup / incubation function of Nexus would be covered by the Technology Project. The remaining goal of Nexus (a permanent home for frameworks that represent code sharing efforts between Eclipse projects) does not overlap with the Technology project.
