#ansible-docs: Docs Working Group aka DaWGs

Meeting summary

1. introductory chatter (acozine, 14:30:43)
   
2. porting guide and changelog updates (acozine, 14:34:18)
   1. have an ansible-base porting guide as a separate document, with that same information also pulled into the Ansible porting guide - poll 3 agree, 3 didn't vote (samccann, 15:05:49)
   2. ansible-base has its own changelog.rst already (samccann, 15:06:08)
   3. https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst (felixfontein, 15:06:31)
   4. https://gist.github.com/felixfontein/7d5efcc70c8a25c218d9e8082f5ee92f#file-porting_guide_2-10-rst (felixfontein, 15:10:59)
   5. sample porting guide https://gist.github.com/felixfontein/7d5efcc70c8a25c218d9e8082f5ee92f#file-porting_guide_2-10-rst (samccann, 15:11:28)
   6. ACTION: samccann create an issue on ansible-collection/overview to gather the list of things we need to know to get collection changelogs into the Ansible changelog.rst - in preparation for creating issues in each collection repo on what they need to do (samccann, 15:17:48)
   7. ansible build data (aka included collections ) - https://github.com/ansible-community/ansible-build-data/blob/main/2.10/acd.in (samccann, 15:19:08)
   8. how and when we split anible-base docs from ansible (aka acd) docs is a deeper discussion for later (samccann, 15:23:38)
   9. ACTION: samccann add Splitting ansible-base from Ansible docs to agenda (samccann, 15:24:20)
   10. ansible-base tentatively comes out in mid Aug, and Ansible (acd) in mid Sept (dates subject to change for sure) (samccann, 15:33:05)
   11. https://github.com/ansible/ansible/issues/70348 (felixfontein, 15:36:21)
   12. pip install ansible-base will have a problem requiring users to uninstall first or use --force.. see https://github.com/ansible/ansible/issues/70348 (samccann, 15:38:22)
   13. this upgrade problem is only for pre 2.10 to 2.10+ upgrades, but users will do this at their own pace so needs solid docs 'somewhere' that will linger and be noticable to cover this (samccann, 15:40:09)
   14. ACTION: samccann create a priority issue to track this upgrade problem in prominent places besides the porting guide (samccann, 15:41:32)
   15. https://github.com/ansible/ansible/issues/70348 (bcoca, 15:42:36)
   16. tracking issue for upgrade problems - https://github.com/ansible/ansible/issues/70392 (samccann, 15:50:56)
   17. need to set priorities for docs for ansible-base release and ansible release (samccann, 15:55:32)
   
   
3. open floor (acozine, 15:55:59)

Action items

1. samccann create an issue on ansible-collection/overview to gather the list of things we need to know to get collection changelogs into the Ansible changelog.rst - in preparation for creating issues in each collection repo on what they need to do
2. samccann add Splitting ansible-base from Ansible docs to agenda
3. samccann create a priority issue to track this upgrade problem in prominent places besides the porting guide

Action items, by person

1. samccann
   1. samccann create an issue on ansible-collection/overview to gather the list of things we need to know to get collection changelogs into the Ansible changelog.rst - in preparation for creating issues in each collection repo on what they need to do
   2. samccann add Splitting ansible-base from Ansible docs to agenda
   3. samccann create a priority issue to track this upgrade problem in prominent places besides the porting guide

People present (lines said)

1. felixfontein (108)
2. acozine (108)
3. samccann (78)
4. baptistemm (15)
5. bcoca (11)
6. abadger1999 (10)
7. zodbot (9)
8. cbudz (2)
9. gundalow (1)