# \[Vote ended on 2023-12-05\] Stop using the gh.com/ansible/community meeting agenda for the Community WG meeting **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg\ **Created:** [November 8, 2023, 8:37pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243 "2023-11-08T20:37:57Z")\ **Posts on this page:** 17\ **Page:** 1
**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:** [November 8, 2023, 8:37pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/1 "2023-11-08T20:37:57Z")
So far we posted the meeting notes from the weekly Community WG to [https://github.com/ansible/community/issues/679](https://github.com/ansible/community/issues/679) (a new issue is created every year). Since we’re using the Matrix meeting bot, the meeting notes are automatically posted to this forum (such as [Meeting Log | Ansible Community Working Group | 2023-11-08 19:00:58](http://forum.ansible.com/t/meeting-log-ansible-community-working-group-2023-11-08-1958/2242) from today), and we basically copy’n’paste them over to the GitHub issue. At the meeting we talked about stopping to do that copying over, and just keep the meeting notes in this forum. What do you all think about that? The meeting notes should be tagged so it is easy to get a list of all meeting notes for the Community WG (you can find a list of _all_ meeting notes here: [MeetingBot Logs - Ansible](http://forum.ansible.com/c/workflow/meetbot/16)). Which tags should we use for that? Let’s discuss this here and use this as a first topic to vote on! (See [[vote ended on 2023-11-08] Move votes and discussions to the Ansible forum · ansible-community/community-topics · Discussion #279 · GitHub](https://github.com/ansible-community/community-topics/discussions/279) - we’re voting in the forum for now!) * * * **Use [http://forum.ansible.com/t/vote-ends-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/13](http://forum.ansible.com/t/vote-ends-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/13) to vote! The vote ends on 2023-12-05.** ---
**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:** [November 8, 2023, 9:21pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/2 "2023-11-08T21:21:44Z")
For comparison, the Documentation working group stopped using the issues entirely, closed it, and put a point here to the relevent places in the forum. I go in after each meeting and tag the meeting log with `documentation` and `meeting`. …so I’m +1 for using the forum for it all 🙂 As an aside, since I’ll be migrating ansible/community soon, this is a good opportunity to move things over here to the forum where applicable. ---
**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:** [November 8, 2023, 9:39pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/3 "2023-11-08T21:39:04Z")
I’m currently wondering whether using the `community-wg` tag for the meeting log posts is a good idea. 👍 everyone listening to the `community-wg` tag (SC members should listen to them) also gets informed on the meeting logs, and at the same time: 👎 everyone listening to the `community-wg` tag also gets informed on the meeting logs since this spams everyone listening for Community WG topics. I’m still tending to use the same tag, since the meeting logs are also relevant for folks interested in the Community WG. ---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [November 9, 2023, 1:14am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/4 "2023-11-09T01:14:12Z")
A couple of ideas (although it might need testing): The meeting log lives in the #MeetingBot Logs category, which should give better control on the notifications, as the category has an independent notification setting. If the #community-wg tag notification has higher priority (didn’t test this, so I’m assuming) and the “muted” setting of the category doesn’t trigger, we could also add an additional tag (#meeting-log for ex.) to those topics, so that tag could be “muted”. This raises another “priority fight”, as we probably need to verify the behaviour of a combination of a watched (#community-wg) and muted (#meeting-log) tag in the same topic. I did a quick Discourse search and couldn’t find the answer to what’s the priority, and [it seems Matthew from Fedora was having the same issue/question](https://meta.discourse.org/t/what-is-the-exact-priority-interaction-between-tag-and-category-notification-settings/213210). We could do some testing though to verify the behaviour and see if any of the options above work. Update: By the way, looks like the “notification” options for a category+tag [is not on the roadmap](https://meta.discourse.org/t/doesnt-work-subscribe-for-topics-in-the-category-with-a-specific-tag/177944/9) (or wasn’t in 2021) ---
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [November 9, 2023, 9:22am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/5 "2023-11-09T09:22:03Z")
> [@samccann](#): > > …and tag the meeting log with `documentation` and `meeting`. For the record, it’s planned to figure out a way for the bot to know what tags to apply in advance, I just haven’t had time 😉 > [@Leo](#): > > I did a quick Discourse search and couldn’t find the answer to what’s the priority, and [it seems Matthew from Fedora was having the same issue/question](https://meta.discourse.org/t/what-is-the-exact-priority-interaction-between-tag-and-category-notification-settings/213210). That’s the interaction between a **category** and a tag, not two tags. The end result is that you can now control that interaction - if you watch a tag and mute a category (and by default you’ll have #Workflows & Logs muted I think) then a checkbox appears in your tracking prefs to control which should win. The interaction of a muted tag a and watched tag is still unclear to me however. Matthew, myself, and CDCK people have been discussing it (and other filtering things) for a while and plan a public topic when we have a moment to write it all up. ---
**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:** [November 9, 2023, 3:56pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/6 "2023-11-09T15:56:52Z")
This sounds like a really good idea to me. At the spur of the moment, I would suggest to (re-) use the #community-wg tag. This way, you will get everything related to the Community WG under this tag, be it discussions, votes, meeting logs or whatever. Of course, this should be tagged automatically. But as @gwmngilfen said, people are already working on this. ---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [November 9, 2023, 4:57pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/7 "2023-11-09T16:57:29Z")
> [@gwmngilfen](#): > > That’s the interaction between a **category** and a tag, not two tags. The end result is that you can now control that interaction - if you watch a tag and mute a category (and by default you’ll have #Workflows & Logs muted I think) then a checkbox appears in your tracking prefs to control which should win. Yeah, I was actually doing a reference to the cat+tag of my second paragraph, I didn’t find anything around tag+tag at that time. If the checkbox exists, I think that would solve the main issue by @felixfontein: > [@felixfontein](#): > > 👎 everyone listening to the `community-wg` tag also gets informed on the meeting logs As only those who unmute or tick the checkbox would get the notifications. ---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [November 9, 2023, 5:44pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/8 "2023-11-09T17:44:03Z")
> [@gwmngilfen](#): > > For the record, it’s planned to figure out a way for the bot to know what tags to apply in advance, I just haven’t had time 😉 We could use the auto-tag of Discourse if we put a “unique enough phrase” in the meeting logs post for it to trigger the rule. (I already setup a few simple ones for some tags and it seems to be working nicely). ---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [November 16, 2023, 2:35pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/9 "2023-11-16T14:35:08Z")
> [@Leo](#): > > We could use the auto-tag of Discourse if we put a “unique enough phrase” in the meeting logs post for it to trigger the rule. Following up from yesterday’s #community-wg meeting, I have added the auto-tag to Discourse for the meeting logs with the following rule: `Meeting Log | Ansible Community Working Group` \> #community-wg Tested it with a topic and it worked _without_ double quotes (") only. Using the “case sensitive” option as a fail safe just in case. If anyone sees a false positive being tagged please let us know (flag the topic or comment here). ---
**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:** [November 24, 2023, 9:23pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/10 "2023-11-24T21:23:49Z")
I’ve explicitly tagged all old meeting notes with `community-wg` this morning. ---
**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:** [November 24, 2023, 9:29pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/11 "2023-11-24T21:29:40Z")
Proposal for a vote: 1. The community WG meeting notes are posted in the “Meeting Logs” category in the forum with tag `community-wg`. 2. Until end of December 2023, they are also posted in [GitHub - ansible/community: This repository is for management of all Ansible community related initiatives.](http://github.com/ansible/community/), more precisely to [https://github.com/ansible/community/issues/679](https://github.com/ansible/community/issues/679). If this is OK for everyone, let’s start a vote for this soon, say beginning of next week. (After all, the [trial period for votes in the forum ends on December 12th!](https://github.com/ansible-community/community-topics/discussions/279#discussion-5777385)) ---
**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:** [November 25, 2023, 11:51am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/12 "2023-11-25T11:51:04Z")
+1 for your proposal and on starting a vote beginning of next week. ---
**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:** [November 27, 2023, 7:50pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/13 "2023-11-27T19:50:37Z")
Vote (ending **December 5th** ) on the following proposal: 1. The community WG meeting notes are posted in the “Meeting Logs” category in the forum with tag `community-wg`. 2. Until end of December 2023, they are also posted in [GitHub - ansible/community: This repository is for management of all Ansible community related initiatives.](http://github.com/ansible/community/), more precisely to [Community Working Group Meeting Agenda 2023 · Issue #679 · ansible/community · GitHub](https://github.com/ansible/community/issues/679). _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/13))_ _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/13))_ CC [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) ---
**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:** [November 27, 2023, 8:00pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/14 "2023-11-27T20:00:17Z")
I voted and added the #active-vote tag to the topic. Thanks @felixfontein! ---
**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:** [December 6, 2023, 7:53am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/15 "2023-12-06T07:53:37Z")
Thanks everyone! I’ve closed the vote and counted: - 7 x +1 from SC (felixfontein, mariolenz, gotmax23, briantist, acozine, markuman, Andersson007, russoz) - 4 x +1 from community (Leo, gwmngilfen, cybette, samccann) No other votes. Can someone from SC please confirm? ---
**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:** [December 6, 2023, 8:34am UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/16 "2023-12-06T08:34:08Z")
@felixfontein i can confirm everything except 8 SC +1 but anyway the quorum is reached:) ---
**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:** [December 6, 2023, 12:33pm UTC](https://forum.ansible.com/t/vote-ended-on-2023-12-05-stop-using-the-gh-com-ansible-community-meeting-agenda-for-the-community-wg-meeting/2243/17 "2023-12-06T12:33:48Z")
Sigh, counting is hard… Of course there are 8 x +1 for SC 🙂 Thanks for checking!