Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330938

Summary:	Terminate Eclipse Incubator project
Product:	[Eclipse Project] Platform	Reporter:	John Arthorne <john.arthorne>
Component:	PMC	Assignee:	John Arthorne <john.arthorne>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, david_williams, pwebster, remy.suen, tom.schindl, wayne.beaton
Version:	3.7
Target Milestone:	4.4 M6
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:	428679
Bug Blocks:

Description John Arthorne

2010-11-23 11:52:57 EST

As part of our recent reorganization of Eclipse project Unix groups, we noticed the top-level eclipse.incubator project did not have its own committer group. We also noticed that e4 has largely replaced eclipse.incubator as the place where experimental things go. Therefore in a PMC call we decided to phase out eclipse.incubator and centralize all Eclipse platform incubation under eclipse.e4.

However in this discussion we completely missed UFaceKit. Since it uses SVN rather than CVS, we missed it when gathering the list of projects to be updated. Therefore we now need to decide what to do with UFaceKit. Do we keep eclipse.incubator alive just for UFaceKit, or do we move UFaceKit elsewhere?

Tom I would like your input on this. The easiest option is to simply move UFaceKit into eclipse.e4. It would not need to change bundle/package names, or change repository location. The only effect is that all "eclipse.e4" committers would be able to contribute to it. Are you ok with this, or do you prefer keeping UFaceKit as a separate project?

Comment 1 Paul Webster

2010-11-23 12:21:47 EST

I like where we turn it into a git repo in e4 :-)

PW

Comment 2 Thomas Schindl

2010-11-25 01:32:09 EST

I'm fine with move it to e4. We are using some SVN-Specials (svn:external) in our project structure so I'd need some help from git people if this is also possible there but I'm fine moving this to git.

Comment 3 John Arthorne

2010-11-25 08:39:58 EST

(In reply to comment #2)
> I'm fine with move it to e4. We are using some SVN-Specials (svn:external) in
> our project structure so I'd need some help from git people if this is also
> possible there but I'm fine moving this to git.

Moving to git is a completely separate topic. Your bundle/package names are currently org.eclipse.ufacekit, and I think it is fine for them to stay that way. Since e4 is a perpetual incubator, it was generally a mistake that we used org.eclipse.e4.* in our bundles/packages, because it requires another rename when the code graduates. You can stay in SVN or move to Git - in both cases they will be repositories owned by the Eclipse top level project so it makes no difference. Having said that, if you wanted to be included in the e4 build I suspect either git or CVS would be easier.

The only concrete difference is that more committers will have commit rights on UFaceKit, but so far we have never had problems with e4 committers messing with areas they weren't active on.

Comment 4 Thomas Schindl

2010-11-25 09:08:06 EST

Getting part of the build is not needed at the moment - given the fact that my long term build should be made upon maven I don't want someone to invest into that for now.

So I'm fine moving the project under the e4 umbrella.

Comment 5 John Arthorne

2010-11-30 14:33:25 EST

Thanks Tom. I am converting this into a PMC bug to perform project reorganization to combine our incubators.

Comment 6 Paul Webster

2012-11-02 13:11:46 EDT

I've migrated the platform-incubator CVS module into /gitroot/e4/org.eclipse.e4.ui.git

Tom, if you want to move an SVN repo over you'll have to co-ordinate that with the webmasters (if UFaceKit is still in SVN)

PW

Comment 7 John Arthorne

2013-03-12 09:22:20 EDT

The current state is that all code except UFaceKit has been merged into e4 git repositories years ago. All that's left is to formally terminate the old Platform Incubator project and its sub-project UFaceKit.

Comment 8 John Arthorne

2014-03-05 16:25:48 EST

Done. See bug 428679 for details.