Jump to: navigation, search

Difference between revisions of "Policies/Uploading and Downloading from Eclipse Software Policy"

(Common Mechanism)
Line 26: Line 26:
  
 
=Auditing and Approval=
 
=Auditing and Approval=
 +
 +
A full description of the nature of all information captured by a call-home service must be publicly accessible.
  
 
Any project implementing a call-home server must get approval from EMO(ED).
 
Any project implementing a call-home server must get approval from EMO(ED).

Revision as of 16:10, 13 August 2013

Warning2.png
This is a work-in-progress; this policy is not in effect.


This policy is concerned with Eclipse Foundation project code "calling home" or otherwise providing data out of user installations to Eclipse Foundation Servers.

Opt-in

Any call home service would have to be opt-in.

The user needs to be able to review the data before it is sent.

Private Information

Any information provided from an end-user installation to an Eclipse Foundation server is subject to the terms of the Eclipse Privacy Policy.

Raw data, which may include non-obvious potentially private information, needs to be transferred securely.

Raw data needs to be stored securely and access to the data needs to be strictly controlled.

Storage

The target for data collected by content distributed from eclipse.org must be an Eclipse Foundation 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.

Dissemination

Cleaned and processed data needs to be publicly accessible.

Auditing and Approval

A full description of the nature of all information captured by a call-home service must be publicly accessible.

Any project implementing a call-home server must get approval from EMO(ED).

Common Mechanism

Having multiple separate projects each with their own call-home mechanism that prompts the user for opt-in makes us look goofy.