Skip to content
This repository has been archived by the owner on Apr 8, 2024. It is now read-only.

Update Steering committee guidelines #49

Merged
merged 16 commits into from
Mar 21, 2022
Merged
Show file tree
Hide file tree
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions ansible_community_steering_committee.rst
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,38 @@ Depending on a topic you want to discuss with the Community and the Committee, a
* `Ansible Collection Requirements <https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst>`_.
* `Ansible Collection Inclusion Checklist <https://github.com/ansible-collections/overview/blob/main/collection_checklist.md>`_.

Community Topics Workflow
-------------------------

The Committee uses the `Community-topics workflow <https://github.com/ansible-community/community-topics/blob/main/community_topics_workflow.md>`_ to asynchronously discuss and vote on the `community-topics <https://github.com/ansible-community/community-topics/issues>`_.

The quorum, the minimum number of Committee members who must vote on a topic in order for a decision to be officially made, is half of the whole number of the Committee members.

If the quorum number contains a fractional part, it is rounded using standard rules for rounding whole numbers. For example, if there are thirteen members currently in the committee, the quorum will be seven.
Andersson007 marked this conversation as resolved.
Show resolved Hide resolved

In case of equal numbers of votes for and against a topic, the chairperson's vote will be used as a casting vote to resolve the deadlock. For example, if there are six votes for and six votes against a topic, and the chairperson's vote is among those six which are for the topic, the final decision will be positive. If the chairperson has not voted yet, other members ask them to vote.
Andersson007 marked this conversation as resolved.
Show resolved Hide resolved
Andersson007 marked this conversation as resolved.
Show resolved Hide resolved
Andersson007 marked this conversation as resolved.
Show resolved Hide resolved

Collection Inclusion Requests Workflow
--------------------------------------

When reviewing community collection `inclusion requests <https://github.com/ansible-collections/ansible-inclusion/discussions>`_, the Committee members check if a collection adheres to the `Community collection requirements <https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst>`_.

#. A Committee member who conducts the inclusion review copies the `Ansible community collection checklist <https://github.com/ansible-collections/overview/blob/main/collection_checklist.md>`_ into a corresponding `discussion <https://github.com/ansible-collections/ansible-inclusion/discussions>`_.

#. In the course of the review, the Committee member marks items as completed or leaves a comment saying whether the reviewer expects an issue to be addressed or whether it is optional (for example, it could be **MUST FIX:** <what> or **SHOULD FIX:** <what> under an item).

#. For a collection to be included in the Ansible community package, the collection must be reviewed and approved by, at least, two Committee members.

#. After the collection gets two or more Committee member approvals, a Committee member creates a `community topic <https://github.com/ansible-community/community-topics/issues>`_ linked to the corresponding inclusion request. The issue's description says that the collection has been approved by two or more Committee members and establishes a date (a week by default) when the inclusion decision will be considered made. This time period can be used to raise concerns.

#. If no objections are raised up to the established date, the inclusion request is considered successfully resolved. In this case, a Committee member:

#. Declares the decision in the topic and in the inclusion request.
#. Moves the request to the ``Resolved reviews`` category.
#. Adds the collection to the ``ansible.in`` file in a corresponding directory of the `ansible-build-data repository <https://github.com/ansible-community/ansible-build-data>`_.
#. Announces the inclusion through the `Bullhorn newsletter <https://github.com/ansible/community/wiki/News#the-bullhorn>`_.
#. Closes the topic.

Meetings
========

Expand Down
5 changes: 5 additions & 0 deletions steering_committee_membership_guidelines.rst
Original file line number Diff line number Diff line change
Expand Up @@ -132,3 +132,8 @@ The process of the election consist of the following steps:
person responsible for arranging the election about that.
#. Conduct anonymous voting somewhere.
#. Internally and publicly announce the elected candidate.

The chairperson has the following powers unlike regular members:

* The chairperson has a casting vote when vote deadlocks in `community topics <https://github.com/ansible-community/community-topics/issues>`_ happen (equal numbers of votes for and against a topic.
Andersson007 marked this conversation as resolved.
Show resolved Hide resolved
* Has a power of veto - the power to unilaterally reject a decision made by the Committee. In this case, the chairperson must explain their motives in a corresponding `community topic <https://github.com/ansible-community/community-topics/issues>`_.
Andersson007 marked this conversation as resolved.
Show resolved Hide resolved