# Allow release-managers to post Ecosystem Releases

**URL:** <https://forum.ansible.com/t/allow-release-managers-to-post-ecosystem-releases/3549>\
**Category:** Forum Guide & Feedback\
**Tags:** release-management\
**Created:** [January 31, 2024, 6:16pm UTC](https://forum.ansible.com/t/allow-release-managers-to-post-ecosystem-releases/3549 "2024-01-31T18:16:22Z")\
**Posts on this page:** 4\
**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:** [January 31, 2024, 6:16pm UTC](https://forum.ansible.com/t/allow-release-managers-to-post-ecosystem-releases/3549/1 "2024-01-31T18:16:22Z")

</div>

Would it be possible to allow members of the `@release-managers` group to post to the #Ecosystem Releases category without having our posts moderated? Posting announcements to the forum is now a part of the Ansible package release process.

---

<div class="post-metadata">

**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:** [February 1, 2024, 12:09am UTC](https://forum.ansible.com/t/allow-release-managers-to-post-ecosystem-releases/3549/2 "2024-02-01T00:09:55Z")

</div>

Yes, this should be possible and I was looking into it to allow the publishing of all ecosystem releases directly by a specific dedicated group (EcoReleases).

There is also another option I think, which would be adding the group as moderators.

I think having a deduccated group with permissions to publish is better than giving moderator level to the whole category to every group that needs to post there. It will add some maintenance as we need to keep that list updated.

The downside of the publishing permissions per group is that we remove the moderation queue I think, meaning only those in the designated group/s can create topics. I need to do some testing in the sandbox to confirm, unless @gwmngilfen has the answer or a better alternative.

---

<div class="post-metadata">

**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:** [February 1, 2024, 9:14am UTC](https://forum.ansible.com/t/allow-release-managers-to-post-ecosystem-releases/3549/3 "2024-02-01T09:14:14Z")

</div>

I believe we can do both if we promote the release-managers group to category moderators in that particular category. I can take a look when I have a moment, but travel starts tomorrow 🛫😛

---

<div class="post-metadata">

**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:** [February 12, 2024, 4:10pm UTC](https://forum.ansible.com/t/allow-release-managers-to-post-ecosystem-releases/3549/4 "2024-02-12T16:10:02Z")

</div>

OK, I have added the [EcoReleasePublishers](http://forum.ansible.com/g/EcoReleasePublishers/) group as a category moderator for #Ecosystem Releases - please give it a try!

(That seemed a better fit than the release-managers group, based on the name and who are members of the group, but it can obviously be changed)
