labels for lifecycle management?

AICoE / content-pipeline

Other

3 stars 5 forks source link

labels for lifecycle management? #28

Closed goern closed 2 years ago

goern commented 2 years ago

Shall we create labels for this repo so that we can manage the lifecycle of a talk?

"please-submit" and "help wanted" - for something that needs a speaker, that would be a cool talk to give
"lifecycle/active" - is submitted and we are waiting for feedback

if the issue is closed, it is done, how do we show if it was accepted or if the issue is closed with the talk having been held?

/assign @durandom /assign @isabelizimm /kind question /priority important-soon

isabelizimm commented 2 years ago

Sounds like a good idea! I previously created a new-idea label, which could be used for your first use case.

Using #12 as an example, we closed the issue once the talk was given (adding supporting docs for the talk is a ➕ ). Maybe we want a lifecycle/accepted label to show which talks were accepted?

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 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/AICoE/content-pipeline/issues/28#issuecomment-1087962836): >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.