# New guidelines proposal: clarify guidelines about team representatives

**URL:** <https://forum.ansible.com/t/new-guidelines-proposal-clarify-guidelines-about-team-representatives/8094>\
**Category:** Project Discussions\
**Tags:** resolved, community-wg\
**Created:** [August 26, 2024, 3:29pm UTC](https://forum.ansible.com/t/new-guidelines-proposal-clarify-guidelines-about-team-representatives/8094 "2024-08-26T15:29:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [August 26, 2024, 3:29pm UTC](https://forum.ansible.com/t/new-guidelines-proposal-clarify-guidelines-about-team-representatives/8094/1 "2024-08-26T15:29:12Z")

</div>

See [steering\_committee\_membership: clarify guidelines about team represen… by gotmax23 · Pull Request #1806 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/1806).

> Based on general discussions we’ve been having over the past year about inactive steering committee members, I figured we should clarify the team representative section that we recently added (for Core and potentially other teams in the future).

Please discuss here and leave any textual suggestions in the PR.

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [August 27, 2024, 9:18am UTC](https://forum.ansible.com/t/new-guidelines-proposal-clarify-guidelines-about-team-representatives/8094/2 "2024-08-27T09:18:26Z")

</div>

@gotmax23 LGTM and imo no vote is needed there as the PR doesn’t actually change the policy. We don’t vote on adding clarifications, so can be merged w/o a vote after a couple of days I believe if approved

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [August 27, 2024, 2:57pm UTC](https://forum.ansible.com/t/new-guidelines-proposal-clarify-guidelines-about-team-representatives/8094/3 "2024-08-27T14:57:07Z")

</div>

I tend to agree with @Andersson007 that we don’t need a vote on this since it’s only a clarification, no policy change.

Nevertheless, I’ve added the community-wg-nextmtg tag. Let’s have a quick discussion on this tomorrow. But I think (hope) nobody will object.

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [August 28, 2024, 6:38pm UTC](https://forum.ansible.com/t/new-guidelines-proposal-clarify-guidelines-about-team-representatives/8094/4 "2024-08-28T18:38:43Z")

</div>

Also sound good w/o a vote. As stated, this is really a clarification, not something new.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 28, 2024, 7:36pm UTC](https://forum.ansible.com/t/new-guidelines-proposal-clarify-guidelines-about-team-representatives/8094/5 "2024-08-28T19:36:03Z")

</div>

We talked about this at today’s community meeting, and decided that this should be OK without a vote. Please approve the PR if you agree, or object here if you don’t. If nobody objected in a few days, we’ll just merge it.

---

<div class="post-metadata">

**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\
**Post date:** [August 29, 2024, 7:39am UTC](https://forum.ansible.com/t/new-guidelines-proposal-clarify-guidelines-about-team-representatives/8094/6 "2024-08-29T07:39:36Z")

</div>

Merged it as it looks uncontroversial, thanks everyone!
