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 2] I, as a Manager of op1st, want to know the current interaction points, channels, landing and entry pages, so I can figure out the current status, what needs to be continued, what needs to be upgraded or downgraded. #135

Closed schwesig closed 1 year ago

schwesig commented 2 years ago

Persona/ User: Manager of op1st User's Story: I want to know the current interaction points, channels, landing and entry pages Reason: so I can figure out the current status, what needs to be continued, what needs to be upgraded or downgraded

Define Done: A full list, description, quantity and quality of all input, start, contact, communication channels, pages, sites, etc. interested people can get in touch with us (push and pull)

This epic will be solved by:

Additional Info: e.g. MoSCoW

hemajv commented 2 years ago

We attended the Operate First Website WG meeting last week and the following were discussed which will determine how to start working on this issue moving forward:

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/135#issuecomment-1264424115): >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.