-
Notifications
You must be signed in to change notification settings - Fork 144
DaWGs (Documentation Working Group) Meeting Agenda 2021 #579
Comments
2021-01-05long-running issues from
do we or don't we adopt semantic markup
open floor
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-01-05/docs_working_group_aka_dawgs.2021-01-05-16.00.html |
Contributing to Ansible DocumentationEasy Places you can help!
Less easy but need developer help on:
interesting links
|
2021-01-07status update
what must we accomplish by Feb 2 and what can we push off to a later
new repo for new community guides etc
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-01-07/documentation_working_group_supplemental_meeting.2021-01-07-15.31.html notes on brainstorming sessionhttps://hackmd.io/x0VwaKSYQCaHGJR4LelSEw?view *dev guide *- people will need 2.10 info, some devel info, some will need both. this is a case that either a unified dev guide that includes the differences between older versions and newer versions or an index page with the different versions of various documents would attempt to solve.
|
2021-01-12role argspec update
template for collection
|
|
|
2021-01-26Docsite Split Update
documenting use of
|
|
2021-02-02Index pages for the Core/Package Docsite Split
backports status
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-02-02/docs_working_group_aka_dawgs.2021-02-02-16.01.html |
2021-02-09opening chatternew landing pages!docsite split update
open floor
LogsMinutes: https://meetbot-raw.fedoraproject.org/ansible-docs/2021-02-09/docs_working_group_aka_dawgs.2021-02-09-16.00.html |
2021-02-16Ansible 3 release and docsite split
future of
|
|
2021-02-23documentation for filter and test plugins
semantic markup proposalopen floor
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-02-23/docs_working_group_aka_dawgs.2021-02-23-16.01.html |
2021-03-02
|
In today's community meeting (#539 (comment)), we decided that /devel/ should not include pre-releases of collections. That saves the DaWGs meeting from also discussing that ;-) |
|
2021-03-16collection /docs/ folder usage
open floorLogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-03-16/docs_working_group_aka_dawgs.2021-03-16-16.02.html |
|
I'm double booked this week, so I am posting a little information early in case I'm not watching the meeting when it's discussed
I can make a meeting 30 minutes to one hour earlier (until Daylight Saving Time shifts again :-)
Does this option and implementation look like what we want? https://hackmd.io/E5a0dw0tTDCteQVVk4VvJw?both#Development-of-ansible-core-and-latest-of-collections
It would be great if we can have input on what the structure of this looks like. One of the problems that I found with the current plugin doc data structures is that the names don't follow any common standards. I've addressed that in antsibull-docs by writing a schema which normalizes all of the names prior to giving the data to the rest of the program but it would be better if these were standardized in the specification. |
possible RST table for new module attributes are being discussed at - ansible/ansible#75164 (comment) Tracking issue of all the things we need to get done by core-2.12 release - ansible/ansible#75664 |
2021-09-21opening chatter
core-2.12 docs needs
New module attributes
ssh doc problem
expand/collapse in sphinx
Open FloorActions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-09-21/documentation_working_group_aka_dawgs.2021-09-21-15.00.html |
2021-10-12Updates on ongoing work
Actions
LogsMinutes: https://meetbot-raw.fedoraproject.org/ansible-docs/2021-10-12/documentation_working_group_aka_dawgs.2021-10-12-15.00.html |
2021-10-26Action Item review
shaded borders on plugin tables
Meeting time change for Daylight Savings
PR76088Should devel docs use the interim branches of devel?
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-10-26/documentation_working_group_aka_dawgs.2021-10-26-15.00.html |
2021-11-09Action Item review
docs survey issues
reviving semantic markup
community-contributed examples
Open Floor
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-11-09/documentation_working_group_aka_dawgs.2021-11-09-16.01.html |
2021-11-16Action Item Review
Docs survey feedback
Semantic Markup
Community-contributed examples
Ansible 5 prep
Open Floor
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-11-16/documentation_working_group_aka_dawgs.2021-11-16-16.08.html |
|
2021-11-30Action Item Review
setting docs priorities for 2022
semantic markup
responsive plugin tables
Actions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-11-30/documentation_working_group_aka_dawgs.2021-11-30-16.00.html |
2021-12-07Action Item Review
Responsive parameter tables
semantic markup
docs vs docs-tooling and attracting more contributors
Open FloorActions
LogsMinutes: https://meetbot.fedoraproject.org/ansible-docs/2021-12-07/documentation_working_group_aka_dawgs.2021-12-07-16.02.html |
Closing this issue. Please add agenda items to the new 2022 issue - #643 |
Closing this issue. Please add agenda items to the new 2022 issue - #643
This tracks the DaWGs (Documentation Working Group )meetings for Ansible docs, starting from Jan. 2021.
This team uses the following GitHub tracking boards:
If you have a question, comment, idea, or anything else to discuss, please leave a comment here to add it to the agenda for our next meeting. If you don't show up for the meeting, your item will probably be skipped.
If your IRC nick is different from your Github username, leave that as well.
See https://github.com/ansible/community/blob/master/meetings/README.md for the schedule.
Once an item has been addressed please edit the text to make it strike-through style (two tildes ~~ on either side of the text) or check the checkbox if available.
When creating new agenda ensure docs and meeting_agenda labels are set.
Join us anytime in #ansible-docs on libera IRC!
See #521 for 2020 minutes and #389 for prior meeting minutes.
The text was updated successfully, but these errors were encountered: