RE: [eclipse.org-architecture-council] Eclipse 4.0 (was Eclipse ProjectA

["Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>]

Thanks, Jochen. Communication about this is critical. Unfortunately you
even started this e-mail by calling "e4" the next version of the Eclipse
platform and I'm still stuck that "e4" is the prototype you are
proposing. I'm sure we all have different visions of what the next major
version of Eclipse needs to be and I look forward to participating in
the process that ensures as many of those needs are met as possible.

Doug S.

-----Original Message-----
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf
Of Jochen Krause
Sent: Thursday, March 06, 2008 8:19 PM
To: eclipse.org-architecture-council; eclipse.org-board; Mike Wilson;
Steve Northover
Subject: [eclipse.org-architecture-council] Eclipse 4.0 (was Eclipse
ProjectAnnouncement and Project Review Schedule)

Dear Board and Architecture Council members,

I would like to clarify the situation around "e4", the next version of
the Eclipse platform, as there is a discussion going on about an "e4"
incubator project component.

There has been a presentation to the Eclipse board about moving the
Eclipse platform to a new level for Eclipse 4.0 in December 2007.
Defining the scope of Eclipse 4.0 has also been one of the Eclipse 3.4
plan item.

The platform team has recently requested to create a new component
within the Eclipse incubator project to make their technology
evaluations available to the community. This has been perceived as a
"decision" about the next version of the platform by some readers - and
the wording of the component proposal can easily be interpreted this
way. But this is not at all the intention of this component. The
component is just about sharing code. 

The Eclipse platform and the RAP team have met to see if they could work
together on e4. We saw our meeting as a part of the "pre-proposal-phase"
of a new project. We have planned to join forces and will announce
shortly a proposal for an e4 incubator project, following the Eclipse
guidelines and process. The process has been established to make
projects transparent and help to engage with the community.

And we are serious about it: Everybody is welcome to join, collaborate,
comment or critizise! There is a lot of work to do. We think that we
need to innovate in many areas to retain a leadership position for
Eclipse, and your know how is welcome. EclipseCon will be a great
opportunity to meet and discuss.

It is really good news that some of the processes that many of us
perceive as a burden most of the time have a value. Receiving comments
and concerns about something that is only planned shows that our
processes apply to reality and that the Eclipse community is very vital.

Jochen


-----Original Message-----
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf
Of Schaefer, Doug
Sent: Thursday, March 06, 2008 8:40 PM
To: eclipse.org-planning-council
Cc: eclipse.org-architecture-council
Subject: [eclipse.org-architecture-council] RE: Eclipse
ProjectAnnouncementandProject 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
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-counci
l
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-counci
l

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list, you
must contact emo@xxxxxxxxxxx to request removal.