# \[Vote ended on 2025-03-16\] Update involuntarily leaving SC process

**URL:** <https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058>\
**Category:** Project Discussions\
**Tags:** resolved, community-wg\
**Created:** [February 4, 2025, 6:22pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058 "2025-02-04T18:22:14Z")\
**Posts on this page:** 17\
**Page:** 1

<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:** [February 4, 2025, 6:22pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/1 "2025-02-04T18:22:14Z")

</div>

I suggest to update the involuntarily leaving SC process and [allow PMs](https://github.com/ansible/ansible-documentation/pull/2393) in addition to emails.

At the end of the day, the forum is so important for us nowadays when it comes to discussions and votes that it’s an additional reason to remove people from the SC. If they don’t react on on PM here, they probably are not active on the forum at all. Which is a problem in itself 😉

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [February 5, 2025, 12:51am UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/2 "2025-02-05T00:51:09Z")

</div>

I second that, and would go further and prioritize the forum: send PMs before emails.

---

<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:** [February 12, 2025, 7:13pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/3 "2025-02-12T19:13:25Z")

</div>

I’m +1 for also allowing PM. I would suggest to always try an email if there’s no reply by PM after some time, though. Maybe folks expect email notifications of the forum to work and they broke for some reason; getting a direct mail is helpful in that case.

---

<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:** [February 13, 2025, 5:10pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/4 "2025-02-13T17:10:13Z")

</div>

This somehow contradicts my intention to use PM _instead_ of an email. Since so much has moved to the forum, I wanted to simplify the process by staying on this communication platform.

If you think an email should be mandatory, let’s stay with the email-only solution that we already have.

---

<div class="post-metadata">

**Author:** ![markuman](https://avatars.discourse-cdn.com/v4/letter/m/7bcc69/32.png) [@markuman](https://forum.ansible.com/u/markuman)\
**Post date:** [February 13, 2025, 6:37pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/5 "2025-02-13T18:37:31Z")

</div>

Because the SC is important for the community and there was a good reason the user becomes a SC member, there is basically no reason not to try every other contact option also.  
+1 for PM, because the forum is the official communication platform.

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [February 13, 2025, 6:51pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/6 "2025-02-13T18:51:54Z")

</div>

I don’t think that is an “one or the other” situation, so I would try both, but prioritising PM in the forum

---

<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:** [February 14, 2025, 9:30am UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/7 "2025-02-14T09:30:35Z")

</div>

Let’s make PM mandatory, and email optional? I’m personally OK with removing emails too as there’s imo not point to keep optional stuff in those policies that are already quite big

---

<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:** [February 14, 2025, 3:48pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/8 "2025-02-14T15:48:07Z")

</div>

It looks like there are different opinions on this.

As far as I understand, everybody is fine with sending a PM (first). But some people think we should send an email additionally if there’s no response, and others are fine with not sending an email at all.

Should I start a vote on this? Like:

- Send a PM, if there’s no answer additionally send an email before starting the member audit
- Send a PM, if there’s no answer directly start the member audit

> [@Andersson007](#):
>
> Let’s make PM mandatory, and email optional?

I don’t like keeping email as optional. Let’s even keep it as mandatory or drop it.

---

<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:** [February 14, 2025, 9:48pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/9 "2025-02-14T21:48:13Z")

</div>

I’m for sending both email and PM. I don’t care whether they are sent at the same time, with some days/a week inbetween, or whatever. While the forum / PMs are great, putting everything on one communication channel is IMO a bad idea. Especially in an important situation like “are you still around?” using more than one channel is quite important IMO, as there might be reasons why one channel might not work well enough.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [February 15, 2025, 9:06am UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/10 "2025-02-15T09:06:09Z")

</div>

Very well put. We should (almost) spam over various communication channels during different weeks.

---

<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:** [February 17, 2025, 4:58pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/11 "2025-02-17T16:58:21Z")

</div>

If you want to keep email as a communication channel, I tend to

1. Send PM
2. Send email as a last resort after a week if there hasn’t been a reaction

instead of sending both at the same time. Which would be what @felixfontein suggested [here](https://github.com/ansible/ansible-documentation/pull/2393#discussion_r1953280783).

This way, we would not only use two communication channels but also give people more time to react.

---

<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:** [February 19, 2025, 7:22pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/12 "2025-02-19T19:22:11Z")

</div>

Ok, so are folks more in favor of sending email and PM at the same time, or a week apart? Please comment so we can decide what to vote on 🙂

---

<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:** [February 20, 2025, 10:05am UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/13 "2025-02-20T10:05:25Z")

</div>

I would prefer at the same time to keep less stuff in mind and not to unnecessary complicate the process

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [February 23, 2025, 10:41pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/14 "2025-02-23T22:41:32Z")

</div>

It seems we should vote on that as well. Drafting the options here:

Not add PM (keep it as-is)  
 Add PM, send at the same time as e-mail  
 Add PM, send before the e-mail  
 Add PM, send after the e-mail  
 Send PM and stop sending e-mail (probably not taking votes but added for completeness)

---

<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:** [March 2, 2025, 3:28pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/15 "2025-03-02T15:28:55Z")

</div>

_Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/15))_

_Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/15))_

---

<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:** [March 11, 2025, 8:39pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/16 "2025-03-11T20:39:58Z")

</div>

[@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) please note that this vote has been open for over one week already. Please don’t forget to vote!

---

<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:** [March 16, 2025, 2:16pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-03-16-update-involuntarily-leaving-sc-process/40058/17 "2025-03-16T14:16:56Z")

</div>

We have quorum, so I’ve closed the vote.

There have been 7 votes from the SC and 2 from the community backing this, and only one vote backing an alternative approach (PM and email at the same time).

The result is to send a PM first and an email in a second attempt if there hasn’t been a reaction on the PM.
