[EPIC] As a service user, I want to have a one stop location to interact with the community and its developers so I can give feedback on the service

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] As a service user, I want to have a one stop location to interact with the community and its developers so I can give feedback on the service #144

Closed Gkrumbach07 closed 2 years ago

Gkrumbach07 commented 2 years ago

Persona / User

Thoth Guidance Service user

User's Story

I want to have a one stop location to interact with the community and its developers

Reason

so I can give feedback on the service

Define Done

[ ] There needs to be a central page that links to all the forms of communication with the community
[ ] There needs to be a way to differentiate between problem issues and feedback issues
[ ] There should be a way to easily see requested and accepted features so duplicate issues are avoided

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

/area user /area community /kind user-story /sig community /kind onboarding

sesheta commented 2 years ago

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

In response to [this](https://github.com/open-services-group/community/issues/144#issuecomment-1197698305): >/area user >/area community >/kind user-story >/sig community >/kind onboarding 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 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/open-services-group/community/issues/144#issuecomment-1257566076): >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.