00:06:49 Maccabee Levine: Phil lives in a library! 00:07:01 Autumn Faulkner (she/her): I am all set to take notes if we don’t have other plans/volunteers 00:07:09 Caitlin Stewart: Reacted to "I am all set to take..." with ❀️ 00:07:11 Jenn Colt: Reacted to "I am all set to take..." with πŸ₯³ 00:07:28 Peter Murray: Reacted to "Phil lives in a libr..." with ❀️ 00:07:55 Tom Cramer: https://docs.google.com/presentation/d/1FQwm9Ewgc5vs5FJQYAdhLOudSgwBnR7j7l4Fduf9LBY/edit?slide=id.p2#slide=id.p2 00:08:34 Caitlin Stewart: I'm happy to share 00:12:53 Maccabee Levine: Olamide, Kevin and Peter as well! 00:13:02 Day, Kevin: Reacted to "Olamide, Kevin and P..." with πŸ‘ 00:13:08 Huff, Jeremy T: Reacted to "Olamide, Kevin and P..." with πŸ™Œ 00:14:17 Lisa McColl: Reacted to "Olamide, Kevin and P..." with πŸ™Œ 00:20:14 Tod Olson: Not meeting has been largely due to constraints on my end. 00:23:10 Caitlin Stewart: Replying to "Not meeting has been..." it's mutual Tod! 00:31:21 Jennifer Eustis: Sounds great, thanks Autumn 00:32:08 Caitlin Stewart: @Autumn Faulkner (she/her) I took some notes while you were talking if they are useful: addressing a shortfall in coordination with RMS by getting more engaged with release ensure that regular Library workers who are not super involved in Slack can get updates that are free, accurate, and easy to understand Coordinating with POs who have been piloting a new process to create functional release notes Another goal is for PC to understand and communicate current state of operations for releases aiming for May-June timeline 00:33:11 Tom Cramer: Hi Jeremy! I hear you have openings next week. Can we meet? :) 00:33:26 Charlotte Whitt: Reacted to "Hi Jeremy! I hear yo..." with πŸ˜‚ 00:33:35 Autumn Faulkner (she/her): Reacted to "@Autumn Faulkner (sh..." with πŸ™ 00:34:38 Huff, Jeremy T: Reacted to "Hi Jeremy! I hear yo..." with πŸ˜‚ 00:47:33 Kristin Martin: Which libraries are you referring to with the large development resources? 00:47:41 Jenn Colt: Hard to argue libraries are in a good position right now 00:48:00 Thomas Trutt: Cornell was part of that group before go-live. 00:48:07 Thomas Trutt: Reacted to "Hard to argue librar..." with πŸ’― 00:48:07 Tom Cramer: Reacted to "Which libraries are ..." with πŸ˜‚ 00:48:08 Charlotte Whitt: I can help with that :-D … the biggest issue was several developers being head hunted to work for EBSCO 00:48:42 Kristin Martin: There was a grant. 00:49:01 Caitlin Stewart: I can't find my raise hand button while screen sharing but I have a question 00:49:11 Tom Cramer: want to drop the share? 00:49:28 Caitlin Stewart: Brilliant, Tom, thanks. 00:49:30 Tom Cramer: thank you Caitlin for driving the slides! 00:52:46 Caitlin Stewart: huge legal and administrative overhead to think about with contracting 00:52:57 Tom Cramer: Reacted to "huge legal and admin..." with πŸ‘ 00:53:18 Tod Olson: Reacted to "huge legal and admin..." with πŸ‘ 00:53:26 Thomas Trutt: Reacted to "huge legal and admin..." with πŸ‘ 00:53:51 Charlotte Whitt: +1 Kristin 00:54:50 Tom Cramer: one area the community could step up is apply more funds to AWS, devOps, QA, release management. It’s towards the end of the software dev lifecycle, but is all β€œcritical community operations” that arguably should be borne by the community as a whole 00:55:12 hkaplanian: Reacted to "one area the communi..." with πŸ‘ 00:55:22 hkaplanian: Reacted to "huge legal and admin..." with πŸ‘ 00:56:54 Autumn Faulkner (she/her): Reacted to "one area the communi..." with πŸ‘ 00:56:57 Christopher Spalding (EBSCO): Just want to note that the conversation on pass-through on an opt-in basis is still alive, but is requiring a number of internal conversations as it has tax and reporting implications that we had not realized. We continue to discuss, but the approach would be an opt-in option and not a provider tax. 00:57:32 Tod Olson: Reacted to "Just want to note th..." with βœ”οΈ 00:57:56 Huff, Jeremy T: Reacted to "Just want to note th..." with πŸ™Œ 00:58:06 Peter Murray: The ArchiveSpace project made a fascinating decision to put the source code in the open and the application documentation behind a pay-wall. A library has to become a member of the ArchivesSpace organization to get to the documentation. There was an outcry at the time, but it seems to have worked for them. 00:58:35 Tom Cramer: Reacted to "The ArchiveSpace pro..." with πŸ‘ 00:58:50 Jenn Colt: Reacted to "The ArchiveSpace pro..." with πŸ‘ 00:59:18 Jenn Colt: Replying to "The ArchiveSpace pro..." This would let us put greater value ourselves on our docs too which would probably be welcome 00:59:20 Autumn Faulkner (she/her): Reacted to "The ArchiveSpace pro..." with πŸ‘€ 00:59:32 Tom Cramer: Replying to "The ArchiveSpace pro..." I remain optimistic β€” perhaps uniquely so β€” that FOLIO could do something similar, especially with the docs and access to members’ expertise 00:59:36 Tom Cramer: Reacted to "This would let us pu..." with πŸ‘ 00:59:51 Tom Cramer: Reacted to "Just want to note th..." with βœ”οΈ 01:01:15 Autumn Faulkner (she/her): Replying to "The ArchiveSpace pro..." I love this approach. Truly good documentation comes at a significant cost β€” time, maintenance, etc. Perhaps a tiered approach would make sense? Basic member access would include documentation, then a more premium membership level could include newsletters, perhaps more in-depth instructional content? 01:01:35 Caitlin Stewart: Replying to "The ArchiveSpace pro..." Lots of intersections with the work we discussed today 01:02:00 Shelley Doljack: bye