Date
11:00 AM EST at https://cornell.zoom.us/j/703126880
Facilitator: Andrew Myers
Notetaker: rsteans
Attendees
Agenda / Notes:
- Roll call (please log in above)
- Review project board: https://github.com/projecthydra/projecthydra.github.io/projects/1
- Review outstanding PRs
- 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:
- HTML Proofer... got it down to only 165 failures!
- Explore them? Fix them? Punt?
- Can someone remind me whether samvera.github.io is for all of Samvera products, or just Hyrax?
- thoughts on a product-centric (and thus, a version-centric) organizational structure?
- Other documentation efforts
- What is our strategy for coordination?
- Do we need to be more vocal?
- Blog?
- HTML Proofer... got it down to only 165 failures!
- 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.
Notes:
- Discussion re: project board items
Do some reviewing
Get things off PR list and pushed
Specifically - Lynette's Glossary - Already approved - feedback from JulieRudder - if no changes, can we push? Consolidating terms into a usable glossary - Decision: MERGED
Oldest one - Amending Documentation - subtracting an unordered list presumably to remove something no longer relevant - issue on Hyrax for that - It may be that LaRita needs to pick it up, HyRax issue tagged to this - Documentation is fine - update documentation and then tag the issue on it. Will fix the issue and then update the documentation (push).
PR 166 - Minor and version specific (Jen) - Hyrax server chatter about notification, make sure this is version specific (it is now). Where you can set notification update. Minor, but nice for anyone using Hyrax 1 as there's so much chatter. - Does not have new stuff in it - front matter to specify the version - line that this only applies to 1.0. AI: Drew will work on this offline.
ReadMe has reference on how to add versioning
184 - haven't looked at it in a bit. Added editor's chages. ACTOR stack is complicated. Jen is taking a look at it - not where we'd want it to be. Need to update it with the Tech Writer's stuff.
Justin has provided some description of the Actor Stack -
QUESTION: Should we frame our Interviews as a Blog Post? Jen considering it - the interview itself - how do you control flow when in stack? Why would you want to use a transaction? when in process of saving work and do derivatives - didn't quite get it. Material just wasn't quite there. Original interview. Decent enough, better than nothing. Could get ahold of an Actor Stack person to finish it out.
Put a place in Documentation for Blog posts? More conversational - short and specific. "This is what happens, in steps". As a developer, if I want to jump in and bebug and fix, this is very helpful.
218 - PR last night Spec to site so that when you run R-Spec, pushes Jekyll to basically run an R-Spec as if in rack. Bess merged it. Hadn't tied it into Travis at all, so there are a few things - set up a default rake, changes to format, format styler. Clean-up in this PR, inside of Travis config an exclude directive, errant ruby files,
Take a look at that - bumped ruby to .2.4.6 and 2.5.0 test against latest minor releases
Inside of spec helper - moved where HTML proofer was running - now built inside of spec helper. HTML link checker, was commented out - still commented out.
3 outstanindg PR's with 2 where we know why its held
- Other discussion
- Facilitator & Notetaker for next meeting
- Facilitator:
- Notetaker: