[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[eclipse.org-planning-council] RE: Eclipse Project AnnouncementandProject Review Schedule
|
You're right, the planning council list may not be the best place,
certainly all the councils and the board itself need to be interested in
this. For the Arch council members, please check full e-mail thread on
the archives page started by Doug Gaff:
http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/mailli
st.html
Getting back to the "Component" description: "The result was the design
of a new platform "e4", which will be the basis for Eclipse 4.0." By new
platform, did you mean fork? My fear is that this is a likely scenario,
which would make the issues Doug Gaff brought up originally even more
important. If we're going to have two platforms, we'd better have the
processes in place to ensure they get the resourcing necessary to keep
them both alive.
Doug Schaefer.
-----Original Message-----
From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of
Boris Bokowski
Sent: Thursday, March 06, 2008 2:11 PM
To: eclipse.org-planning-council@xxxxxxxxxxx
Subject: [eclipse.org-planning-council]
RE:[eclipse.org-membership-at-large] Eclipse Project
AnnouncementandProject Review Schedule
Whoa. I expected a flamewar on planeteclipse, but not here.
Doug Gaff wrote:
> What is frustrating me about this project proposal
You misread the announcement e-mail. It is not a project proposal,
merely a new *component* in the existing Eclipse Incubator project. I
admit that one can easily be confused with the other.
We realized (admittedly, very late) that nobody from the SWT team had
commit rights in the existing Eclipse Incubator project. Creating a new
component in that Incubator project was the fastest way to create a home
for experimental code that we will be demoing at EclipseCon, with write
access to everybody who has been involved so far - people at IBM,
Innoopract, and Code 9.
The key words are "so far" - our hope is to find more people and
companies who would like to work with us on e4.
Could we continue this discussion in a more open forum? The Planning
Council mailing list is not open to everybody; I had to ask nicely to be
added as a subscriber. For example, could a new mailing list be created,
e.g. eclipse-incubator-e4-dev@xxxxxxxxxxx? (I believe we asked for this
as part of the component creation process already.)
Boris
--
Boris Bokowski
Eclipse Platform UI committer
IBM Rational Software, Ottawa Lab
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council