Life at Eclipse

Musings on the Eclipse Foundation, the community and the ecosystem

Introducing Eclipse Labs

Back in December, I discussed a number of initiatives that the Eclipse Foundation was going to be working on in 2010. The one that attracted the most feedback was “Eclipse Labs”. Well, we are very happy to announce that thanks to Google, this idea has become a reality. Better yet, Google has already released a cool new project “Workspace Mechanic” on Eclipse Labs.

The Eclipse community has a large and vibrant ecosystem of commercial and open source add-ons to the Eclipse platform. In the open source world, there are two options if you want to start an Eclipse oriented project: 1) propose a project with the Eclipse Foundation or 2) start a project on one of the existing forges, ex. Google Code, SourceForge, Codehaus, etc. For some projects, the IP due diligence and development process expected of Eclipse projects is not warranted. However, creating an Eclipse project on a forge makes it difficult to gain visibility in the Eclipse community. Can we find a third option that allows projects to start and prosper without the process of the Foundation but at the same time gain some of the visibility Eclipse projects often get by being at the Foundation?

Last year, we started a discussion with the people running the Project Hosting on Google Code service to see if they would be interested in creating an Eclipse area on Google Code. They had already been thinking along the same lines and were very receptive to the idea. Therefore, I am excited to announce the availability of Eclipse Labs, a third option for Eclipse oriented open source projects.

What is Eclipse Labs?
If you have ever created a project on Google Code you will quickly recognize Eclipse Labs. Eclipse Labs allows you to very quickly create an open source project with access to an issue tracking system, source code repository (Subversion or Mercurial) and a project web site. The default license is EPL but you can change it to the other licenses available on Google Code. Anyone can create a project on Eclipse Labs at any time. (Assuming you agree to the Google Code terms of use and the Eclipse Labs guidelines.) Eclipse Labs projects are encouraged to use the org.eclipselabs namespace, but are not required to do so.

Eclipse Labs project owners will also be encouraged to create tags/labels to describe your project. We have pre-populated a set of Eclipse specific labels that will be displayed on the Eclipse Labs search page. Eclipse Labs will also have an API that allows people to search on these labels. My hope is that Eclipse projects will begin to highlight on their own web site Eclipse Labs projects that are relevant to their own project. For example, Eclipse BIRT could list all the BIRT add-ons created on Eclipse Labs. We also want to populate Eclipse Marketplace with the projects from Eclipse Labs. The API is not yet available but it should be in the next couple of weeks. I think this will present a lot of opportunity for cross pollination for Eclipse Labs projects.

What is Eclipse Labs Not?
Remember, this is a third option. Projects hosted on Eclipse Labs are not official Eclipse projects. Therefore, they can’t be called Eclipse projects, use the org.eclipse namespace or be included in the Release Train or Packages. If an Eclipse project wants to include an Eclipse Labs project they will need to go through the normal IP process. If a project wants any of these benefits they must become an Eclipse Foundation project. The details have been specified in the Eclipse Labs Guidelines.

Moving Forward
Eclipse Labs is open for business now. It is still in a beta form, so please provide your feedback.

Our hope is that Eclipse Labs quickly grows to a larger number of projects than are already hosted at the Eclipse Foundation. We need to make it as easy as possible for someone to open source their awesome Eclipse based technology. Not all projects need to be hosted at the Eclipse Foundation and in fact I am hoping more projects will start at Eclipse Labs and then, if they choose, graduate to the Eclipse Foundation.

Big Thanks to Google
The people at Google have been great during this process. Google has once again shown their commitment and support for the open source community. Obviously without this support Eclipse Labs would not have been possible.

Thanks also goes to Ian Skerrett for driving this from our side!

Advertisements

Written by Mike Milinkovich

May 13, 2010 at 1:42 pm

12 Responses

Subscribe to comments with RSS.

  1. EclipseLabs projects can also be reached via shorter URLs:

    http://eclipselabs.org/p/workspacemechanic

    instead of

    http://code.google.com/a/eclipselabs.org/p/workspacemechanic/

    Denis Roy

    May 13, 2010 at 2:02 pm

  2. This is great news! It is also a great way of junior developers to clone official repos, work on their sandbox and eventually come up with a bugfix, contributing it back to the official repo while having their own projects running. Of course they could do that at GitHub or Google Code, but without the same visibility, so Eclipse Labs turns out to be a good idea. Congratulations.

    Any plans for Git to be included on the repository list?

    Ugo

    May 13, 2010 at 2:32 pm

  3. Git support has been requested here:
    http://code.google.com/p/support/issues/detail?id=2454

    84213

    May 13, 2010 at 3:45 pm

  4. Quite interesting indeed! How is Mylyn support?

    Egon

    May 14, 2010 at 2:43 am

  5. Which benefits will an existing project hosted e.g. at SourceForge (which provides more feature and is more customizable) have if it migrates to Eclipse Labs? The (Eclipse) visibility is given by Eclipse Marketplace, isn’t it? For me Eclipse Labs looks like Google Code with Eclipse branding…
    Is it easier to graduate a project hosted at Eclipse Labs to a real Eclipse project compared to a project not hosted at Eclipse Labs?

    Holger

    May 14, 2010 at 3:28 am

  6. Git-Support is something I think is important for EclipseLabs else I have to learn one more Version Control System now that Eclipse-Projects are going to move to Git and Eclipse will hopefully ship with Git-Support it might make a lot of sense to support it on EclipseLabs

    Tom Schindl

    May 14, 2010 at 4:42 am

  7. @Egon: there are alpha version Mylyn connectors for Google Code: http://wiki.eclipse.org/Mylyn/Extensions#Google_Code
    One doesn’t accept the Eclipse Labs project URLs yet (http://code.google.com/p/googlecode-mylyn-connector/issues/detail?id=71), the other says it only offers read-only access at the moment (http://code.google.com/a/eclipselabs.org/p/projecthosting-connector-for-mylyn/)

    Rolf

    May 14, 2010 at 5:22 am

  8. @Holger – Alex Blewitt’s article on InfoQ does a nice job of summarizing some of the benefits and future directions. Check it out at http://www.infoq.com/news/2010/05/eclipse-labs

    Mike Milinkovich

    May 14, 2010 at 9:01 am

  9. Congratulations It is also nice that Mercurial gets some love in addition to Git. I think both DVCS are great.

    Lars Vogel

    May 19, 2010 at 6:30 pm

  10. Can I create a full P2 update site on a project here?

    benson

    November 28, 2010 at 3:02 pm

  11. @Benson – Yes you can create a p2 update site at Eclipse Labs. Here are two examples:

    http://code.google.com/a/eclipselabs.org/p/industrial-mylyn/
    http://code.google.com/a/eclipselabs.org/p/wascana/

    I hope that helps!

    Mike Milinkovich

    November 29, 2010 at 1:35 pm

  12. Hey! Would you mind if I share your blog with my myspace group?
    There’s a lot of people that I think would really appreciate your content. Please let me know. Many thanks


Comments are closed.

%d bloggers like this: