[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [technology-pmc] Restructuring Nebula Project
|
What I was trying to say is that even for relatively stable code (such as some of the Nebula components), reaching the 1.0 release will take some time. Even if the code is perfect per Eclipse expectations, there is still community building and build processes to take care of. The "where will you go after Technology" question is more relevant for graduation review rather than project creation.
As I said, I agree that projects should be able to talk about concrete relocation plans as part of the graduation review.
> I wonder if, after a few subprojects reach maturity, it might make sense
> for the entire Nebula project to just move to RT?
Why RT? The interesting question is whether or not it makes sense to have the Nebula project at all if all components are broken out into individual projects. The answer to that question will determine whether the new projects should be sub-projects of Nebula or sub-projects of Technology directly.
Oracle
Konstantin Komissarchik | Consulting Member of Technical Staff
Phone: +1 425 201 1795 | Mobile: +1 206 898 0611
Oracle Eclipse Tooling
411 108th Ave NE, Suite 2100 | Bellevue, WA 98004
-----Original Message-----
From: technology-pmc-bounces@xxxxxxxxxxx [mailto:technology-pmc-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Monday, November 24, 2008 8:17 AM
To: Technology PMC
Subject: Re: [technology-pmc] Restructuring Nebula Project
Ideally, projects should find a more permanent home when they reach a
1.0 release. However, there is precedent to remain longer.
That said, I'd like to start encouraging all projects to have some kind
of long term plan. I'd like them to have some idea where they're going.
FWIW, I like the idea of having the individual Nebula components be
separate projects.
I wonder if, after a few subprojects reach maturity, it might make sense
for the entire Nebula project to just move to RT?
Wayne
Konstantin Komissarchik wrote:
> It's the before or after question. I think a good policy would be to let projects graduate at technology and then ask them to find a permanent home. Perhaps, the "relocation plan" would be a required part of the graduation review.
>
> Oracle
> Konstantin Komissarchik | Consulting Member of Technical Staff
> Phone: +1 425 201 1795 | Mobile: +1 206 898 0611
> Oracle Eclipse Tooling
> 411 108th Ave NE, Suite 2100 | Bellevue, WA 98004
>
>
> -----Original Message-----
> From: technology-pmc-bounces@xxxxxxxxxxx [mailto:technology-pmc-bounces@xxxxxxxxxxx] On Behalf Of Gunnar Wagenknecht
> Sent: Friday, November 21, 2008 11:15 AM
> To: Technology PMC
> Subject: Re: [technology-pmc] Restructuring Nebula Project
>
> Konstantin Komissarchik schrieb:
>
>> Some thought should be given to post-technology home for stable widgets, but unless it is very likely that the code would be merged into an existing project, I don't see any harm with going forward with creating separate projects. Nicely encapsulated mature projects should be easy to move from technology to another top-level project.
>>
>
> Didn't we define a 1.0 release as a suitable milestone for projects to
> leave the technology project? Maybe I just remember incorrectly.
>
> -Gunnar
>
>
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/technology-pmc
