Child pages
  • 2018-11-27 Meeting Agenda and Notes
Skip to end of metadata
Go to start of metadata


 Click for additional ways to connect...

Topic: Samvera Documentation WG
Time: this is a recurring meeting Meet anytime

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap (US Toll):  +14086380968,703126880# or +16465588656,703126880#

Or Telephone:
    Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
    Meeting ID: 703 126 880
    International numbers available:

Or an H.323/SIP room system:
    H.323: (US West) (US East) (China) (India) (EMEA) (Australia) (Hong Kong)
    Meeting ID: 703 126 880


Or Skype for Business (Lync):

Facilitator: Andrew Myers


Attendees (please log 

Agenda / Notes:

  1. Add additional agenda items if needed.
  2. PR review and merge:
      1. after looking at this locally, it looked a little funky because of it's size and the background it was on, so we made it bigger, change the background of the header, and adjusted styles to look good with the new white background.
      2. Johannes Frenzel came back with a requested change that Andrew Myers will follow up on.
    2. (merged, thanks Chris Diaz)
  3. Discussed the future of this WG for a bit.
    1. There isn't much energy in it anymore, but plenty of work remains.
    2. Nobody seems to have cycles to devote outside of the meetings
    3. Turning the meetings into bi-weekly hour-long work sessions seems to be the most productive thing we can do until a more concerted effort put forward.

Action Items (carried over from last week)

  • Cross linking - Call out external sources of documentation, with a brief descriptions of what they're talking about.
    • Hyrax Github Wiki,,, Hyku Github Wiki
    • For each external source, spend 1/2 hour or so, to identify a good spot for a link back
    • Contact person who manages external documentation source, and ask them to put the link.
  • Categorize all pages under the following:
    1. Community
    2. Users
    3. Developers
    4. Admins
    • At the next meeting, we see how well those categories are suited, if we need different categories
    • The purpose of the top-level categories is to better define the information architecture of the site.
    • We want to identify audience (e.g. Developers) and/or process (e.g. Testing)
    • Structurally, the home page will be replaced by a more modernized page displaying the top-level categories, and maybe a brief description of each.