User Tools

Site Tools


DIG Meeting Agenda and Minutes - December 7, 2023

This meeting will be held via videoconference beginning at 2 p.m. EDT/11 a.m. 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 discussions please sign up for the Evergreen Documentation Discussion List.

Connection Information:


  1. Remember to click "Record"!
  2. Introductions & Check-in
  3. Pet Show & Tell
  4. Collaboration/Updates:
    1. Hack-a-Way report
    2. Keyboard shortcuts documentation
    3. Update Antora
    4. Reports docs review
    5. New for 2024: Angular Staff Catalog documentation
    6. ?
  5. Other Business
    1. 2024: Technical writing student tackles Docs project(s)! (Report on 11/17 meeting)
    2. Docs build errors? (ABN)
  6. Holiday Social!
  7. Next meeting: Thursday, January 4 - ??
    1. Topic: TBD


  1. Introductions & Check-in
    1. 9 people in attendance
  2. Pet Show & Tell
    1. 5 pets were in attendance (including a new black cat!)
  3. Collaboration/Updates:
    1. Hack-a-Way report: Not much documentation stuff happened, other making the domain switch–then breaking the docs, briefly ;-)
    2. Andrea and Jane emptied queue of docs pull requests! Yay! Lots of first docs commits this year!
      1. Sitka has added to their docs. Bunch of new stuff with Angular navigation plus the keyboard shortcuts. The latter are also context-specific (per last UI meeting). Also getting to keyboard shortcuts is different in AngularJS and Angular.
      2. Still need to get something into community docs in 2024, then continue to update as get rid of more AngularJS and Dojo pages. (We're getting closer and closer!)
      1. On hold until people have time in 2024
      1. Susan did great review of reports docs!
      2. Lena wrote documentation for Angular Reports!
      3. Awesome screen shots from Beth!
      4. Action item (but no shame): Andrea will tackle any newer updates
  4. Other Business
    1. 2024: Technical writing student (Spencer!) tackles Docs project!
      1. Several of us met with Spencer 11/17/2023 to talk about possible docs projects for his master's project
      2. He's going to work on the stuff in the "New for 2024" doc above
      3. Starting in January, finishing in March
      4. His Advisor loved it, especially tackling the project in stages
      5. Equinox may have community server updated to 3.12 in early 2024
      6. Talked about new staff catalog features in 3.12 (not much–and Andrea already updated docs for "Additional Content" tab
    2. Docs build errors
      1. Hoping Blake or Jane would be present–not certain what's going on with build errors; weird stuff!
      2. New things not showing up in sidebar for previous versions, even though they're present in the files
      3. Git lesson from Andrea showing the things
      4. We were all confounded as to why they're not showing up
      5. Blake popped in: He'll take a look at it
      6. Blake discovered that the docs have been having trouble building since November 17–failing because it says it's running out of memory. Blake and Andrea will look into the date further to see if there was anything from around that date that could be causing it.
        1. Last docs commit before 11/16 was small one from Blake
        2. After that, next one was on 11/22
        3. Could be running out of memory after updating Main, but before finishing 3.11, etc., since it does one branch at a time
        1. "that was the day that we added rel_3_12 branch to the list of branches we're asking it to generate. That was apparently one too many, and it has exceeded the 2GB memory limit that Node.js imposes itself. I've edited the generation script to allow for 4GB memory instead, and it finished! So, the website now has all of the latest stuff."
        2. "A secondary issue: the non-main branches were not getting the latest documentation. This was due to a flaw in the documentation script. It wasn't running through all of the branches and pulling the latest git changes. I've introduced a chunk of code in that bash script that does that now.
          1. Any system admins that need to know more: when a new branch is introduced, we're going to need to reference it in the build script ~antora/run_docs…for branch in "rel_3_12" "rel_3_11" "rel_3_10" "rel_3_9" "rel_3_8" "rel_3_7" "rel_3_6" "main";"
    3. Older Evergreen docs–missing 3.5. Antora docs go 3.6+ and older docs only go up to 3.4
      1. It's there–we discovered a missing return carriage, which is why it's not showing up. Andrea can fix that (with "help" from one of her cats)–and does, live!
  5. Next meeting: Thursday, January 4
    1. Recap of things we pushed to 2024
    2. Conference things
    3. 3.12 docs scheduling
evergreen-docs/dig_meetings/20231207-agenda.txt · Last modified: 2024/01/03 17:26 by dluchenbill

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.