Eclipse Labs FAQ

Date: May 13, 2010

  1. What is Eclipse Labs?

    Eclipse Labs is a community of open source projects that build technology based on the Eclipse platform. It provides the infrastructure services typically required by open source projects, such as code repositories, bug tracking, project web sites/wiki. Eclipse Labs is hosted by Google Code Project Hosting, so it will be very familiar to developers already using Google Code Project Hosting.

  2. I have a technical questions about Eclipse Labs. How do I get support?

    Please contact the normal Google Code Project Hosting support channels. Help is available at code.google.com/p/support/

  3. What are the rules of hosting a project on Eclipse Labs?

    All projects hosted on Eclipse Labs agreed to the standard Google Code Project Hosting terms of use and the Eclipse Labs User Guidelines.

  4. Are projects on Eclipse Labs official Eclipse projects?

    No, Eclipse Labs projects are not official Eclipse Foundation projects. Eclipse Labs projects are not hosted by the Eclipse Foundation and do not have to follow the Eclipse Foundation development and intellectual property policies.

    There are a number of things Eclipse Labs projects can not do since they are not official Eclipse Foundation projects, including 1) include the word Eclipse in their name, 2) use the org.eclipse namespace for their bundles names, or 3) participate in the annual Eclipse release trains, unless they are included in an official Eclipse project.

  5. When should I consider using Eclipse Labs vs starting a project at the Eclipse Foundation?

    There are a number of benefits and obligations for hosting a project at the Eclipse Foundation. The benefits for your project include:

    • more exposure with the Eclipse community through the eclipse.org web site, newsgroupgs, Eclipse conferences, etc. This may make it easy for you to build a community of users and contributors.
    • official recognition as an Eclipse project, so you can use the org.eclipse namespace and use Eclipse in your project name. This strong association with the Eclipse brand maybe important to some organizations and individuals.
    • potential to be included in the annual Eclipse release train. As a result, the project can be included in any of the packages that are visible on the eclipse.org download page. This will expand the distribution and potential user community for your project.
    • participating in the Eclipse IP due diligence process, an important check for some downstream consumers of open source technology.

    The obligations for being an Eclipse Foundation project may increase the effort and decrease the flexibility of starting an open source project. Eclipse Labs has been established for projects that don't want to come under the process and rules of the Eclipse Foundation but still want to be part of the greater Eclipse community. We would recommend projects starting on Eclipse Labs if one or more of the factors pretain to your project:

    • the project is experimental and the committers are not sure of the future direction.
    • the project is very new with a limited community.
    • the committers are new to open source with not a lot of experience leading an open source project.
    • the project is targeted at a small niche and might not benefit from the wider exposure of being an Eclipse Foundation project.

  6. Is it possible for an Eclipse Labs project to become an Eclipse Foundation project?

    Yes. In fact we hope some projects will start at Eclipse Labs, build a community and technology, then eventually migrate to the Eclipse Foundation. If you believe at one time you will want to move your project to the Eclipse Foundation we suggest you ensure that 1) you keep track of all contributions and ensure they are contributed under the EPL. 2) do not include or link to any code that is licensed under the GPL. Unfortunately, that license is incompatible with the EPL. You should also be aware that there are important restrictions on the use and distribution of LGPL code by Eclipse projects.

  7. I have an existing project on Google Code, can I migrate it to Eclipse Labs?

    If you have an existing project on Google Code that you would like to migrate to Eclipse Labs, file an issue here. Once an issue is filed, you will be contacted within the next 48 hours with instructions for how to migrate your project.

  8. How can I identify where my P2 repository is located?

    We are asking all projects on Eclipse Labs to identify the location of their P2 repository , so in the future it will be possible to create a composite repository for all Eclispe Labs projects. To identify the location of your P2 repo, go to the Admin tab and click on the 'Project Summary' sub-tab in your project. In the 'Project Summary' sub-tab, add a Link under the Link heading. Set the Link text to 'p2repo' and the link url to the url for the p2 repository . Save your changes.

  9. Why is the open source license selection restricted to EPL or Apache 2.0, MIT License, Mozilla Public License or New BSD.

    Projects hosted at Eclipse Labs are expected to be Eclipse plugins or built with Eclipse technology. Therefore, the open source license you choose must be compatible with the Eclipse Public Licenese (EPL). These licenses are the compatible licenses available at Google Code Project Hosting.