# How to resolve community-wg topics **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg\ **Created:** [April 1, 2024, 8:49pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688 "2024-04-01T20:49:36Z")\ **Posts on this page:** 9\ **Page:** 1
**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:** [April 1, 2024, 8:49pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/1 "2024-04-01T20:49:36Z")
> [@Unmaintained collection: community.rabbitmq](http://forum.ansible.com/t/unmaintained-collection-community-rabbitmq/3931/12): > > I agree that we should “close” the discussion, but I don know how to technically achieve this. I have the ability to lock the topic, but I don’t know if that helps when SC folks search for all topics with the `community-wg` tag. Was there a discussion somewhere on how to close wg topics here in the forum? ---
**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:** [April 1, 2024, 8:54pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/2 "2024-04-01T20:54:39Z")
Looks like the workflow is defined at [community-topics/community\_topics\_workflow.md at main · ansible-community/community-topics · GitHub](https://github.com/ansible-community/community-topics/blob/main/community_topics_workflow.md). The closest I can see is under the implementing section, where it’s marked as `implemented`. Though in this case, perhaps it needs `not implemented` instead? ---
**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:** [April 2, 2024, 4:26pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/3 "2024-04-02T16:26:48Z")
@felixfontein What do you mean by “close this”? Deleting / locking / archiving this thread or what? Or maybe add a `closed` or `resolved` or similar tag? Personally, I can live with doing nothing at all and “close” this discussion by agreeing that we don’t see issues or problems with the collection anymore and don’t discuss it further. ---
**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:** [April 2, 2024, 7:45pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/4 "2024-04-02T19:45:13Z")
I remember that we were discussing about the `implemented` / … tag once, my personal favorite back then would have been `resolved` since it’s a more generic term that would also apply here. Maybe we need to start a separate discussion on that - I think we should stop polluting this topic with it 🙂 Can someone with moderator rights cut off this part of this topic as a new topic? ---
**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:** [April 2, 2024, 8:28pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/5 "2024-04-02T20:28:53Z")
I think I did it correctly 🙂 This is a new topic now. ---
**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:** [April 3, 2024, 6:12pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/6 "2024-04-03T18:12:03Z")
> [@felixfontein](#): > > I remember that we were discussing about the `implemented` / … tag once, my personal favorite back then would have been `resolved` since it’s a more generic term that would also apply here. +1 to **resolved**. Another option is `community-wg-done`, if I recall correctly, we had a 19 or 20 char limit for tags. ---
**Author:** ![cybette](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/cybette/32/16_2.png) [@cybette](https://forum.ansible.com/u/cybette)\ **Post date:** [April 3, 2024, 6:19pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/7 "2024-04-03T18:19:09Z")
+1 to `resolved` or `done`, an issue can be resolved even if there’s no implementation. ---
**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:** [April 3, 2024, 6:53pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/8 "2024-04-03T18:53:30Z")
We talked about this a bit at today’s community meeting. I think we have identified three approaches to this: 1. Tag discussions with another tag like `resolved`, `done`, `community-wg-done`, etc. A short one can be reused by everyone, a long (prefixed) one is unique for a working group. 2. Replace the `community-wg` tag with another tag like `community-wg-resolve` (the `d` does not fit due to the max tag length) or `community-wg-done`. This makes it easy to list all discussions that are open by simply looking for the `community-wg` tag (inside Project Discussions to be more specific). 3. Enable the feature which allows to mark discussions as “solved” by marking one answer as “solution” for Project Discussion. One advantage here is that the resolving message will be shown below the first post, so it’s easy to see what the resolution of such a topic is. I hope I didn’t forget anything important 🙂 ---
**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\ **Post date:** [April 3, 2024, 8:39pm UTC](https://forum.ansible.com/t/how-to-resolve-community-wg-topics/4688/9 "2024-04-03T20:39:04Z")
Personally, I like the 3rd option the most, but might I make a suggestion? Instead of enabling the solutions option for the entire Project Discussions category, what about creating a sub category `Community Workgroups` (for e.g.) and enabling solutions there? Pin a “How to” topic on etiquette for the solutions to topics there. Unlike Get Help where solutions are the best/most-direct answer to the OP’s problem, the solutions should mark a summary reply of the thread’s general consensus (perhaps voted on before marking as the solution).