#ansible-docs: DaWGs aka Docs Working Group

Meeting summary

1. Galaxy docs update (samccann, 14:35:24)
   1. https://github.com/ansible/ansible/pull/63695 (samccann, 14:38:37)
   2. https://github.com/ansible/ansible/tree/devel/docs/docsite/_extensions (felixfontein, 14:45:00)
   3. - consider putting common files/tools (sphinx, theme, extensions) in separate repo and then 'vendor' them to both ansible/ansible and galaxy for docs (samccann, 14:51:36)
   4. https://medium.com/opsops/git-vendor-295db4bcec3a possible info on git vendoring (samccann, 15:02:47)
   5. AGREED: keep galaxy docs in galaxy repo. move theme and associated files/tools/extensions to a n ansible/docs-tools repo and use git vendor/ or similar approach to share across both docsites. publish galaxy docs as product on docs.ansible.com (samccann, 15:06:31)
   6. git vendor" is a specific implementation, vendoring is a general process (which can be defined to even include submodules I think) (samccann, 15:07:58)
   
   
2. https://github.com/ansible/proposals/issues/68 (samccann, 15:09:04)
   1. https://www.irccloud.com/pastebin/9CbKMq6R/module%20docs%20that%20mention%20%22check%20mode%22 (acozine, 15:24:43)
   
   
3. Open Floor (samccann, 15:32:43)
   1. https://github.com/ansible/ansible/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Adocs+label%3AP3 (samccann, 15:34:37)

Action items

1. (none)

People present (lines said)

1. samccann (78)
2. acozine (50)
3. felixfontein (40)
4. bcoca (20)
5. zodbot (8)
6. zbr (2)
7. gundalow (1)