[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [rt-pmc] Re: Request for creation review approval
|
Greetings all. Unfortunately, I believe that we have been caught in that
in-between space that separates the private communication that occurs
when a new project idea is first suggested and the transparent
conversation that occurs once things are well underway. I believe that
all parties are acting in good faith, but due to the lack of transparent
communication, I believe that we're moving in circles.
In December, I responded to Heiko's questions about incubation:
Hi Heiko.
Like every other project that arrives at Eclipse. ScalaModules will
have to start in incubation. There's no need to do any actual releases
while in incubation. We can do a "1.0 release/graduation" review as
soon as you're ready. Chances are it will take a little while for the
IP team to clear all the contributions anyway.
Mature projects cannot benefit from our parallel-IP process. Are there
many third-party dependencies? It may take the IP team a while to
clear them all and you cannot pull a third-party library into your
project without IP clearance. With parallel-IP, incubating projects
can pull in third-party libraries after a cursory review by the IP team.
You can name the "1.0" release whatever you want. i.e. if you want to
follow up your current 1.0.1 release with a "1.1" or a "2.0" at
Eclipse, that'd be fine.
The back story is that ScalaModules has already had a 1.0 release. The
code base is mature and communities of users, adopters, and developers
are already building around it. Frankly, it is a mature project. As I
explained to Heiko, all projects still need to start in incubation,
because they need to learn the Eclipse way of doing things; or--since
Heiko has been around the Eclipse block a few times--give everybody else
a chance to know that his team understands the Eclipse way of doing things.
I agree that the time-frame is tight. But given all that I've said
above, I think that Heiko can pull it off. With help from the PMC and
project mentors, I feel that--assuming the IP due diligence process
progresses without significant delay--we can make this happen.
I don't think that ScalaModules should shoot for inclusion in Helios.
And, I don't think that Heiko necessarily wants that either. That, I
believe, is a miscommunication. Aligning with the schedule of Helios is
very different than actually being on the release train itself. FWIW,
many projects do this. I believe that it was my surprise in seeing the
Helios alignment that started this whole string of communication.
At the time of its release, the proposal document seemed to adequately
indicate all of the above. The schedule proposed in the document does
indicate a "2.0" release in the specified timeframe. In retrospect, the
discussion of how ScalaModules would incubate should have been more
explicit. This is something that I should have caught before I let the
proposal go public.
There is no guarantee of success: that is up to Heiko. There is,
however, precedent for mature code bases coming to Eclipse and
successfully graduating with their first release in a relatively short
time-frame.
Wayne
--
Wayne Beaton, The Eclipse Foundation
http://www.eclipse.org
I'm going to EclipseCon!
http://www.eclipsecon.org
