...
Bess: Looks like the other one Justin was working on.
Any other agenda items?
Ryan's work
Jen will start with Tom - will write up what they know about? How do we know this is successful? Jen: I have some familiairty with this topic. We can leave up to the expert to say we're done, or we can have the new developer work with the expert developer. Or get feedback from Documentation WG.
Bess: Less interested in knowing everthing about ACTOR stack, and more interested in accomplishing a specific task with ACTOR stack.
Goal is modify an actor.
Jen: Modify the ACTOR is one level of thoroughness. Modify ACTOR stack, might be a little tricky, do succesffully without breaking code completely.
Andrew: What is the most common interaction between developer customizing Smavera and the stack? Should I be modifying or adding to the Stack?
Andrew: Tom will tell you how do anything you want, but what is intended way to interact with the ACTOR stack?
Bess: What would you focus on?
Andrew: there to inject logic. To be expandable, so how do you add your own ACTORs to stack?
Bess: example?
Andrew: Isn't this where derivitavive generation and whatnot comes in? If you wanted to peel off a preservation copy
Bess: Add an actor that will atke a copy of my uploaded file and send it to S3. Actual accomplishing of that is crucial. Not necessarily S3. A directory. Concrete example to know how to inject something into an actor stack.
Jen: Lot of value to community.
Bess: Unless there's a different direction we're going in.
Jen: Get working code - how to do something. Something to accomplish that you'd want to accomplish.
Bess: Good its small. What is our citerion for success and what is question answered by the interview. Jen - your role - do the interview, but then someone can set up the actor stack that you just described.
Let's hold off on other things until we've had a retrospective until we've talked about what went well and what we can improve for next time.
Jen: The intention is to do it solo (answering Andrew's question). For now, we're doing simplest thing least intimidating to a new developer.
Bess: Let's talk to Tom on this first. Then Jen, can you report back?
Jen: That's fine. Should be straightforward to do pretty quickly. Not in one week, or today. Should be able to fit it into developers schedule.
If it works out he can do it, could possibly have something by next meeting.
Bess: If that works out, great.
Drew: I was going to offer - what is size of the interview?
Jen: Just fleshed it out. Just tell us a bit about where this pattern comes from, what is the intention of this code? Why add an actor intead of modfying one. What is the thing we want to get most commonly? Example: Put something on a differnet server from what's provided. Derivative and characterization.
Developer should be able to do something meaningful with this concept.
Bess: Provide criteria to keep focused.
Drew: So we'll take output and doc it up?
Jen: I'll make a Google Doc and share.
Bess: After that it's wordsmithing. Provide the right amount of context and structure.
Drew: A How To tutorial?
Bess: Yes. Credit interviewee.
Bess: Project tracking in a very small scale way. Create a ticket and get it on the board. (Ryan AI)
Jen: So this is going to be a how-to interview, we have some ways to do this.
Bess: Metainterview information. Here's how I prepared for the interview. What worked well. What didn't work as expected.
Drew: Any existing tutorials around ACTOR stack?
Jen: Tom did a modification a while back and had some good documentation?
Bess: Where is it?
Jen: It's in left-menu on Samvera GitHub - might be one of the intros. Might be it's own link. Also adding to Hyrax (a year ago?) Justin gave a good talk and there was documentation.
Bess: a slide show?
Jen: We have the slideshow and more than that.
Bess: Another criteria for success. If I wanted to look at ACTOR stack I wouldn't know where to go. A-Z has ACTOR stack for work.
Jen: This is not part of the interview process.
Bess; Right. Done criteria should include - when I go to the documentation site, I can find the ACTOR stack info. That's criteria for us turning this into public consumption.
Drew: Where are the tutorials?
LaRita: In New Start section, but all of them don't work. I created an issue for that at one point. Dive Deeper Into Samvera - http://samvera.github.io/what-happens-view.html has been put in, but doesn't function. All I get is http://samvera.github.io/deeper_samvera_index.html
Looks like 2 different places with slideshow.
Drew: Works for me.
LaRita: Not for me.
Bess: Just getting the title.
Drew: Just use the arow keys.
All: Oh! There it works. We need to document how this works.
LaRita: make a page in here that links to the slideshow - use your arrow keys to go through it. Make sure these are navigable and make sure they're up.
Drew: I'll make the tickets.
Finding ACTOR stuff.
Bess: Allright. We're at the end of this topic.
Drew: Want to make sure we're not duplicating effort.
Jen: Not in any danger of that. A new developer wants to interview on a topic. Could happen there's something there that's referred to.
Bess: What's here is better than nothing, but is not complete. There's a method but no stack mentioned in what's there.
Jen: There's good documentation in the code, but not available to new users as a how to. Where's more reading? etc...
Drew: Look for docs in English and then look to Ruby Docs as I want to dig deeper.
Jen: From framework of when people have have time, and need to learn good, concrete details.
Bess: About end of time and end of content.
AI: Jen's work and Ryan's project tracking.
Pick facilitators and note takers for next time.
Travis will atke notes next time. Drew can facilitate next time.