#ansible-docs: Docs Working Group aka DaWGs
Meeting started by acozine at 15:00:42 UTC
(full logs).
Meeting summary
- opening chatter (acozine, 15:00:48)
- role argspec not quite ready for documentation
generation. Still needs examples, and ansible-doc work
potentially (samccann,
15:02:21)
- rules for the `docsite_pr` label on GitHub (acozine, 15:09:56)
- this explains the options for the `docsite_pr`
label -
https://github.com/ansible/community/issues/579#issuecomment-809823241
(samccann,
15:16:48)
- as reviewers, we should assume the PR creator
may not be familiar with git etc and keep edits within 'suggested
edits' (samccann,
15:17:47)
- AGREED: the label
*must* be applied when Edit on GitHub is clicked from
docs.ansible.com pages and *can also* be applied when it's clicked
directly from within the GitHub site. If applying the label to both
is the easy way to implement this feature, let's do that. If "apply
to both situations" is harder to implement, let's skip the second
situation. (samccann,
15:23:06)
- package `devel` docs (acozine, 15:25:04)
- - published devel with Ansible 4 collection
list and it works (samccann,
15:25:32)
- https://docs.ansible.com/ansible/devel/collections/
(acozine,
15:26:05)
- still to come - we need a way to pull the most
recent collection versions from galaxy to publish to devel
(samccann,
15:29:32)
- meeting time follow-up (acozine, 15:36:58)
- https://github.com/ansible/community/blob/main/meetings/ical/docs.ics
(acozine,
15:37:42)
- ACTION: acozine to
regenerate the meetings calendar for ansible/community (acozine,
15:40:58)
- collection /docs folder proposal -
https://github.com/ansible-community/antsibull/issues/242
(samccann,
15:47:20)
- we agreed to use option A in that proposal.
Next step is to delve further into what this would look like, a
roadmap of tasks, and/or a sample collection (preferably with a
transfer of docs out of the Scenario Guides section). (samccann,
15:48:32)
- collection /docs/ folder (acozine, 15:49:19)
- a collection /docs folder can have multiple
.rst files and some local index. And the technical details is how do
we inject all this into docs.ansible.com (samccann,
15:55:11)
- ACTION: samccann
acozine to review logs/minutes and update docs proposal issue
accordingly (samccann,
15:56:36)
- open floor (acozine, 15:56:55)
- the breadcrumbs feature for collections was
disabled due to excessive memory use (abadger1999,
15:58:26)
- f we want to reenable breadcrumbs, we can ask
if the jenkins workers can be given more RAM or we can redesign the
implementation to not use the sphinx breadcrumb feature (samccann,
16:02:14)
- ticket to add a config option to enable
collection breadcrumbs:
https://github.com/ansible-community/antsibull/issues/267
(abadger1999,
16:06:02)
- we could pass CPUs=1 in the jenkins buld script
without reconfiguring the jenkins workers, maybe on the nightly
build? (samccann,
16:12:46)
- if we test this, we need to use
antsibull==0.29.0 as most recent has breadcrumbs disabled
(samccann,
16:13:48)
Meeting ended at 16:16:26 UTC
(full logs).
Action items
- acozine to regenerate the meetings calendar for ansible/community
- samccann acozine to review logs/minutes and update docs proposal issue accordingly
Action items, by person
- acozine
- acozine to regenerate the meetings calendar for ansible/community
- samccann acozine to review logs/minutes and update docs proposal issue accordingly
- samccann
- samccann acozine to review logs/minutes and update docs proposal issue accordingly
People present (lines said)
- acozine (86)
- samccann (78)
- abadger1999 (32)
- felixfontein (32)
- zodbot (8)
- tadeboro (6)
- dericcrago (2)
Generated by MeetBot 0.1.4.