[Vote ended on 2022-02-16 at ~18:30 UTC] Expand collection inclusion checklist and clarify requirements

[Andersson007]

Summary

Proposal

I suggest slightly expanding collection inclusion checklist and clarify requirements. See the PR ansible-collections/overview#196

DO NOT READ THE BELOW: The information below is for tracking progress of the topic and does not relate to the topic's idea

Simplified version of the workflow

Preparation stage

• A Committee person checks the topic's content, asks the author / other persons to provide additional information if needed (adds the waiting label in this case).
• Adds the topic to the Board.

Discussion stage

• If the topic is ready to be discussed, the Committee person:

  • Adds the discussion_topic label.
  • Moves the topic to the In Discussion column on the Board.
  • Opens the discussion by adding a comment asking the Community and the Committee to take part in it.

• No synchronous discussion is needed (there are no blockers, complications, confusion, or impasses).

Voting stage

• Depending on the topic's complexity, 1-2 weeks after the discussion was opened, the Committee person formulates vote options based on the prior discussion and gives participants reasonable amount of time to propose changes to the options (no longer than a week). The person summarizes the options in a comment and also establishes a date when the vote begins if there are no objections about the options / vote date.
• In the vote date, the vote starts with the comment of a Committee person which opens the vote and establishes a date when the vote ends ($CURRENT_DATE + no longer than 21 days; usually it should not exceed 14 days, 21 days should only be used if it is known that a lot of interested persons will likely not have time to vote in a 14 days period).
• The Committee person labels the topic with the active-vote label and moves the topic to the Active Vote column on the Board.
• The Committee person adds [Vote ends on $YYYY-MM-DD] to the beginning of the topic's description.

Voting result stage

• The next day after the last day of the vote, the Committee person:

  • Removes the active-vote label.
  • Add a comment that the vote ended.
  • Changes the beginning of the topic's description to [Vote ended].
  • Counts the votes separating ones made by Community and made by Committee and creates a summary comment containing the result.
  • Asks another Committee person to count the votes and provide the summary.

• At least two Steering Committee members count the votes and summarize the result in comments.

• The vote's result and the final decision are announced via the Bullhorn.

Implementation stage

• the PR is merged:
  • Add the implemented label.
• A Committee person moves the topic to the Resolved column on the Board and closes the topic.

Additional Information

No response

[Andersson007]

• The essence of the proposal is suggestion to merge Expand checklist and clarify requirements ansible-collections/overview#196.
• Please take a look and suggest any changes before 11 Feb 2022.
• If no objections, we'll start the vote (simple with +1 / -1 as available options) on 11 Feb 2022.

[Andersson007]

[Vote will start now and will end on February 16 at 18:30 UTC!]
Please vote here:
+1 if you're fine with the additions introduced by the PR
-1 if you're against the additions.

If you have any suggestion on wording, vote here anyway if you're OK/not OK with their meaning.

Thank you

[Andersson007]

+1

[felixfontein]

+1

[tadeboro]

+1

[markuman]

+1

[ssbarnea]

+1 also visible on review.

[cidrblock]

+1

[jillr]

+1 (and reviewed)

[gundalow]

+1 (and reviewed)

[jillr]

Count (here or reviewed in the PR):
SC: 11 +1, 0 -1

Updated at: 18:28UTC (I had miscounted, thanks anderson007 for pointing out my mistake!)

[briantist]

+1

[acozine]

+1

[jamescassell]

+1

[Andersson007]

Count:
SC: 11 +1, 0 -1

[Andersson007]

Thanks everyone for reviewing and voting on the issue! @jillr thanks for helping with vote count!
The PR has been merged.