Skip to main content
Jump to: navigation, search

Difference between revisions of "Developer Team Page"

(Backlog)
 
(179 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{#eclipseproject:technology.higgins}}
+
 
 
[[Image:Higgins_logo_76Wx100H.jpg|right]]
 
[[Image:Higgins_logo_76Wx100H.jpg|right]]
Note: '''This page is relevant only for Higgins committers and active contributors.'''
+
This page is information for active committers and contributors.
 
+
===Meetings and Events===
+
* [[Higgins F2F planning]]
+
* [[Higgins Past Meetings and Events]]
+
 
+
=== Version Numbering ===
+
 
+
There are four levels of granularity in the Higgins project:
+
;SVN Projects: are named '''major.minor.service.qualifier''' as described in the "plugins" section here: [[Version Numbering]]. [For java projects every project is indeed a plugin. But for non-java projects a project might be a C++ lib, etc.] For projects (plugins) we are following the rules in [[Version Numbering]].
+
;Features: We only have one feature and we DO follow the rules in [[Version Numbering]].
+
;Components: in Higgins are sets of related projects. But they are just organizing concepts and not digital artifacts. We have not found a need to have version numbers for components. So there is no problem here.
+
;Solutions: in Higgins are complete working apps or web services. There is no equivalent concept in [[Version Numbering]]. We do not use version numbers at the solution level.
+
;Higgins: is the name for the entire project. This is roughly equivalent to numbering of the entire Eclipse IDE (e.g. Eclipse 3.1 or 3.2).
+
* The first bugfix release after 1.0.0 will be 1.0.1 (see [[Beyond Higgins 1.0]])
+
* The first milestone (stable build) after 1.0.0 will be 1.1M1 (see [[Beyond Higgins 1.0]])
+
* We expect to have Higgins 1.1 stable builds approx every 6 weeks or so.
+
 
+
===Backlog===
+
The list of all kinds of things that we might like to do someday is here:
+
* [[Backlog]]
+
 
+
===Processes===
+
* [[Higgins Development Processes]]
+
* Component Owners MUST:
+
*# Create rows (and sometimes entire tables) for each project on the [[Components]] page.
+
*# Manually create (and constantly update) the "dep" wiki page in the "Dependencies" column (entitled "Dep.") for each project/row on the [[Components]] page.
+
*# Edit the autobuild scripts to include java components in the nightly build
+
*# Create a "row" wiki page for each row using the [[Component Description Template]]
+
*# Make sure that automated build scripts are using the latest build.xml
+
*# Make sure that all 3rd party dependent jars are read from the dependencies.redistributable project. For projects that autobuild this can be verified by checking that the auto-generated "Third Party Dependencies" section of the "dependencies" page linked from a build page (see the "downloads" column on the [[Components]] page.
+
 
+
* Solution Owners MUST:
+
*# Add a link to the solution here [[Solutions]]
+
*# Create the solution page using [[Solution Description Template]]
+
*# Put the following string #eclipseproject:technology.higgins preceeded and followed by two sets of { brackets in the top line of all wiki pages they create so that the wiki page will have the Higgins left-hand navigation links.  (If I put the actual full string in here, it messes up the formatting.
+
 
+
===Developing===
+
* All Java code MUST be developed using Eclipse 3.3
+
* [[Higgins Conventions]] for file headers, copyrights
+
* [[Project Structure and Naming]]
+
* Eclipse policy on [[Project Dependencies]]
+
* All Java code must build using JRE 1.4 (and must support both Sun and IBM JREs)
+
* Special plugin we use: [[Higgins2Ant]] -- new page, needs work
+
 
+
===Building===
+
* [[Automated Builds]] --description of the existing nightly build process (see [[Build Enhancements]] for a wishlist of enhancements to the nightly and developer build processes)
+
* [[Starting a Higgins Build]] --how to kick off a build on the eclipse build server
+
* [[Copying necessary 3rd party libs to project lib folder using PERL script]] --steps to copy all necessary 3rd party libs from centralized location (local) to project lib folder
+
 
+
===Deploying===
+
* [[Deployment Requirements]] -- gathering requirements for our build/deploy processes
+
 
+
===Misc Tools===
+
* [[Generating anonymous psf file using PERL script]] --steps to generate anonymous psf file for a project including all it's dependencies
+
 
+
===IP-Related===
+
* List of [[Higgins 1.0 Third Party Dependencies]] --status of each dependency as set by the Eclipse Legal team
+
* List of [[Higgins Third Party Dependencies]] --status of each dependency as set by the Eclipse Legal team
+
* [[Higgins 1.0 IP Log]]
+
* [[Higgins IP log]]
+
* [https://dev.eclipse.org/ipzilla/buglist.cgi?bug_id=&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=technology.higgins&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=component&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=substring&product=technology&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=technology&value-1-1-0=technology.higgins&value0-0-0=&order=bugs.bug_severity&query_based_on=    Open Higgins Ipzilla items] (committers only)
+
* [[Response to Open Specification Promise]] --Higgins and Microsoft CardsSpace
+
* [[Draft Response to Open Specification Promise]] --earlier draft
+
 
+
=== Contributions by team members ===
+
* [[Higgins committers with contributions active in the 1.0 repository]] --Eclipse Legal Review
+
* [[Higgins developers with contributions active in the 1.0 repository]] --Eclipse Legal Review
+
* [[Higgins commiters by component]]
+
 
+
===Eclipse Foundation-related Info ===
+
 
+
Eclipse Committers
+
* [[Development Resources]]
+
** [[Development Conventions and Guidelines]]
+
* Eclipse [[Development Process 2006 Revision Final]]
+
 
+
IPZilla
+
* [https://dev.eclipse.org/ipzilla/buglist.cgi?bug_id=&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&component=technology.higgins&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field-1-0-0=product&field-1-1-0=component&field0-0-0=noop&keywords=&keywords_type=allwords&long_desc=&long_desc_type=substring&product=technology&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type0-0-0=noop&value-1-0-0=technology&value-1-1-0=technology.higgins&value0-0-0=&order=bugs.bug_severity&query_based_on=    Open Higgins Ipzilla items] (committers only)
+
* Raw [https://dev.eclipse.org/ipzilla/ IPzilla] (committers only)
+
 
+
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.
+
  
Orbit
+
== About ==
*Orbit http://www.eclipse.org/orbit/ is 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.
+
This is the Developer Team Page for Higgins 2
  
[[Category:Higgins Developer Info]]
+
== Prior Version ==
 +
See: [[Higgins_1.x_Developer_Page]]

Latest revision as of 12:15, 20 August 2014

Higgins logo 76Wx100H.jpg

This page is information for active committers and contributors.

About

This is the Developer Team Page for Higgins 2

Prior Version

See: Higgins_1.x_Developer_Page

Back to the top