Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Policies/Uploading and Downloading from Eclipse Software Policy"
(→Storage) |
(→Common Mechanism) |
||
| Line 31: | Line 31: | ||
=Common Mechanism= | =Common Mechanism= | ||
| − | + | Having multiple separate projects each with their own call-home mechanism that prompts the user for opt-in makes us look goofy. | |
Revision as of 16:07, 13 August 2013
This policy is concerned with Eclipse Foundation project code "calling home" or otherwise providing data out of user installations to Eclipse Foundation Servers.
Contents
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
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.