# Where should Working Group and other process docs live?

**URL:** <https://forum.ansible.com/t/where-should-working-group-and-other-process-docs-live/2760>\
**Category:** Project Discussions\
**Tags:** community, documentation\
**Created:** [December 5, 2023, 5:18pm UTC](https://forum.ansible.com/t/where-should-working-group-and-other-process-docs-live/2760 "2023-12-05T17:18:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**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:** [December 5, 2023, 5:18pm UTC](https://forum.ansible.com/t/where-should-working-group-and-other-process-docs-live/2760/1 "2023-12-05T17:18:22Z")

</div>

As part of [Moving ansible/community content to ansible-community](http://forum.ansible.com/t/moving-ansible-community-content-to-ansible-community/1928/1) , we need to discuss where we want to put detailed process documentation that a working group might have. The wiki at the old location is stale, but does show that some working groups do have more detailed docs than can go on a single forum group page here.

Some examples that come to mind:

- Documentation WG needs a place to document how to publish documentation for a release.
- Community WG currently documents all its processes on [docs.ansible.com](https://docs.ansible.com/ansible/latest/community/steering/steering_index.html)
- Release Managers WG documents its processes at [Ansible Package Release Management](https://ansible.readthedocs.io/projects/ansible-build-data/)

So the specific questions that come to mind for me:  
1 - Should we let WGs just put docs where they want? (aka ain’t broke, don’t fix it)  
2 - Do we need a WG ‘summary’ page that links to all of them?

For #2, we do have [this docs page](https://docs.ansible.com/ansible/latest/community/communication.html#working-group-list), but it’s not particularly easy to read. We could reformat it some, but perhaps the better approach is we ensure any WG with a separate process docsite includes that in their forum group page, and then that docs page just links to the forum group pages? (there’s a PR already to do that for the WGs that do have a forum page now).

---

<div class="post-metadata">

**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:** [December 7, 2023, 7:08pm UTC](https://forum.ansible.com/t/where-should-working-group-and-other-process-docs-live/2760/2 "2023-12-07T19:08:12Z")

</div>

Related to this, we also have process docs not tied to a specific working group, such as:

- [Meetup toolkit](https://ansible.readthedocs.io/projects/meetup/en/latest/) - An aid to those coordinating Ansible meetups
- [Project onboarding and docs toolkit](https://ansible.readthedocs.io/projects/project-onboarding/en/latest/) - Guidelines for new Ansible projects on repo setup and proposed documentation structure

We also have a lot of process docs on [docs.ansible.com](http://docs.ansible.com) for the community, steering committee, as well as collection inclusion (which I think may still be split between docs and a github readme). Adding to that list, we’ll probably have more docs for guidelines on running the community in the future so… growing list.

Some ideas of the top of my head:

- For Working groups here in the forum - add process links to the group page summary
- For docs not associated with a working group - Form a ‘group’ here anyway and add to the forum group page summary.

Longer term - we should have a ‘presence’ on the community website - maybe a subpage for the active working groups to say what they do, and then point to the group page here on the forum. [Gnome](https://www.gnome.org/get-involved/) has something like this
