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)
anyone can add to the agenda at
https://github.com/ansible/community/issues/521(samccann,
14:45:01)
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)
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)
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)
preliminary start date for the Collections
Transition: ansible/ansible devel branch will freeze on March 2nd
for the transition(acozine,
14:59:23)
we have already instituted a No New Modules
policy(acozine,
15:01:42)
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)
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)
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)