#ansible-docs: Docs Working Group aka DaWGs

Meeting summary

1. how to add agenda items (acozine, 14:35:18)
   1. anyone can add items to the agenda for the Docs Working Group (DaWGs) - the 2020 agenda is https://github.com/ansible/community/issues/521 (acozine, 14:44:59)
   2. anyone can add to the agenda at https://github.com/ansible/community/issues/521 (samccann, 14:45:01)
   
   
2. quick status (acozine, 14:45:42)
   1. -community help on docs broken links has been fantastic! most issues are closed already! (samccann, 14:46:24)
   2. https://github.com/ansible/ansible/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3Adocs+ (acozine, 14:47:28)
   3. looking for help reviewing open docs PRs, especially the first page at https://github.com/ansible/ansible/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3Adocs+ (samccann, 14:48:27)
   
   
3. Collections (gundalow, 14:49:58)
   1. I started https://github.com/ansible-collections/overview/pull/3 which aims to give some more context around Collections (what/why/how) (gundalow, 14:50:29)
   2. i hope for ^ to be a living document, by that I mean we will keep on updating it with new questions (and hopefully answers); examples; and links to other bits of documentation (gundalow, 14:51:46)
   3. preliminary start date for the Collections Transition: ansible/ansible devel branch will freeze on March 2nd for the transition (acozine, 14:59:23)
   4. we have already instituted a No New Modules policy (acozine, 15:01:42)
   
   
4. open floor (acozine, 15:05:43)
   1. cbudz working on linking docs.ansible.com test section to molecule docs if we can find the owner of said docs (samccann, 15:14:53)
   
   
5. What to do with module links in porting guides (samccann, 15:17:53)
   1. http://docs.testing.ansible.com/ansible/devel/porting_guides/porting_guides.html (samccann, 15:20:56)
   2. module links in old porting guides will need some kind of fix when all the modules move to a new collection location. (samccann, 15:21:24)
   3. could use some help to figure out a way to have a variable in the url in .rst that picks up the version from the conf.py file and inserts it. That way we can make the same fix to all versions of the docs and backport cleanly (samccann, 15:24:42)
   4. AGREED: we should use the urls to replace the internal xrefs for modules in porting guides. (e.g. 2.8 porting guide use 2.8 based module urls, etc) (samccann, 15:25:29)

Action items

1. (none)

People present (lines said)

1. acozine (87)
2. samccann (41)
3. gundalow (20)
4. cbudz (12)
5. zodbot (9)
6. kmaxwell (7)
7. felixfontein (1)