Notification time stamped 2020-03-31 16:23:51 UTC
===========================================
#ansible-docs: Docs Working Group aka DaWGs
===========================================
Meeting started by acozine at 14:31:56 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/ansible-docs/2020-03-31/docs_working_gr...
.
Meeting summary
---------------
* sanity check (acozine, 14:32:31)
* contributor summit summary (acozine, 14:47:33)
* Contributor summit summary -
https://meetbot.fedoraproject.org/ansible-community/2020-03-29/ansible_co...
(samccann, 14:47:52)
* contributor summit log -
https://meetbot.fedoraproject.org/ansible-community/2020-03-29/ansible_co...
(samccann, 14:48:12)
* docs discussions focues on changelog/porting guide optins and how
ansible docs will be handled in the NWO (samccann, 14:51:48)
* changelogs and porting guides from Collections (acozine, 14:54:21)
* LINK:
https://github.com/ansible-collections/overview/issues/18#issuecomment-60...
for reference (samccann, 15:34:24)
* one idea - we would have two options for collection owners - 1. use
our tool, or 2. use your own solution and provide us with a file
that looks like <proposal>
https://gist.github.com/felixfontein/d15112c7a866e8806d7e9f9ea4085cfa
(samccann, 15:42:13)
* this would require (1) core team has to get the ansible/ansible
changelog generator to output the new format. (2) the community
team would have to write code for the acd changelog generator to
consume the new format (samccann, 15:42:30)
* another idea - we mandate one tool and integrate that tool's output
with core's changelog (aka collections in ACD would not have a
choice but must use this tool) (samccann, 15:45:10)
* - third idea - we link to peoples disparate change logs (least work,
but doesn't give comprehensive view of changes, just a bunch of
links users have to follow) (samccann, 15:46:00)
* - fourth idea - people write an input => input transform + metadata
of what input fragments are needed for the next release. - similar
to first proposal, but there are individual fragments instead of a
container (samccann, 15:46:58)
* fifth idea - we handle ACD like a linux distro - changelogs would be
links. however, there would be a common release notes that
individual components could contribute things they considered major
enough to be worthy of that. (samccann, 15:48:12)
* LINK:
https://github.com/abadger/misc-work/blob/master/ansible/build_acd/acd.in
(abadger1999, 16:11:52)
* ACD as currently envisioned would have 55 collections (samccann,
16:12:38)
* AGREED: we will add the pros/cons for all the ideas here -
https://github.com/ansible-collections/overview/issues/18
(samccann, 16:18:43)
* open floor (acozine, 16:21:51)
Meeting ended at 16:23:51 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* acozine (111)
* felixfontein (87)
* samccann (83)
* abadger1999 (67)
* bcoca (34)
* gundalow (11)
* zodbot (10)
* zbr (2)
* tremble (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`:
http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/ansible-docs/2020-03-31/docs_working_gr...
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorap...