devconf.us 2022 Boston - Githubissues

open-services-group / scrum

SCRUM issues and user stories

GNU General Public License v3.0

0 stars 2 forks source link

devconf.us 2022 Boston #24

Closed schwesig closed 1 year ago

schwesig commented 2 years ago

[ ] Presentation
[ ] Idea
[ ] Community Usecases
- [ ] jaeger
- [ ] openshift
- [ ] argocd
- [ ] ...
[ ] let's get started, free resource
- [ ] peribolos as a Service Tom - Service // bot
- [ ] Jaeger Sally - Komplexe Demo
- [ ] ODH - Data Science
- wie deployed
- einfach benutzen Thoth
[x] https://github.com/open-services-group/community/issues/236
[ ] Website Community Cloud update
[ ] Website Community Cloud Metrics

schwesig commented 2 years ago

/assign @schwesig

schwesig commented 2 years ago

/triage accepted

schwesig commented 2 years ago

/kind website /kind documentation /users documentation /sig community /priority important-soon /area user /area monitoring /kind metrics /kind news

sesheta commented 2 years ago

@schwesig: The label(s) kind/website, sig/community, area/user, area/monitoring, kind/metrics, kind/news cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/open-services-group/scrum/issues/24#issuecomment-1195174549): >/kind website >/kind documentation >/users documentation >/sig community >/priority important-soon >/area user >/area monitoring >/kind metrics >/kind news 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.

sesheta commented 1 year 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 1 year 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/scrum/issues/24#issuecomment-1455076032): >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.