This one might need a better title, but the gist of it is, the core team as requested that we follow-through on original plans to split the docs such that the core team has control over the core docs and all other docs related to the package/steering committee etc go in a separate repository.
Background
About a year ago, we moved documentation out of the ansible/ansible repository to the ansible/ansible-documentation repository.
At the time we acknowledged this was an interim step to allow us to iterate on an improved docs build and ownership option. At the time, we considered two followon items:
Split docs and keep the core docs (to be defined) under the control of the core team, in this repository.
Move the remaining Ansible package docs to a repo in the ansible-community org so the community can fully own these docs.
Benefits
The Ansible community Steering Committee can more easily control the docs they must approve/regulate for the Ansible package.
Core docs return to core control, like any other project in the Ansible ecosystem so they are no longer governed by community so to speak.
User Stories
As a core maintainer, I want to keep core docs under our span of control so that they continue to match the ansible-core project.
As a reader, I want to have docs to match the projects I use (core or package) so that I have full information in one location for each project.
As a documentation contributor, I want to be able to quickly edit a file when I see a problem so that I can help keep documentation acurate.
### Tasks
- [ ] Create forum topic with list of currently-excluded files from core
- [ ] Define 'what are community, what are core, and what are steering committee docs base on that topic list
- [ ] Determine how to continue to build package docs from multiple repos
samccann
commented
1 month ago
This one might need a better title, but the gist of it is, the core team as requested that we follow-through on original plans to split the docs such that the core team has control over the core docs and all other docs related to the package/steering committee etc go in a separate repository.
Background
About a year ago, we moved documentation out of the ansible/ansible repository to the ansible/ansible-documentation repository.
At the time we acknowledged this was an interim step to allow us to iterate on an improved docs build and ownership option. At the time, we considered two followon items:
Benefits
User Stories
As a core maintainer, I want to keep core docs under our span of control so that they continue to match the ansible-core project.
As a reader, I want to have docs to match the projects I use (core or package) so that I have full information in one location for each project.
As a documentation contributor, I want to be able to quickly edit a file when I see a problem so that I can help keep documentation acurate.