# Reduce fragmentation: moving stuff to the forum and archiving repos **URL:** \ **Category:** Project Discussions\ **Tags:** resolved, community-wg\ **Created:** [April 25, 2024, 7:17am UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141 "2024-04-25T07:17:27Z")\ **Posts on this page:** 9\ **Page:** 1
**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:** [April 25, 2024, 7:17am UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/1 "2024-04-25T07:17:27Z")
As community-topics repo is on the way to oblivion (the [discussion](http://forum.ansible.com/t/community-topics-archiving-the-repo/4990/7) and thanks everyone who鈥檚 closing issue there), i suggest doing more to reduce fragmentation. How about moving activities from the following repos and archiving them: - [GitHub - ansible-collections/ansible-inclusion: Requests to include new collections into the ansible package](https://github.com/ansible-collections/ansible-inclusion) - [GitHub - ansible-collections/overview: Collections overview, how to request a namespace](https://github.com/ansible-collections/overview) I know there are many inactive repos that we can archive but in this topic i would focus only on repos we use actively like the above. If anything else actively used by the community that we can move here comes to your mind please mention. The algorithm will be roughtly: 1. Move all the activities to the forum (if needed, create groups, invite people, add categories/tags) 2. Make sure all the references on [docs.ansible.com](http://docs.ansible.com) and on readthedocs poin to the forum 3. Put a note in READMEs and open an issue in affected repos about moving the activities to the forum 4. Archive the repo I also don鈥檛 think we should vote on this one: just imo a verbal approval of some people using particular repos would be enough. If it鈥檚 silent here, we鈥檒l interpret it as an agreement 馃槈 Thoughts? ---
**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:** [May 21, 2024, 7:28am UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/2 "2024-05-21T07:28:17Z")
Let鈥檚 proceed with [overview](https://github.com/ansible-collections/overview) I see the following actions we need to do in order to archive the repo - I don鈥檛 think README is relevant anymore, so nothing from it should be moved to [docs.ansible.com](http://docs.ansible.com) - move removal\_from\_ansible.rst to [docs.ansible.com](http://docs.ansible.com) (in progress, [Move Ansible package collection removal process to docs.ansible.com by Andersson007 路 Pull Request #1492 路 ansible/ansible-documentation 路 GitHub](https://github.com/ansible/ansible-documentation/pull/1492)) - move collection\_checklist.md to [docs.ansible.com](http://docs.ansible.com) - stub out the moved docs - status.rst: outdated, ignore - close/finish currently open PRs - opened an issue to notify subscribed people [FYI This repo is getting archived 路 Issue #241 路 ansible-collections/overview 路 GitHub](https://github.com/ansible-collections/overview/issues/241) - created a forum mechanism as a replacement for requesting a community collection repo, updated the communication guide [Requesting a collection: replace overview links by Andersson007 路 Pull Request #1529 路 ansible/ansible-documentation 路 GitHub](https://github.com/ansible/ansible-documentation/pull/1529) - update all occurrences on [docs.ansible.com](http://docs.ansible.com) [Requesting a collection: replace overview links by Andersson007 路 Pull Request #1529 路 ansible/ansible-documentation 路 GitHub](https://github.com/ansible/ansible-documentation/pull/1529) - update README [README.rst: update wrt the repo archiving by Andersson007 路 Pull Request #242 路 ansible-collections/overview 路 GitHub](https://github.com/ansible-collections/overview/pull/242) - archive the repo As there was no opposition to the proposal, I鈥檒l start implementing it. If I missed anything, please put a comment. If you wanna help, raise your hand:) ---
**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:** [May 21, 2024, 7:34am UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/3 "2024-05-21T07:34:05Z")
UPDATE: decided to suspend this for now considering the community feedback. Let鈥檚 also proceed with [ansible-inclusion](https://github.com/ansible-collections/ansible-inclusion) - Move the collection\_checklist.md file to somewhere - Create a forum category and tags corresponding to the labels used in the repo - Create a forum group putting _relevant_ content from [GitHub - ansible-collections/ansible-inclusion: Requests to include new collections into the ansible package](https://github.com/ansible-collections/ansible-inclusion) to the group description - Associate the group with the tags - Reopen in-progress discussion on the forum, put a comment inviting participants to proceed on the forum topics - Update README - Update all occurrences on [docs.ansible.com](http://docs.ansible.com) - Archive the forum As there was no opposition to the proposal, we can start implementing it. If I missed anything, please put a comment. If you wanna help, raise your hand:) ---
**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:** [May 22, 2024, 6:24pm UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/4 "2024-05-22T18:24:04Z")
I鈥檓 not sure whether moving inclusion request discussions to the Forum will make it easier. GH discussions allow threads, which are more readable (if used correctly) than discussions here, at least for longer discussions. (I fully agree with the overview repo though.) ---
**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:** [May 28, 2024, 6:10am UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/5 "2024-05-28T06:10:57Z")
> [@felixfontein](#): > > I鈥檓 not sure whether moving inclusion request discussions to the Forum will make it easier. While working on the overview, was thinking about the same. As there are more voices besides that one in my head, let鈥檚 keep it as-is? @mariolenz @markuman @gotmax23 @russoz @briantist are you OK with not moving things from `ansible-inclusion` to the forum? ---
**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:** [May 28, 2024, 10:14am UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/6 "2024-05-28T10:14:02Z")
I tend to move the inclusion requests to the forum. But I鈥檓 not against keeping it as-is if you think GH discussions are better for this. ---
**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:** [May 30, 2024, 8:50am UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/7 "2024-05-30T08:50:37Z")
OK, cool, let鈥檚 suspend the ansible-inclusion-to-forum move for now, i鈥檝e just added a comment in the related TODO list. Another idea is how about moving the inclusion-related discussions to `ansible-build-data`? Not saying that it鈥檚 a good one coz i don鈥檛 hang out in the repo a lot but what do you think? ---
**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:** [May 30, 2024, 2:40pm UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/8 "2024-05-30T14:40:58Z")
At the end of the day, including a new collection means adding it to `ansible-build-data`. At the spur of the moment, I would say moving inclusion discussions there makes sense. We would have the discussion about inclusion and the inclusion itself in one place. Or does anyone ~~say~~ see any drawbacks to this? ---
**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:** [June 1, 2024, 8:21pm UTC](https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141/9 "2024-06-01T20:21:37Z")
I don鈥檛 think moving the discussions to ansible-build-data is a good idea. That repository is for working on and discussing Ansible releases, not for discussing adding new collections to Ansible. I think it鈥檚 better to keep these two things separate. (Also this would make it a lot harder to sort discussions in my mailbox. Right now I have two different folders for ansible-inclusion and for ansible-build-data. Using two different places makes it a lot easier to keep them separate.)