RE: [eclipse.org-planning-council] RE:[eclipse.org-membership-at-large] Eclipse Project AnnouncementandProject Review Schedule
Incubator projects are process workaround for parallel-IP work. And
anyway, the real discussion here is about diversity on Eclipse 4.0.
And yes, I'm happy to continue this on planet eclipse.
> -----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,
> a new *component* in the existing Eclipse Incubator project. I admit
> 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
> component in that Incubator project was the fastest way to create a
> for experimental code that we will be demoing at EclipseCon, with
> 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
> 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
> added as a subscriber. For example, could a new mailing list be
> e.g. eclipse-incubator-e4-dev@xxxxxxxxxxx? (I believe we asked for
> part of the component creation process already.)
> Boris Bokowski
> Eclipse Platform UI committer
> IBM Rational Software, Ottawa Lab
> eclipse.org-planning-council mailing list