|
|
| (50 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | __NOTOC__
| + | #REDIRECT [[Higgins]] |
| − | __NOTOC__
| + | |
| − | ==Higgins==
| + | |
| − | ===Conventions===
| + | |
| − | * [[Higgins Conventions]]
| + | |
| − | * [[EMF Generation]], [[Deriving EMF Models]]
| + | |
| − | ===Higgins Component Owner===
| + | |
| − | * [[Higgins Component Owner Checklist]]
| + | |
| − | | + | |
| − | ===Misc===
| + | |
| − | * [[Instructions for triggering Higgins build process]]
| + | |
| − | * [[Tests]]
| + | |
| − | * [http://dev.eclipse.org/mhonarc/lists/higgins-dev/maillist.html higgins-dev list archive]
| + | |
| − | * [[Committer Access To CVS]]
| + | |
| − | * [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.higgins/?cvsroot=Technology_Project Web view of CVS]
| + | |
| − | | + | |
| − | ==Eclipse==
| + | |
| − | ===Coding conventions and guidelines===
| + | |
| − | * [[Development Conventions and Guidelines]]
| + | |
| − | | + | |
| − | ===Eclipse Legal===
| + | |
| − | * [http://www.eclipse.org/legal/guidetolegaldoc.php Guide to the Eclipse Legal Documents]
| + | |
| − | * [http://www.eclipse.org/legal/committerguidelines.php Eclipse Committer Due Diligence Guidelines], feel free to email license@eclipse.org with any IP related licensing or process questions
| + | |
| − | * [http://www.eclipse.org/legal/copyrightandlicensenotice.php Eclipse Legal Copyright standards]
| + | |
| − | | + | |
| − | ====Clarification of IP processes for use of third party libraries====
| + | |
| − | * Any time anyone working on the Higgins project wants to introduce a project dependency, it needs to be brought forward to the Higgins project.
| + | |
| − | * If the decision is made to introduce the dependency and the dependency involves software that is not licensed under the EPL, then a formal IP process needs to be gone though to approve the software binaries for inclusion in the project cvs. Note that this process must be followed even if the software is a common java library used by other Eclipse processes. (If the software has been used by another Eclipse project, the process is much faster.) Eclipse has a system IPzilla for managing this process. If you are anticipating a dependency, you need to bring it forward as soon as possible to allow time for the IP due diligence process to take place. See more about IPzilla below.
| + | |
| − | *Libraries licensed with EPL are the easiest to get permission to use, followed by Apache 2.0. GPL and LGPL licences are not compatible with EPL.
| + | |
| − | | + | |
| − | ===IPzilla===
| + | |
| − | *IPzilla is like bugzilla only for IP requests http://wiki.eclipse.org/index.php/IPzilla. You can access it from your Eclipse committer tools page https://dev.eclipse.org/committers/menu/menu.php
| + | |
| − | | + | |
| − | ===Orbit===
| + | |
| − | *Orbit is a new Eclipse project http://www.eclipse.org/orbit/ designed to be a repository for third party libraries that are approved for use in Eclipse projects. If the incoming libraries are not already bundles then Orbit committers will work to create a bundle that is suitable for use in Eclipse projects. See http://wiki.eclipse.org/index.php/Orbit_Faq for a list or Orbit managed libraries. Orbit managed libaries are the easiest of third party libraries to add to an Eclipse project. Even if a library is listed under Orbit, you still need to go through the IPzilla process before putting it into the Higgins CVS.
| + | |
| − | | + | |
| − | == See Also ==
| + | |
| − | * [http://eclipse.org/higgins Higgins Home]
| + | |
