Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Needs SC vote before merging] Steering Committee: team membership #1237

Merged
merged 4 commits into from
Apr 13, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,8 @@ The following table lists the current Steering Committee members. See :ref:`stee
+------------------+---------------+-------------+
| Brian Scholer | briantist | 2022 |
+------------------+---------------+-------------+
| Core Team repr. | See Forum | 2024 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the Community Topic in the forum exists, I think we should have a link to it here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't exist yet but how about just adding a link afterwards w/o a vote? We first need to vote on this PR imo as the core-team representative announcement topic depends on approval of this PR by SC,
If you want to create it now it wouldn't hurt either, so please go ahead and paste the link here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I think I've put this badly. I should have said when the Community Topic in the forum exists.

So vote on this, merge your PR (if the vote is positive) and add the link afterwards.

+------------------+---------------+-------------+
| Dylan Silva | thaumos | 2021 |
+------------------+---------------+-------------+
| Felix Fontein | felixfontein | 2021 |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,6 @@ This document describes the expectations and policies related to membership in t
Expectations of a Steering Committee member
-------------------------------------------


As a Committee member, you agree to:

#. Abide by the :ref:`code_of_conduct` in all your interactions with the Community.
Expand All @@ -42,6 +41,15 @@ A person is eligible to become a Committee member if they have:
#. Active contributions to Ansible and/or related projects in any form described in the :ref:`collections_contributions`.
#. A consent to follow the :ref:`steering_expectations`.

Team membership
^^^^^^^^^^^^^^^

The Committee can accept a team to be a member.
In this case, the team chooses its representative and announces the person in a dedicated `Community Topic <https://forum.ansible.com/tags/c/project/7/community-wg>`_.
felixfontein marked this conversation as resolved.
Show resolved Hide resolved
After the announcement is made, the new representative is added to the `SteeringCommittee <https://forum.ansible.com/g/SteeringCommittee>` group on the forum, and the previous representative is removed from that group.

The team uses the same Community Topic for announcing subsequent representative changes. Representatives should commit to at least two months of membership.

Process
^^^^^^^^

Expand Down