search

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

Refinement and Planning Sessions #117

Closed schwesig closed 2 years ago

schwesig commented 2 years ago

Refinement and Planning Sessions

started in discussion gchat Thoth Station Developer Chat by @goern Mon, Apr 4, 5:20am

we have just a tiny discussion about how we want to drive forward the refinement/planning sessions, and I would like everyone's input on that:

  1. we want to have a workflow that enables SIGs to refine and plan features, these should be in line with our MVP and Open Services Group's OKRs. planned features should work well with the sprint goals noted down on the current release issue
  2. we want to turn the team/community wide refinement and planning sessions into an informational session: everybody should be brought up to speed of whats happening in sigs, what the planning status is and where issues to be debated have surfaced. Debating the issue could be done during the meeting, ... or offline
  3. I'll propose an assignment of repos to SIGS, this seems to be an open issues
  4. assigning issues to sigs (during issue triage) is based on semantics of the issue, and could happen a little but fuzzy. more important: sig leads should quickly review issues and split/reassign them if the issue feels wrong-placed in a sig
schwesig commented 2 years ago

/cc @codificat

goern commented 2 years ago

for Thoth Station we have https://github.com/thoth-station/core/blob/master/docs/TermsAndConditionsForTheScrum.md which guides us what the outcome of a refinement session shall be

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

codificat commented 2 years ago

for Thoth Station we have https://github.com/thoth-station/core/blob/master/docs/TermsAndConditionsForTheScrum.md which guides us what the outcome of a refinement session shall be

Is this enough or is there anything else needed here?

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/117#issuecomment-1236395437): >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.