11:00 AM EST at https://cornell.zoom.us/j/703126880
Topic: Samvera Documentation WG
Time: this is a recurring meeting Meet anytime
Join from PC, Mac, Linux, iOS or Android: https://cornell.zoom.us/j/703126880
Or iPhone one-tap (US Toll): +14086380968,703126880# or +16465588656,703126880#
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 703 126 880
International numbers available: https://cornell.zoom.us/zoomconference?m=kETmSkQJwRw5MtUhdEDgGzCl7yPcJrhY
Or an H.323/SIP room system:
18.104.22.168 (US West)
22.214.171.124 (US East)
126.96.36.199 (Hong Kong)
Meeting ID: 703 126 880
Or Skype for Business (Lync):
Facilitator: Jennifer Lindner
Notetaker: Ryan Steans
- Lynette Rayle (Cornell)
- Ryan Steans (Avalon)
- LaRita Robinson (Notre Dame)
- Jennifer Lindner (DCE)
- Bess Sadler (DCE)
Agenda / Notes:
- Roll call (please log in above)
- Review project board: https://github.com/projecthydra/projecthydra.github.io/projects/1
- Reporting on items completed since last meeting
- Review status of in-process tickets
- Discuss ready items & groom backlog
- Any new items needed?
- What should be moved to ready?
- Other agenda:
- Update on technical writer consultation
- Glossary - ready to go? https://github.com/samvera/samvera.github.io/pull/192
- Pick facilitator / notetaker for next time
- Notetaker is responsible to copy template agenda into a new agenda for next meeting and add any followup items immediately.
- Discussion re: project board items
- Other discussion
- Facilitator & Notetaker for next meeting
Ryan make Template for notes for next meeting (add Ruth)
Jen will ping the channel when she's ready. She will make a ticket for the work
Larita will update the ticket to reflect the work done and what's going on with Jekyll work
LaRita working on issues on the board - how to do PR's (there was a PR for it).
"How to submit a PR" is in done column - 198 - needed to be added to new cards. Needs to be merged in.
Jen - leave it as issue whether to go further with it. Lynette - good to use, could add to the template - actual checkboxes for PRs. Pretty long, but may be useful. Template that's for the issue - use all of it - PR is different.
LaRita suggests suggests to templatize a link to the "How to submit a PR" -
Lynette just merged it.
Jen: NavTab stuff.
LaRita - NavTab stuff - issues - using Include and Tabs/ frontmatter to generate however many tabs needed - the problem with how Frontmatter read it. The biggest problem was how it autogenerates a table of contents. Drew looking at a quick plugin to handle the front matter. Not sustainable as is. Work looking at other templates - none had been updated in a while, so we did not switch templates as nothing was as new as what we're doing.
Jen: AI: Can we update the ticket to reflect the work done and what's going on.
LaRita: Make frontmatter fo eachp page only knows its own version - would get rid of depth of what it needs to know. Drew knows the Ruby Plug-in, file structure for each filename. Will determine how its built into the version in tabs.
Autobuilding does not pick up table of contents from included. Hopefully next week or two Drew can work on this.
Jen: Documentation best practices.
Lynette: as I have time, I'm looking at. Not active.
Jen: Connecting to Shib. Bess: Haven't had time to work on that.
Jen: DOn't merge the PR because it's the transcibred interview. Update! Tried talking to Tia who has experience and passion for documenting API's. No response. Got in touch with other person - Masters in writing, etc... 4 hour consultation, transcribe interview.
But it worked and Jen will have something for the group in short order. DIdn't get down from Giarlo quite what he meant in a few places - so we may need to go back. So, we need to think about how many revisions we can do.
AI: Jen will ping the channel when she's ready. She will make a ticket for the work.
Glossary - Lynette - run by Julie to see if she has any comments. Combining of info in several different places. Glossary itself will probably have to be versioned. May shift over time - but versioning hopefully won't be an issue.
Start by checking in with Julie to see if she likes what we have, and then we can merge it.
Get an issue created to make sure everything is tied to a release version. Point to a Master or a release version. Update links when we merge.