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 defintion and collection of workload data #87

Closed durandom closed 2 years ago

durandom commented 3 years ago

copied from a mail by @tumido

We're working with various direct and indirect users:

  1. Academic users doing research on the data
  2. Engineers and operators working directly with the platform, deploying their workloads and consuming the data, their applications have their own users, described later as indirect users
  3. Workshop users who are invited to the platform usually by engineers to "try something out", deploying applications or what not
  4. Indirect consumers are users accessing applications deployed on top of the platform or are just presented with the data, not being aware that it originated from this platform.
    • This also includes users consuming our CI, since they can view logs hosted on our platform. These logs are results of CI job runs against their own code, though technically the logs are produced within our platform and hosted there. If anything goes wrong in the CI run, they are usually presented with snippets of what went wrong. Does this also require DUA?
    • Accessing hosted applications that allow users to browse or work on data within and/or outside of the platform.
    • Interfacing with APIs that are indirectly linked (cnamed) to our platforms providing recommendations etc (Project Thoth)
    • Interacting with our chat-ops in Github and Slack which is still an interaction with our platform

we have to define how users can opt-in or -out for the collection of their data. it's similar to the operational data defined in #80

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/87#issuecomment-992743745): >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.