DaWGs aka Documentation Working group | Ansible Docs | #docs:ansible.com
Meeting started by @samccann:ansible.im at 2024-03-19 16:01:28Meeting summary
- TOPIC: Documentation Updates (@samccann:ansible.im, 16:04:10)
- LINK: https://github.com/ansible/ansible-documentation/pull/1209 (@orandon:ansible.im, 16:08:06)
- INFO: curious if anyone has thoughts on expanding "unintended functionality" to avoid ambiguity - at first it sounded to me like it might refer to a bug (@orandon:ansible.im, 16:08:49)
- INFO: a group of 14 student tech writers will be choosing doc issues from Ansible (`ansible/ansible-documentation`) as well as Foreman and another Gnome project - we should be hearing from them next week (@orandon:ansible.im, 16:36:57)
- INFO: here's a screengrab of the project schedule: (@orandon:ansible.im, 16:37:30)
- INFO: need someone to take care of running https://github.com/ansible/ansible-documentation/blob/devel/hacking/tagger/tag.py for the next few weeks (tagging rc and releases) (@samccann:ansible.im, 16:52:23)
- INFO: You need a directory with an ansible-documentation and ansible-core checkout and then run ./tag.py tag after new ansible-core releases or rcs (@samccann:ansible.im, 16:52:42)
- INFO: The script assumes the upstream is the origin remote, but you can pass a flag to change that (@samccann:ansible.im, 16:53:18)
- INFO: For example, `./tag.py --remote upstream tag` if the upstream repo is the `upstream` remote (@gotmax:matrix.org, 16:54:16)
- TOPIC: open floor (@samccann:ansible.im, 16:55:12)
- LINK: https://forum.ansible.com/t/table-stakes-for-including-projects-on-the-ecosystem-page/4341 (@orandon:ansible.im, 16:55:53)
Meeting ended at 2024-03-19 17:02:50
Action items
- (none)
People present (lines said)
- @orandon:ansible.im (41)
- @samccann:ansible.im (40)
- @utoddl:matrix.org (14)
- @gotmax:matrix.org (8)
- @deric.crago:ansible.im (4)
- @sutapa_b:matrix.org (2)
- @ansibot:ansible.im (2)
Full logs: full_log.txt