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). Which tags should we use for that?
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.
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.
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.
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
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.
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.
everyone listening to the 
everyone listening to the 