This meeting will be held on the #evergreen channel on the Freenode IRC network (http://evergreen-ils.org/irc.php) beginning at 2pm EDT/ 11am PDT. Current and future DIG participants are encouraged to attend, and any interested members of the Evergreen Community are welcome as well. For updates, notifications, and discussion please sign up for the Evergreen Documentation Discussion List.
Introductions: paste "#info <username> is <name> <affiliation>" to identify who you are and what organization, if any, you represent
Helpful Information: Documentation contributions and collaboration
-
-
Old and Ongoing Business:
Check-in - How is everyone doing?
Previous Action Items (see below)
Antora progress
Meta data "Untitled" pages still exist
Should the server-side generation script(s) be in the EG repo?
Keeping our branch in sync with master docs/* (looks like manual only) - Jane did this:
commit 7b21150d322
handling RELEASE NOTES in Antora - new module?
Looks like we missed 3.5
In order to get this merged to master - should we create some sort of roadmap?
site.yml probably needs to change to mention all of the Antora-ized AKA branches: branches: [vmaster, vrel_3_5]
Antora site.yml
Antora will need each branch to have a corresponding "version" English word in antora.yml -> version: 'latest'
Should that somehow be baked into the make-release process for buildmasters?
3.5 documentation work
Experimental catalog documentation work
New Business:
Evergreen International Online Conference!
June Meeting
Collaboration time
sandbergja will make a video for proof of concept in the Quick Starts section
everyone will review all of the docs on Antora, looking for broken things and other fixes needed and report on Launchpad
DIG will work on 3.5 documentation during Bug Squashing Week, March 16-20
bmagic will think about and explore how to query our git repo to see if there are any non-merged branches that touch /doc/* files
Note:
At the May 2018 Documentation Interest Group meeting in person at the Evergreen conference 2018 in St. Charles, Missouri, it was agreed that DIG meetings would alternate each month between meetings that were half agenda, half collaboration in one month and a full meeting length of working on the documentation in the other month.