Difference between revisions of "Policies/Uploading and Downloading from Eclipse Software Policy"
|Line 2:||Line 2:|
This policy is concerned with Eclipse Foundation project code "calling home" or otherwise
This policy is concerned with Eclipse Foundation project code "calling home" or otherwise Eclipse Foundation .
This policy applies for
This policy applies for that:
* for updates;
* a heartbeat;
* usage statistics;
* data from a user's workstation; or
* otherwise information from user installations.
Revision as of 13:51, 18 October 2013
This policy is concerned with Eclipse Foundation project code "calling home" or otherwise connecting from software distributed by the Eclipse Foundation to remote services.
This policy applies for software that:
- checks for updates;
- provides a heartbeat;
- gathers usage statistics;
- gathers data from a user's workstation; or
- otherwise collects information from user installations.
Any service that sends data to an Eclipse Foundation server must be "opt-in". That is, a user must agree to participate (agreement may be implicit due to the nature of the operation)
If the nature of the data being collected changes, the user must be informed of the changes and be given the opportunity to explicitly agree to continue participation.
The user must be able to review any data included with the call home before it is sent to any Eclipse Foundation Server.
Services that get/pull data only do not require "opt-in". The server components for these services must not attempt to persist any information related to a get/pull data service (Eclipse Foundation-managed server logs, with access restricted to Eclipse Foundation staff only, are exempted from this requirement).
Raw data, which may include non-obvious potentially private information, must be transferred securely.
Raw data must be stored securely and access to the data needs to be strictly controlled. To access the raw data, an individual must be a committer, and sign a non-disclosure agreement (NDA) with The Eclipse Foundation.
Obvious means of identifying a specific individual or organization (e.g. IP address) must not be persisted.
Reasonable effort must be taken to avoid persisting or disseminating information that can inadvertently be used to identify an individual or organization.
The target for data collected by content distributed from an Eclipse Foundation-managed server must also be an Eclipse Foundation-managed server (e.g. the Eclipse packages must be configured to send data to an eclipse.org server). This can be configurable by adopters to send to an alternate server.
Aggregate data needs to be publicly accessible.
The retention policy for publicly accessible data must be documented.
Auditing and Approval
Documentation, including a full description of the nature of all information captured by a call-home service, must be publicly accessible.
The implementation of a call-home service must be reviewed and approved by the implementing project's Project Management Committee (PMC).
Any project implementing a call-home service must get approval from EMO(ED).
Reasonable effort must be undertaken to leverage existing "call home" mechanisms rather than create new ones.