# Meeting Log | Ansible Docs | 2024-03-19 16:01:28

**URL:** <https://forum.ansible.com/t/meeting-log-ansible-docs-2024-03-19-1628/4459>\
**Category:** MeetingBot Logs\
**Tags:** documentation\
**Created:** [March 19, 2024, 5:02pm UTC](https://forum.ansible.com/t/meeting-log-ansible-docs-2024-03-19-1628/4459 "2024-03-19T17:02:52Z")\
**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:** [March 19, 2024, 5:02pm UTC](https://forum.ansible.com/t/meeting-log-ansible-docs-2024-03-19-1628/4459/1 "2024-03-19T17:02:52Z")

</div>

# DaWGs aka Documentation Working group | Ansible Docs | #docs:ansible.com
Meeting started by @samccann:ansible.im at 2024-03-19 16:01:28  
  

### Meeting summary

1. TOPIC: Documentation Updates (@samccann:ansible.im, 16:04:10)

  1. LINK: https://github.com/ansible/ansible-documentation/pull/1209 (@orandon:ansible.im, 16:08:06)
  2. 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)
  3. 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)
  4. INFO: here's a screengrab of the project schedule: (@orandon:ansible.im, 16:37:30)
  5. 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)
  6. 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)
  7. 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)
  8. INFO: For example, `./tag.py --remote upstream tag` if the upstream repo is the `upstream` remote (@gotmax:matrix.org, 16:54:16)

2. TOPIC: open floor (@samccann:ansible.im, 16:55:12)

  1. LINK: http://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

1. (none)

  
  

### People present (lines said)

1. @orandon:ansible.im (41)
2. @samccann:ansible.im (40)
3. @utoddl:matrix.org (14)
4. @gotmax:matrix.org (8)
5. @deric.crago:ansible.im (4)
6. @sutapa\_b:matrix.org (2)
7. @ansibot:ansible.im (2)

  
  

Full logs: [full\_log.txt](https://forum.ansible.com/uploads/short-url/3Hk6l95LY7Nk9xs4u5lFmLiZKB2.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:** [March 26, 2024, 5:03pm UTC](https://forum.ansible.com/t/meeting-log-ansible-docs-2024-03-19-1628/4459/2 "2024-03-26T17:03:43Z")

</div>

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