Notification time stamped 2020-12-03 16:49:28 UTC
============================================================================= #ansible-docs: DaWGs supplemental meeting aka The Great Docsite Split of 2021 =============================================================================
Meeting started by acozine at 15:31:38 UTC. The full logs are available at https://meetbot.fedoraproject.org/ansible-docs/2020-12-03/dawgs_supplemental... .
Meeting summary --------------- * opening chatter (acozine, 15:32:26) * draft proposal doc https://hackmd.io/TQmzyhCUSSKa22iFR_079A?both (samccann, 15:39:52) * hacked ansible-collections docsite: http://docs.testing.ansible.com/ansible/2.11/ (samccann, 15:40:08) * hacked ansible-core docsite: http://docs.testing.ansible.com/ansible/devel/ (samccann, 15:40:22) * hacked docsites will disappear without warning in a few weeks (acozine, 15:40:54) * The guiding principle here is that the Ansible Collections Documentation includes only the scenario/platform guides specific to those collections, and the overall collection index. Everything else is really based on the version of ansible-core included and is thus in the Ansible Core Documentation. (samccann, 15:41:09)
* Which documentation topics/sections will end up where (acozine, 15:42:04)
* pros and cons of splitting the docs (acozine, 15:47:07) * we should duplicate ansible.builtin on both docsites until those plugins are removed from core. Core users will need that info Ansible package docsite updates won't be in sync with core releases. (samccann, 16:02:17) * consider adding to the core banner for those plugins 'for the full collection index go here' to point to ansible-collections (samccann, 16:02:53) * consider interim stub pages on ansible-core-2.11 to show where all the scenario etc guides have moved to (samccann, 16:20:15) * general problems with latest https://hackmd.io/TQmzyhCUSSKa22iFR_079A?both#How-to-handle-latest (samccann, 16:24:00)
* handling /latest/ (samccann, 16:24:10) * the /latest/ convention solves the problems of personal/blogpost links going stale. if they link to a /latest/ page, it always stays valid (samccann, 16:33:14) * make sure any links from ansible-collections to ansible-core docs uses the version specific url, not /latest/ so it matches the core version used w. Ansible (samccann, 16:36:48) * general feeling so far is to keep /latest/ for both docsites (samccann, 16:40:51) * ACTION: samccann to discuss moving scenario guide .rst files to ansible-collections somewhere -w gundalow and abadger1999 (samccann, 16:44:30) * ACTION: explore generally how much of our current documentation actually needs to be versioned and how versioned and unversioned docs could live together on docs.ansible.com in perfect harmony (samccann, 16:47:36)
Meeting ended at 16:49:28 UTC.
Action Items ------------ * samccann to discuss moving scenario guide .rst files to ansible-collections somewhere -w gundalow and abadger1999 * explore generally how much of our current documentation actually needs to be versioned and how versioned and unversioned docs could live together on docs.ansible.com in perfect harmony
Action Items, by person ----------------------- * samccann * samccann to discuss moving scenario guide .rst files to ansible-collections somewhere -w gundalow and abadger1999 * **UNASSIGNED** * explore generally how much of our current documentation actually needs to be versioned and how versioned and unversioned docs could live together on docs.ansible.com in perfect harmony
People Present (lines said) --------------------------- * samccann (108) * acozine (89) * dmsimard (29) * zodbot (10) * lmodemal (3) * felixfontein (2) * cyberpear (1) * dericcrago (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/ansible-docs/2020-12-03/dawgs_supplemental...
-- You received this message due to your preference settings at https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedoraproj...