Troubleshooting collection CI problems(samccann, 15:07:12)
our collection development docs may assume a
deeper level of ansible experience than actual new collection owners
have(samccann,
15:11:50)
ACTION: put more
troubleshooting breadrumbs in the developing/releasing collections
to run common ansible-test sanity checks locally first.(samccann,
15:14:04)
ACTION: samccann -
verify if Zuul is available for automating any collection publishing
to galaxy(samccann,
15:18:24)
- is anyone accessing/using the Docs github
project board? is it useful? -
https://github.com/ansible/ansible/projects/27?(samccann,
15:26:17)
example of a project board using the new format
-https://github.com/orgs/ansible-collections/projects/6/views/1
(samccann,
15:30:29)
- general consensus is that a better project
board is not a bad thing, but no one feels they would necessarily
use it vs the existing DaWGs agenda/meeting minutes(samccann,
15:37:02)
splitting up the antsibull package -
https://github.com/ansible-community/antsibull/issues/410(samccann,
15:37:58)
currently planning to split up antsibull in
probably three parts: antsibull-core (some shared code),
antsibull-docs (with the antsibull-docs CLI tool), and antsibull
(with the antsibull-build and antsibull-lint CLI tools, the latter
being deprecated)(samccann,
15:42:46)
this would mean `antsibull-doc updates would no
longer impact the the publicly visible changelog sanity test or the
collections test container(samccann,
15:43:40)