[Product Goal] [O1KR3] - Build a community around Thoth Guidance Service and drive adoption

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

[Product Goal] [O1KR3] - Build a community around Thoth Guidance Service and drive adoption #129

Closed Gkrumbach07 closed 1 year ago

Gkrumbach07 commented 2 years ago

Continuously maintain a service reporting/information/status overview, and host related user group meetings, to funnel feedback into the services and its operation.

Create a community engagement dashboard, so that

we have a clear documentation for users where to get support, where to read the documentation, documents could provide how the processes of interacting with the community work
feedback is documented and turned into an actionable item within 3 days by the service team
new feature requests are refined and triaged within the next sprint, and the process of refinement and triaging is documented
any issue opened on the support repository by service users is reacted upon within two days

Host RH-internal sessions, to grow our community to also have RH PM participation from relevant products (RHODS, SCL, RHEL), create ‘fancy roadmap microsite’ (this is not only features, but also community engagement activities)

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

schwesig commented 2 years ago

/sig community /area community /kind onboarding /area contributor

sesheta commented 2 years ago

@schwesig: The label(s) sig/community, area/community, kind/onboarding, area/contributor cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/open-services-group/community/issues/129#issuecomment-1197701824): >/sig community >/area community >/kind onboarding >/area contributor 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 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/129#issuecomment-1257566087): >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.