Decide on contents for a package maintenance team "issue template"

[Emuentes]

Some tickets have lingered due to lack of consensus or clarity on the outcome that would justify the closing of the ticket.

In an effort to enable the team to confidently close tickets (or break them down into smaller scope, easier to manage parts) let's create an issue template to help streamline discussion practices.

[Eomm]

It is not clear to me if the issue template is a GitHub issue template that will be shown to the users that will open a new issue or the scope is to write down some shared rules in the contribution.md?

In an effort to enable the team to confidently close tickets

I agree, also for merging PR.

I would list these points

Merging PR:

• at least 4 approval
• no blocking review
• merge after X days of the last approval

Close issue:

• summarize the content and close (open other issues if necessary)

[mhdawson]

In terms of merging a PR, in core we only require 2 approvals and 48 hours. Something longer is probably appropriate here as its not code, but processes, policies etc but I'd say some like:

• at least 2 approvals
• no blocking review
• 7 days from time PR was opened.

[mhdawson]

Discussed in last meeting. This is what we agreed to be:

Least 4 approvals
No blocking review
7 days from time 4th approval was received.

Next step is to PR into README.md

[ghinks]

The rules above we added under PR #279
Now we have the rule in master we can close this in the next meeting.