search

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 data license #77

Closed durandom closed 2 years ago

durandom commented 3 years ago

We want to publish all collected data under an open source license. Decide which one to use.

related issue #76

billburnseh commented 3 years ago

Do we have a list of preferred licenses? I will ping Red Hat legal to get input from that angle.

hpdempsey commented 3 years ago

Do we have a list of preferred licenses? I will ping Red Hat legal to get input from that angle.

GNU GPL was selected for the code, so that's certainly an argument to keep it for simplicity. See https://github.com/operate-first/blueprint/blob/main/docs/adr/0001-use-gpl3-as-license.md @billburnseh

durandom commented 3 years ago

I'm not sure if we can use a code license for data.

These two are more geared towards data:

tumido commented 3 years ago

Valid point.

ODBL seams reasonable as well, it's used by OpenStreetMaps - they also have this neat compatibility table: https://wiki.openstreetmap.org/wiki/Import/ODbL_Compatibility That may give us some ideas... :slightly_smiling_face:

billburnseh commented 3 years ago

Work is progressing on the access to data. BU has a document to summarize which will lead to addressing any AUP or data access agreements that are needed/ Doc is located here: https://docs.google.com/document/d/1j8pVhN6n-8xuQpoPpsZS4fWnmGuNPxBMsIWUvzxg99o/edit?usp=sharing. Note that the initial work is focused on access within the environment and the topic of a fully open repo requires further definition of the data, and mitigation required to scrub inforation that could be used in violation of various data protection laws around PII (Personally Identifyable Information) such as GPDR. Resolution of this aspect is not expected soon.

billburnseh commented 3 years ago

Work continues on this, lead by Orran at BU. His last update on 5/28 "Very positive initial feedback from office of technology development, so now we just need to iron out the contract for the DUA and the notice to users, and then work on each of the specific logs… we want to de-identify."

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

sesheta commented 3 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/77#issuecomment-997216930): >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.