11:00 AM EST at https://cornell.zoom.us/j/703126880
- Andrew Myers (WGBH)
- Lynette Rayle (Cornell)
- LaRita Robinson (Notre Dame)
- Ryan Steans (Avalon/ NU)
- Jennifer Lindner (DCE)
Agenda / Notes:
- Roll call (please log in above)
- Review last week's action items:
- Jen: Will contact Tom Johnson regarding potential email interview
Jen: Will craft email interview based on how to perform a task - adding actors (demo how it works when you add an actor)
Drew: Make sure all documentation on Jekyll page is findable, navigable to Actor components
Ryan: Will add Jen's project steps to the Board
- 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:
- (add your items here)
- 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.
Jen - Got in touch with Tom Johnson, he did commit to completing interview questions. Two weeks ago, so as a follow up, can post what those questions look like. Do an example that's relevant and timely. S3 or other relevant topic. Can you give me a rough interview of how to interact with the system at a high level. Don't modify actor, you make a new actor. How do I do what I want to do?
Should I post this to project files?
Drew: yes, on splash page, there's usually something.
Lynette: Was there an issue in Github that it's associated with? Also - Tom is in grad school right now, so maybe he's in exams. Maybe next week is better?
Jen: Is there a place for the pilot program thing? No representation in Samvera Githib repo. Basically - make one issue in GitHub. Tag Ryan Steans on it.
Lynette: Page in Wiki from last effort in Wiki - so not sure you want to hang something off there. Can point from Wiki to GitHub, process of five interviews and interview types. I'll post Wiki page (where we defined what we were going to do) to Slack. It lists five approaches, topics, so we can link to GitHub issues for each one.
Drew; This is work, so it'd be great so we could move the ticket to the "In process" column.
Lynette: Yeah, let's link to GitHub issue.
Drew: make sure all documentation on Jekyll page is findable from components. I just cut and pasted from last meeting notes. I thought I was turning tutorials into front-page items. One of the original dive-into tutorials is one page. It was a slide-show. Slide about actor stack wasn't useful from tutorial, however we did throw in action item to make tutorials more useful. Not sure who did that. Second tutorial is still a slide-show, but I don't think you can link to individual pages. Nothing worked. Too js'y to work. That is still on the backlog, and is a ticket.
I was having issues adding tickets to projects. Anyone more successful?
My add button is greyed out.
Jen - you have to just drag it over. Your add button is greyed out?
Drew - I found a different way to do it, and it works. Moving it down the backlog.
Lynette: Create another project for the pilot we're doing so we can add the work to the project. Surprised to hear the slide show is working. Was there a card associated with those demos?
LaRita: I had issues getting the links to work but arrows working now. Maybe something changed in Chrome.
Drew: I think if you try to go to a hash URL, it doesn't work. We should break it out into one big page.
Lynette: I think under the hood it is one big page - in new documentation, more info on ACTOR stack, that has some information about ACTOR stack and how it functions in the bigger scheme of things.
Drew: is it tagged as Actor? It's a term that gets thrown around a lot. We should target