Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Developer Resources
Higgins-Specific
CVS Branch Structure
- HEAD -- ongoing development
- M0-8 -- created to capture the state of components and deployments at the end M0.8
- M0-8-STS Mike will create this branch
- M0-9 Paul will create this approx mid-July
- M0-8 -- created to capture the state of components and deployments at the end M0.8
IRC channel (#higgins)
We're experimenting with having the following topics (and folks) on the IRC channel every week:
- Monday 11am ET: IdAS Service (and extensions) Jim, Tom, Duane
- Tuesday 11am ET: Token Service, etc. Mike
- Wednesday 11am ET: i-cards, i-card registry, ISS, ISS Client UI, i-card manager Valery, SergeiY, Andy
- Thursday: noon --regular Higgins weekly meeting
- Friday: 10am ET: HBX, RPPS, ISS Maxim, Abhi
Component Owners
Developer Conventions
- Getting Started
- Higgins Development Processes
- Coding-related Conventions
- EMF Generation, Deriving EMF Models
- Nightly_Component_Builds
IP-Related
- List of Higgins Third Party_Dependencies
- Open Higgins Ipzilla items (committers only)
How To
- BuildingAndDeployingH1H3 --tips and tricks for building and deploying both H1 and H3 variants
- Deploy Token Service --tips and tricks for building and deploying the Higgins Token Service
- Instructions for triggering Higgins build process
- Add new component to automated builds
Archives
Previous Face-to-Face
- 06.25.2007_F2F_Agenda agenda and notes for San Francisco F2F
Rough, preliminary, outdated or all three
- Relying Party Security Policy - rough draft
- Idemix and Higgins
- Integrating With Higgins
- Preliminary Use Cases
- OpenXRI Support
- Dependency Template
- testHBXinstall
Eclipse
Committers
IPzilla
- Open Higgins Ipzilla items (committers only)
- Raw IPzilla (committers only)
Legal
- Guide to the Eclipse Legal Documents
- Eclipse Committer Due Diligence Guidelines, feel free to email license@eclipse.org with any IP related licensing or process questions
- 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.
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.