Skip to main content
Jump to: navigation, search

Development Resources/Automatic IP Log

< Development Resources
Revision as of 09:21, 15 May 2008 by Codeslave.ca.ibm.com (Talk | contribs) (link to sample IP log)

The Foundation is working on an automatic IP Log (bug 220977) for each project with the goal of reducing the overhead on each project team. This page is currently a placeholder but will eventually contain the documentation about how the automatic IP Log is generated (by the system) and maintained (by the project team) and processed (by Eclipse Legal). To see this log in action (as it evolves), go here: IP Log for technology.dash.

Committers

The Committers section of the IP Log uses two information sources to generate the two lists:

  1. The list of all committers who have committed code to any of the source repositories from the Commits Explorer. This is the basis of the "Past and Present" list. The commits explorer list is driven by the project meta data source repository item(s).
  2. The list of all past and present committers from the Foundation's internal database of committers and projects. Committers here but not in in the "Past and Present" list are put on the "Never Active" list.

Correcting Errors

  • If a person (person X) is listed in the "Never Active" table but X was never a Committer on this project, then the team should notify the EMO that the Foundation database is in error.
  • If person X is listed in the "Never Active" table but should be in the "Past and Present" table, then the team should check their project meta data via the portal - there are probably directories missing from the "source repository" item.
  • If a ??? is listed in the "Past and Present" table, please notify the EMO that the Foundation database is in error, i.e., the commits explorer shows X to have written code but the Foundation database does not show that person as ever having been a committer.

Contributors

The Contributors section of the IP Log uses one information source:

  1. Everyone who has attached a non-obsolete patch to a RESOLVED/FIXED, VERIFIED/FIXED, or CLOSED/FIXED bug in bugzilla. The bugzilla searches are driven by the project meta data bugzilla item(s).

Correcting Errors

  • If the tentative IP log shows errors in product name or component name, then the team should check their project meta data via the portal - the product name and (optional) component names must be an exact match, capitalization and all.
  • If a person (person X) is listed as a Contributor but the team knows that their patch was never used, their patch should be marked obsolete in bugzilla.
  • If person X should be listed as a Contributor but is not, then be sure that person X has attached a patch to a fixed bug. All external code contributions must come through bugzilla patches, so if a code contribution first comes through email, the contribution must also add a patch. Note that person X must add the patch because if person Y adds the patch for person X, then person Y will be listed as the contributor.

Back to the top