search

open-services-group / community

This repository handles a few common things, it is mainly used by our bots...
GNU General Public License v3.0
8 stars 24 forks source link

[EPIC 5][Xpt] Operate First Value ODH/RHODS/THOTH #184

Closed schwesig closed 1 year ago

schwesig commented 2 years ago

please add anybody you think could contribute here with ideas E.g. converting the mail thread into a JupyterBook seems straight forward, it already has concrete examples and we could link it with dynamic proof points e.g. the JupyterHub profile analysis by @Shreyanand

maybe we can start by identifying what sort of issues/prs we consider contributing to "adding value", and then whether we have existing labels for that also did we ever figure out a way to identify issues outside the org that are linked back to the operate-first org on github?

I think this is something @hemajv

and obviously this is an additional ask, so it would be a user story to be put on one of the scrum boards I guess O2KR2? @schwesig

"Can you provide any stats about my service? Can you give me trends on users, outages, issues, consumption?" https://grafana.operate-first.cloud/d/fuJBFErMz/jupyterhub-user-perspective?orgId=1&var-datasource=moc-smaug&var-log_datasource=app-logs&var-namespace=opf-jupyterhub&var-account=alivaster121&var-account_substring= Is he looking for an even higher level analysis of the service operations data? (maybe trends isn't captured here)

....

schwesig commented 2 years ago

https://docs.google.com/document/d/1L9_G4qPQwUgAd3isqDErioXo7vayDvUhyTWZtVU9Bp8/edit

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 1 year 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 1 year ago

@sesheta: Closing this issue.

In response to [this](https://github.com/open-services-group/community/issues/184#issuecomment-1304500560): >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.