operate-first / blueprint

This is the blueprint for the Operate First Initiative
GNU General Public License v3.0
16 stars 16 forks source link

ADR for EULA #76

Closed durandom closed 2 years ago

durandom commented 3 years ago

We need a EULA for accessing the environment

We don't want consumers of the operational data sign a EULA for accessing the data, but the data should be published under an open source license

related PRs #75 #74

billburnseh commented 3 years ago

Will add this to my question to RH legal to see if there are known agreements like this.

billburnseh commented 3 years ago

Current thinking is that an existing AUP (Acceptable Use Policy, like a EULA) should cover data access within the environment, with possible additions specific to data access. Further, there could be a separate data access policy, but that is unclear at this time. Moving data outside the environment to make it. Current doc working the issues is at https://docs.google.com/document/d/1j8pVhN6n-8xuQpoPpsZS4fWnmGuNPxBMsIWUvzxg99o/edit?usp=sharing

billburnseh commented 3 years ago

Still not clear if the existing AUP may need a tweak to note data access within the operate first environment., but may be fine as is. Will get final info when Michael Daitzman returns from vacation.

billburnseh commented 3 years ago

BU's office of tech development contact just back from vacation. Discussions resumed this week on any changes to AUO (EULA) and a data agreement.

billburnseh commented 3 years ago

No updates from BU yet.

billburnseh commented 3 years ago

No update on this, but the larger issue, a Data Usage Agreement (DUA) is on the table and being discussed, including access to telemetry without anonymization.

sesheta commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

billburnseh commented 3 years ago

As of Oct 21, 2021, BU is in discussion with Harvard on language for a modified EULA and plans to share the outcome more widely as soon as possible thereafter.

HumairAK commented 3 years ago

/remove-lifecycle stale

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/operate-first/blueprint/issues/76#issuecomment-1073367896): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.