# Meeting Log | Ansible Docs | 2024-04-23 15:03:54

**URL:** <https://forum.ansible.com/t/meeting-log-ansible-docs-2024-04-23-1554/5094>\
**Category:** MeetingBot Logs\
**Tags:** documentation\
**Created:** [April 23, 2024, 3:42pm UTC](https://forum.ansible.com/t/meeting-log-ansible-docs-2024-04-23-1554/5094 "2024-04-23T15:42:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MeetingBot](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@MeetingBot](https://forum.ansible.com/u/MeetingBot)\
**Post date:** [April 23, 2024, 3:42pm UTC](https://forum.ansible.com/t/meeting-log-ansible-docs-2024-04-23-1554/5094/1 "2024-04-23T15:42:58Z")

</div>

# Documentation Working Group meeting | Ansible Docs | #docs:ansible.com
Meeting started by @samccann:ansible.im at 2024-04-23 15:03:54  
  

### Meeting summary

1. TOPIC: New Items (@samccann:ansible.im, 15:04:05)

  1. INFO: we have a new workflow to build package docs on demand https://github.com/ansible/ansible-documentation/actions/workflows/build-package-docs.yaml (@samccann:ansible.im, 15:04:52)
  2. INFO: Question for DaWGs: Does anyone have thoughts or opinions on who is allowed to run the workflow? At the moment, anyone who is a collaborator with write permissions can trigger the workflow. (@samccann:ansible.im, 15:05:24)
  3. INFO: is it possible to see who ran the workflow? esp, for production. What about list of PRs included in the update? (@samccann:ansible.im, 15:11:48)
  4. INFO: GH actions does say who triggered a run. (@samccann:ansible.im, 15:14:41)
  5. INFO: Github Actions does show who ran the workflow, good esp, for production. What about list of PRs included in the update? (@samccann:ansible.im, 15:15:54)
  6. INFO: consider just one workflow, limited to commit rights people for now (@samccann:ansible.im, 15:22:23)
  7. INFO: important discussion going on for the future of the Ansible package - http://forum.ansible.com/t/future-of-the-ansible-community-package/4902/39 please vote/add your opinions (@samccann:ansible.im, 15:23:12)

2. TOPIC: Triage (@samccann:ansible.im, 15:25:18)

3. TOPIC: Documentation Updates (@samccann:ansible.im, 15:31:46)

  1. INFO: Created an issue to doc how to create tags: Document how to tag releases · Issue #1272 · ansible/ansible-documentation · GitHub (also tagged v2.15.11 and v2.14.16 last night) (@samccann:ansible.im, 15:31:51)
  2. INFO: Created an issue to doc how to create tags: [Document how to tag releases · Issue #1272 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/issues/1272) (also tagged v2.15.11 and v2.14.16 last night) (@samccann:ansible.im, 15:32:24)
  3. INFO: MUNI student writers are opening prs and can use reviews/assistance etc - https://github.com/ansible/ansible-documentation/pulls?q=is%3Apr+is%3Aopen+label%3A%22MUNI+tech+writers%22 (@samccann:ansible.im, 15:33:38)

4. TOPIC: SC rights in the docs repo (@samccann:ansible.im, 15:35:20)

  1. LINK: https://github.com/ansible/ansible-documentation/issues/1020 (@samccann:ansible.im, 15:35:27)

5. TOPIC: Open Floor (@samccann:ansible.im, 15:39:23)

  
  
Meeting ended at 2024-04-23 15:42:56  
  

### Action items

1. (none)

  
  

### People present (lines said)

1. @samccann:ansible.im (72)
2. @acozine:ansible.im (22)
3. @felixfontein:matrix.org (9)
4. @xnemeth3:matrix.org (2)
5. @ansibot:ansible.im (2)

  
  

Full logs: [full\_log.txt](https://forum.ansible.com/uploads/short-url/oA4yMWfmlQFc75joieEVgbDnN2o.txt)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [April 30, 2024, 3:43pm UTC](https://forum.ansible.com/t/meeting-log-ansible-docs-2024-04-23-1554/5094/2 "2024-04-30T15:43:36Z")

</div>

This topic was automatically closed after 7 days. New replies are no longer allowed.