Specific agreements depend on the nature of the project. For committers in an open source software project (i.e. most Eclipse Foundation projects), traditional agreements are required. Additional working group agreements are required for committers of an open source specification project. The Eclipse Foundation provides p2-like deployment software and the Eclipse Update Manager (“Provisioning Technology”) to enable users to install software, documentation, information and/or other hardware (together “installable software”). This feature is provided with the intention of allowing these users to install, expand and update Eclipse-based products. For more information on installable packaging software, see eclipse.org/equinox/p2/repository_packaging.html (“Specifications”). Unless otherwise stated, all content made available by the Eclipse Foundation will be made available to you in accordance with the terms of the public license Eclipse 2.0 (“EPL”). A copy of the EPL is provided with this content and is also available under www.eclipse.org/legal/epl-2.0. For the purposes of the EPL, “program” means content. You can use deployment technology to allow other parties to install installable software. You are responsible for the presentation and acceptance of the corresponding licensing agreements for the software that can be installed to users of the deployment technology in accordance with the specification. By using deployment technology in this way and making it available in accordance with specifications, you confirm your agreement and the acquisition of all necessary rights to enable: The Eclipse Foundation has obtained the authorization of contributors to re-grant their CPL code under the EPL.
 This contract applies to all contributions you submit. If you believe that the content that is or access it on or via this site, or that udS violates a copyright, please send a notice of copyright infringement to our designated agents, in accordance with the procedures described here: www.eclipse.org/legal/copyright.php in which such changes and/or additions of the program come from that specific contributor and are distributed by that specific contributor. A contribution “comes” from a contributor if it has been added to the program by such a contributor himself or by someone acting on behalf of such a contributor.