# Replacing news-for-maintainers **URL:** \ **Category:** Project Discussions\ **Tags:** community, mindshare, community-wg, collections\ **Created:** [August 15, 2023, 8:27pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133 "2023-08-15T20:27:22Z")\ **Posts on this page:** 20\ **Page:** 1
**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 15, 2023, 8:27pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/1 "2023-08-15T20:27:22Z")
Currently, we have [Issues · ansible-collections/news-for-maintainers · GitHub](https://github.com/ansible-collections/news-for-maintainers/issues) to allow _any_ community member to post an announcement for collection maintainers. I would like to move this to Discourse sooner or later. Discourse has a nice feature that allows getting notifications only for the first post in a topic, so maintainers could enable that option, and then any discussion could happen _in the same topic_ (instead of a separate Github Discussion) without bothering people. ---
**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:** [August 15, 2023, 8:52pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/2 "2023-08-15T20:52:50Z")
[@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) your thoughts? (Just demonstrating group pings 😛 ) Also, does this make more sense under #Project Discussions, perhaps with some suitable tags? ---
**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 15, 2023, 10:15pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/3 "2023-08-15T22:15:24Z")
> [@gwmngilfen](#): > > Also, does this make more sense under #Project Discussions, perhaps with some suitable tags? Yeah, I wasn’t really sure where to put this. I’m still unclear of what the forum equivalent of community-topics is supposed to be. ---
**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 16, 2023, 8:23am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/4 "2023-08-16T08:23:39Z")
The idea SGTM, though i would start with moving community-topics first as the target audience is smaller (24 against 128 at the moment). Then, after we get some experience and feedback, we could move news for maintainers here with less pain / confusion. ---
**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:** [August 16, 2023, 8:34am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/5 "2023-08-16T08:34:42Z")
A post was split to a new topic: [What to rename “community-topics” to as a forum tag](https://forum.ansible.com/t/what-to-rename-community-topics-to-as-a-forum-tag/135) ---
**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 16, 2023, 5:56pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/8 "2023-08-16T17:56:00Z")
> [@gotmax23](#): > > Currently, we have [Issues · ansible-collections/news-for-maintainers · GitHub](https://github.com/ansible-collections/news-for-maintainers/issues) to allow _any_ community member to post an announcement for collection maintainers. I would like to move this to Discourse sooner or later. I agree that this isn’t ideal. Additionally, it feels a bit like wrong since it’s not really an issue, is it? Who do you think should be allowed to publish news for maintainers? The core team and the steering committee? Those are the two groups I thought about first, but maybe there are others. ---
**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:** [August 16, 2023, 7:53pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/9 "2023-08-16T19:53:04Z")
> [@gotmax23](#): > > Currently, we have [Issues · ansible-collections/news-for-maintainers · GitHub](https://github.com/ansible-collections/news-for-maintainers/issues) to allow _any_ community member to post an announcement for collection maintainers. I would like to move this to Discourse sooner or later. Discourse has a nice feature that allows getting notifications only for the first post in a topic, so maintainers could enable that option, and then any discussion could happen _in the same topic_ (instead of a separate Github Discussion) without bothering people. Maybe `news-for-maintainers` could be a (albeit a bit long) tag in the #News & Announcements category, but that category is moderated and we can’t have un-moderated tags. If **any** member should be able to post those type of announcements, then moving that tag to the #Project Discussions category might work for notifying interested people when used together with the #collections tag? ---
**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 17, 2023, 4:23am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/10 "2023-08-17T04:23:02Z")
> [@mariolenz](#): > > Additionally, it feels a bit like wrong since it’s not really an issue, is it? Yeah, pretty much. I’m excited about the forum, as it’s actually a proper place to have community discussions, as opposed to fractured Github repos that (mis)use a task tracker for discussion and announcements. > [@Leo](#): > > Maybe `news-for-maintainers` could be a (albeit a bit long) tag in the #News & Announcements category, but that category is moderated and we can’t have un-moderated tags. Can we just make the #News & Announcements open to all SC and core team members? As @mariolenz pointed out, those are the main two groups who need to post there. I assume Discourse also has the ability to make the category open to all but moderated or to move topics from other places if we need to. ---
**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:** [August 17, 2023, 8:48am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/11 "2023-08-17T08:48:22Z")
> [@mariolenz](#): > > Who do you think should be allowed to publish news for maintainers? The core team and the steering committee? > [@Leo](#): > > Maybe `news-for-maintainers` could be a (albeit a bit long) tag in the #News & Announcements category, but that category is moderated and we can’t have un-moderated tags. Bring these two together - you **can** restrict the use of a tag to specific groups. For example, only the Community Team can use the #official tag right now, to mark official events. So, we _could_ create a tag for this and give the rights to use it to certain groups (or make a new group, if needed). We can then tell maintainers “hey, you should set this tag to Watched in [your preferences](https://forum.ansible.com/my/preferences/tracking)” so they get notifications appropriately. Adding #collections seems fair too. > [@gotmax23](#): > > Can we just make the #News & Announcements open to all SC and core team members? This is something we need to discuss more widely, I’ll make a new topic for this. Right now it’s only available to our team but that was always a placeholder - we need to set expectations here. > [@gotmax23](#): > > I assume Discourse also has the ability to make the category open to all but moderated or to move topics from other places if we need to. It does. Although I’m unclear if you get a notification for a moved topic. We should test that 😛 ---
**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:** [October 4, 2023, 5:22am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/12 "2023-10-04T05:22:48Z")
I just created a new announcement in the news-for-maintainers repository ([ansible-core devel drops support for Python 2.7 and 3.6 · Issue #60 · ansible-collections/news-for-maintainers · GitHub](https://github.com/ansible-collections/news-for-maintainers/issues/60)), but I have no idea where to post it here. ---
**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:** [October 4, 2023, 8:21am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/13 "2023-10-04T08:21:36Z")
We never did finish this debate, oops. As things stand now, I would suggest either a post to #Ecosystem Releases or here in #Project Discussions, tagged with #collections but possibly also a new tag, perhaps `#maintainers`? We can ask that maintainers follow that tag, just as they would follow the old repo, and then they’ll get emails/notifications as appropriate. Does that work? ---
**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:** [October 4, 2023, 7:13pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/14 "2023-10-04T19:13:37Z")
Does this warrant a separate category under #News & Announcements? news-for-maintainers is a specific type of news meant for collection maintainers. ---
**Author:** ![maxamillion](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/maxamillion/32/98_2.png) [@maxamillion](https://forum.ansible.com/u/maxamillion)\ **Post date:** [October 5, 2023, 1:15pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/15 "2023-10-05T13:15:02Z")
+1 Move all the things to the forum! 🕶 ---
**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:** [October 5, 2023, 2:03pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/16 "2023-10-05T14:03:02Z")
I’m wary of that - in the same vein of “lets not have 30 categories under #Project Discussions for all the projects”, I don’t really want 10+ types of news. Even the 3 subcategories we have already feels confusing. Given we expect maintainers to follow “a process” whatever that process is, can we make it “follow this tag” or even “join this group” which can have a tag automatically added. ---
**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:** [October 9, 2023, 9:02am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/17 "2023-10-09T09:02:48Z")
@gwmngilfen the group + tag sounds very good to me. In this case, there’ll be no need for maintainers to mess around tags, subscriptions, etc., they just click “join” that’s it. The group can be called `collection maintainers`, the tag could be `news-for-maintainers`. ---
**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:** [October 9, 2023, 5:54pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/18 "2023-10-09T17:54:38Z")
If we create a `news-for-maintainers` tag in `News & Announcements`, will anyone be able to post to it? > [@Andersson007](#): > > @gwmngilfen the group + tag sounds very good to me. In this case, there’ll be no need for maintainers to mess around tags, subscriptions, etc., they just click “join” that’s it. Indeed, I like the group idea. It will make things easier for everyone, and it’s nice to provide collection maintainers a forum flair to recognize their work. ---
**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:** [October 12, 2023, 9:22am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/19 "2023-10-12T09:22:08Z")
> [@gotmax23](#): > > If we create a `news-for-maintainers` tag in `News & Announcements`, will anyone be able to post to it? The tag could well be in #Project Discussions not in #News & Announcements - it doesn’t matter where the post is if you’re following the tag, and it’s likely such news might well lead to discussions anyway. I’m _really_ trying to keep #News & Announcements and it’s categories focussed on things that _lots_ of people would want to see (and though I might wish for thousands of maintainers, we’re not here yet 😛) ---
**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:** [October 12, 2023, 4:57pm UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/20 "2023-10-12T16:57:19Z")
Okay, we can try a #news-for-maintainers tag in Project Discussions. ---
**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:** [October 13, 2023, 8:15am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/21 "2023-10-13T08:15:24Z")
I’ve created #news-for-maintainers - do you want a description sidebar? ---
**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:** [October 17, 2023, 6:43am UTC](https://forum.ansible.com/t/replacing-news-for-maintainers/133/22 "2023-10-17T06:43:23Z")
hey all, great discussion, thanks it’s now good time to push things forward. i created a [roadmap](https://github.com/ansible-community/community-team/issues/367), did I miss anything? While you’re taking a look, i’ll start creating the `Collection Maintainers` group. UPDATED: created [the group](http://forum.ansible.com/g/CollectionMaintainer). [Next page](https://forum.ansible.com/t/replacing-news-for-maintainers/133.md?page=2)