Skip to main content
Jump to: navigation, search

Difference between revisions of "Development Resources/Automatic IP Log"

(Contributors)
(Replaced content with "This content has been moved to the [https://www.eclipse.org/projects/handbook/#ip-iplog Eclipse Project Handbook]. <hr/> ''This page is moderated by the EMO'' Category:D...")
 
(70 intermediate revisions by 11 users not shown)
Line 1: Line 1:
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: [http://www.eclipse.org/projects/ip_log.php?projectid=technology.dash IP Log for technology.dash].
+
This content has been moved to the [https://www.eclipse.org/projects/handbook/#ip-iplog Eclipse Project Handbook].
 
+
<hr/>
==Third-Party Code==
+
''This page is moderated by the EMO''
The Third-Party Code section of the IP Log shows the approved Contribution Questionnaires from [https://dev.eclipse.org/ipzilla/ ipzilla]. The CQs listed in this table are those that are:
+
[[Category:Development_Resources]]
* state=approved_all_projects or state=approved_one_project or
+
* RESOLVED/FIXED or CLOSED/FIXED (regardless of state)
+
 
+
====Correcting Errors====
+
* '''Missing CQ.''' If a CQ is missing from this list, check its status, resolution, and state: make sure that they match one of the above cases. If not, contact Eclipse Legal.
+
* '''Extra CQ.''' If a CQ is listed but does not belong to this project, then contact Eclipse Legal to have the ipzilla database corrected.
+
* '''Missing or Incorrect License.''' If a CQ is missing the license information, contact Eclipse Legal to have the correct license information added to the database.
+
 
+
==Exempt Pre-Req Dependencies==
+
If the project has Exempt Pre-Req Dependencies, these will be listed in a separate table. These are also Contribution Questionnaires from ipzilla. These CQs are:
+
* state=exempt_prereq
+
 
+
====Correcting Errors====
+
* '''Missing Pre-Req.''' If an exempt pre-req is missing from this list, first check that to see if there is a CQ for that pre-req. If there is no CQ, submit one (using [http://portal.eclipse.org the portal]). If there is a CQ, check that it's state is "exempt_prereq" - if not, contact Eclipse Legal.
+
 
+
==Pending Contribution Questionnaires==
+
If the project has any pending and not yet approved or rejected Contribution Questionnaires, these are listed in a separate table. These represent potential IP issues and thus must be considered carefully during a Release Review.
+
 
+
====Correcting Errors====
+
* '''Unneeded CQ.''' If the code represented by a pending CQ is no longer needed by the project, use ipzilla to withdraw the CQ.
+
 
+
==Committers==
+
The Committers section of the IP Log uses two information sources to generate the two lists:
+
# The list of all committers who have committed code to any of the source repositories from the [http://dash.eclipse.org/dash/commits/web-app/summary.cgi Commits Explorer]. This is the basis of the "Past and Present" list. The commits explorer list is driven by the project meta data <code>source repository</code> item(s).
+
# 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====
+
* '''Should Be Active'''. If a committer is listed as "Never Active" but should be listed in the active "Past and Present" table, then you should check the project meta data via [http://portal.eclipse.org/ the portal] - there are directories missing from the "source repository" item.
+
* '''Mr Question Mark'''. If a "xxx???" person is listed as a committer, that means that the unix login "xxx" committed code to the source code repository, but there is no record of "xxx" as having been a committer on the project. This is a potential IP cleanliness problem, so contact the EMO to resolve it.
+
* '''Extra Committer'''. If someone is listed as a "Never Active" committer, but you know that they were never even a committer at all, then there is an incorrect record in the Foundation database - contact the EMO. On the other hand, if someone is listed as a "Past and Present" committer, but you know that they were never a committer, then something larger is awry because there are source code check-ins by that person. Use the [http://dash.eclipse.org/dash/commits/web-app/summary.cgi commits explorer] to determine what check-ins they made and contact the EMO if there are any errors.
+
* '''Missing Committer'''. If someone who is/was a committer is missing from both the "Past and Present" and the "Never Active" tables, then something is very wrong with this page generate code - contact the EMO.
+
 
+
==Contributors==
+
The Contributors section of the IP Log uses one information source:
+
# 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 <code>bugzilla</code> item(s).
+
 
+
====Correcting Errors====
+
* '''Error Messages.''' If the tentative IP log shows errors (red error messages) in product name or component name, then the team should check their project meta data via [http://portal.eclipse.org the portal] - the product name and (optional) component names must be an exact match with bugzilla, capitalization and all.
+
* '''Extra Contributor.''' 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.
+
* '''Missing Contributor.''' 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 should 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.
+
 
+
==Choosing the Set of Projects==
+
The simplest case is an IP Log for a single project. However, many project teams work together to create a unified release across a set of project. In this case, the IP Log must also be an aggregated/unified IP Log across the same set of projects. At the bottom left of the IP Log page is a "adjust the set of projects" link. That link leads to [http://www.eclipse.org/projects/ip_log_selector.php the selector page]. Use the checkboxes to select a set of projects and generate a unified IP Log for all of those projects.
+
 
+
==Submitting the IP Log to Eclipse Legal==
+
Single or unified-multi-project, either way the IP Log can be submitted to Eclipse Legal for review using the link at bottom center of the page. This link will take you to the portal using a special url which defines which IP Log you want to send. In the portal, you will find a "[submit] IP log to Eclipse Legal" section in the appropriate project specific portal box. Click that, fill out the reason, and voila, the a frozen copy of the log is sent to Legal.
+

Latest revision as of 16:23, 12 December 2016

This content has been moved to the Eclipse Project Handbook.


This page is moderated by the EMO

Back to the top