Tomorrow's Meeting Agenda: Planning and Grooming issues for the next milestone

[Nikhita]

Hey everyone,

We'll be grooming our project board and issues for the upcoming milestone (May) in tomorrow's meeting! \o/ This also means that we might not have time for any open mic discussions.

SIG Cluster Lifecycle has a nice doc about how they do it -  https://github.com/kubernetes/community/blob/master/sig-cluster-lifecycle/grooming.md. We'll probably try to follow something similar. :)

There is an open issue about how to adapt this for contribex - https://github.com/kubernetes/community/issues/3443. Feel free to add suggestions on how we can improve this process!

We have also created a new milestone called "May" with a due date of 15 May 2019. The team community-milestone-maintainers will be able to add the milestone using the `/milestone May` command. Membership in this team is defined by an entry in an OWNERS file for a contribex subproject. If you are a reviewer/approver who fits this criteria but are not already on the team, please feel free to create a PR to add yourself.

If you are a subproject owner or are actively working with a subproject, please do the following before the meeting:

1. Make sure all issues have a kind, priority and area label.

2. If you are working on an issue, add the `lifecycle/active` label and the milestone using the `/milestone May` command.

3. If you would like to work on an issue/would like to see an issue being worked on for the May milestone, add the milestone using the `/milestone May` command.

During the meeting, we will walk through all issues tagged with the milestone and:

1. Plan and discuss which ones should stay and which ones can be removed from the current milestone.

2. Assign people to work on it or add the `help-wanted` label.

If we run out of issues having the May milestone, we can walk through issues having the `priority/important-soon` label.

A few points to remember:

- If someone is assigned to an issue, this does not mean that member is the only person who can work on an issue, it just means they have said they are interested. If another member wants to work on the issue, simply coordinate with the member who has been assigned and ask if it is ok to work on that issue.

- The milestone date is not meant as a deadline, it just to help us prioritize our work better. If you are not able to work an issue that you've been assigned to, feel free to comment about it. Prioritizing self care is more important than prioritizing issues. :)

Best,

Nikhita

[Nikhita]

I have also created another milestone "Next". This is for tasks that you'd like to target for the near future (June or July) but not for May. To apply this milestone, use the `/milestone Next` command. Note: the command is case sensitive.

After May, we could perhaps just walk through the issues in the "Next" milestone....

We are still trying to figure out the best workflow that's suitable for contribex, so please feel free to add suggestions too! :)

- Nikhita