15:00:01 #startmeeting 2023-09-12 - Developer Meeting 15:00:01 Meeting started Tue Sep 12 15:00:01 2023 US/Eastern. The chair is Bmagic. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:01 The meeting name has been set to '2023_09_12___developer_meeting' 15:00:13 #info Agenda at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2023-09-12 15:00:20 #topic Introductions 15:00:22 #info Dyrcona = Jason Stephenson, CW MARS 15:00:24 #info Bmagic = Blake GH, MOBIUS 15:00:40 #info berick Bill Erickson, KCLS 15:00:44 #info shulabear = Shula Link, GCHR in PINES 15:00:52 #info jeffdavis = Jeff Davis, BC Libraries Cooperative (Sitka) 15:00:54 #info abneiman = Andrea Buntz Neiman, EOLI 15:00:55 #info collum = Garry Collum, KCPL 15:00:57 #info eeevil = Mike Rylander, EOLI 15:01:02 #info sleary = Stephanie Leary, EOLI 15:01:14 #info jeff = Jeff Godin, Traverse Area District Library (TADL) 15:01:17 #info JBoyer = Jason Boyer, EOLI 15:01:45 feel free to continue the introductions as you arrive 15:01:48 #topic Action Items from Last Meeting 15:01:51 #info Stompro = Josh Stompro LARL/NWRL 15:01:59 #info mmorgan will explore moving LP stats to community site and automating same 15:02:07 I may not be able to be present/attentive for the entire meeting, but my two action items remain outstanding, as in, I still need to complete them. :-) 15:02:25 jeff: noted 15:02:30 #infor mmorgan = Michele Morgan, NOBLE 15:02:42 mmorgan: any update on that? 15:02:52 Just a quick update on my action item. I'm exploring the Launchpad api 15:03:22 cool, we'll carry it forward 15:03:29 #info berick will make tutorial: "How grid cell templates work" 15:03:56 done and one, but .. 15:04:08 i need some guidance/assistance on getting them into the right shape 15:04:15 i posted them onto https://wiki.evergreen-ils.org/doku.php?id=newdevs:tutorials-wanted 15:04:20 #info terranm = Terran McCanna, PINES 15:05:03 berick++ 15:05:13 berick++ 15:05:28 would that be sleary as a "shaper" ? 15:05:37 berick++ 15:05:53 Well, it's a wiki. It could be anyone with credentials as a shaper. 15:06:03 * sleary will take a look 15:06:10 #info briank = Brian Kennedy, BCLC (Sitka) 15:06:49 #action jeff will make tutorial: "Add missing field to print template" 15:06:56 #action jeff will write tutorial "Retrieve a user's setting and do something based on its value" 15:07:05 #action mmorgan will explore moving LP stats to community site and automating same 15:07:28 thanks sleary. let me know what I can do. 15:07:42 Any more discussion on shaping the markdown -> dokuwiki? 15:07:55 berick thanks for working on these; I appreciate it! 15:08:12 berick++ 15:08:46 #info sandbergja will write tutorial: "Do a database call (Galen’s cat counter)" 15:09:27 sandbergja is probably afk 15:09:44 #info Bmagic will send a call for volunteers to the dev list 15:09:52 that's done 15:09:53 not sure if sandbergja is around, but she left me a note to review her work in progress, so it's... in progress! 15:10:04 sandbergja++ 15:10:18 sleary++ 15:10:27 I'll carry that action forward 15:10:35 #action sandbergja will write tutorial: "Do a database call (Galen’s cat counter)" 15:10:43 sleary++ 15:11:09 #topic Evergreen - Fall release planning / release team 15:11:29 Too late.... 15:12:15 #info Evergreen 3.12 Release Team meeting Friday at 2pm ET - ping abneiman for more info 15:12:32 some to the meeting yall! 15:12:32 we'll be putting together a schedule & roadmap etc 15:12:56 sandbergja++ collum++ rfrasur++ mmorgan++ terranm++ # dream team 15:13:06 abneiman++ 15:13:10 sandbergja++ collum++ rfrasur++ mmorgan++ terranm++ # fo sho 15:13:12 #info rfrasur = Ruth Frasur, EGIN / ECDI 15:13:17 abneiman++ 15:13:44 (I accidentally found myself on the team) 15:13:49 abneiman++ 15:13:55 so start thinking about those roadmap entries! that's all I got for now 15:13:57 abneiman++ 15:13:58 rfrasur: classic you 15:14:11 heh, rfrasur, I accidentally found myself leading the team sooooo let's go 15:14:51 Bmagic - too true. abneiman - twinsies!! (the internet can't smell my fear) 15:14:53 abneiman I will try to listen in, at least... time permitting -.- 15:15:01 It's more people than I've seen on a release team. Might be the* most 15:15:17 If anyone would like to knock any of the staffcatalogblocker bugs out, it'd be great to be able to get closer to getting rid of the old version - https://bugs.launchpad.net/evergreen/?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3A 15:15:18 list=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=staffcatalogblocker&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes 15:15:18 =on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search 15:15:25 by our powers combined 15:15:51 that is a URL if I've ever seen one 15:16:10 dangit Launchpad 15:16:19 love Launchpad URLs, they're the bestest 15:16:59 They're extra 15:18:02 I'm going to make a pitstop at documentation 15:18:06 #topic Documentation 15:18:25 Would anyone like to mention a doc related thing? 15:19:19 dluch couldn't be here but she thought those that were at the last meeting might throw in some info 15:19:22 with many thanks to Sitka, DIG is getting ready to do a big Reports docs update this week 15:19:37 please say git prayers for me. 15:20:15 an incomplete list of helpers on that long project is here: DIG (reviewing), Jennifer Pringle (writing), Susan Morrison (editing), Beth Willis (screenshots), Andrea Buntz Neiman (editing), Elizabeth Davis (editing) 15:21:10 and our fearless leader dluch++ 15:21:14 for keeping the dream alive 15:21:21 abneiman: your concern about the presentation of large (wide) tables on the Evergreen documentation pages is something I looked at for awhile. I think the best answer is to not use tables, but instead format the data as a bulleted list maybe? 15:22:14 abneiman++ dluch++ dig++ 15:22:22 We can talk about it outside of this meeting 15:22:30 Bmagic: thanks for looking. In the case of the table in question, for Global Flags, I'm not sure bulleted lists is really an adequate substitute. But I'll keep poking. 15:22:39 abneiman++ dluch++ dig++ 15:22:57 #topic Launchpad Status (as of noon Eastern) 15:23:03 #info Open Bugs - 3023 15:23:09 #info Pullrequests - 91 15:23:12 #info Signedoff - 19 15:23:32 #topic Launchpad Status since last meeting 15:23:35 #info Bugs Added - 69 15:23:37 #info Pullrequest tag Added - 43 15:23:40 #info Signedoff tag Added - 34 15:23:42 #info Fix Committed - 32 15:23:51 mmorgan++ 15:24:11 we're flying through this meeting 15:24:23 but we might spend some time on this one 15:24:27 #topic New Business - LP#2032835: Should we merge OpenSRF into Evergreen? 15:24:34 Yes. 15:24:44 lol 15:24:56 <-- thinks the same: Yes. 15:25:24 I think it would make sense to wait for Redis to replace Ejabberd however. 15:25:33 i opened the LP after working bug 2017941, where i was reminded of the complexity of managing 2 separate projects. 15:25:33 Launchpad bug 2017941 in OpenSRF "Migrate from Ejabberd to Redis for OpenSRF Messaging" [Wishlist,Confirmed] https://launchpad.net/bugs/2017941 15:26:09 and really just started wondering if it was worth it to keep the separated. 15:26:38 Should this be added as a topic for the hackaway? 15:26:38 +1 to combining them. 15:27:02 +1 to combining 15:27:06 Yes, it could be done during the hack-away, maybe, or at least started. 15:27:20 rfrasur: you don't think we can just take care of this problem here and now. I have the merge button right here. 15:27:25 heh 15:27:31 +1 to combining 15:27:37 is anyone opposed to the idea? 15:27:51 Are there any potential downsides to merging? 15:28:02 lol, I mean...if you have the button, push it. Otherwise...I'll add to the hackaway discussion list 15:28:12 This is something I've heard talked about before. And I'm a little foggy about what some of the talking points were. 15:28:12 #info kmlussier is Kathy Lussier, NOBLE 15:28:42 kmlussier: potentially smearing the lines more between front and back ends, but we're basically building sql in the UI, so I don't think it makes much difference. 15:28:59 kmlussier: one downside, a big change to one (e.g. adding redis suspport) means the other has to wait. 15:29:00 kmlussier: Not really. We're the only project that uses OpenSRF as far as I've been able to find. 15:29:11 Though I also like the idea of waiting until OpenSRF is talking over Redis. 15:29:13 however that example (redis) is pretty darn rare 15:29:30 agreed post-Redis make more sense 15:29:37 berick++ jboyer++ 15:29:58 berick++ 15:29:59 OK, I'm convinced. I may have already been convinced before I asked the question. 15:30:13 if there's consensus here, might make sense to send a heads-up message to the dev and general lists for broader feedback? 15:30:44 +1 to combining 15:30:48 jeffdavis: Do I hear you volunteering for an action item? 15:30:51 +1 to sending that message 15:30:57 sure, berick: would you like to compose the email? 15:30:57 lol what have I done 15:31:08 Probably a good idea either way, I think if there's more discussion to be had it'll more likely be via email than LP comments 15:31:25 yes i can email 15:31:28 ("good idea" -> emailing) 15:31:33 berick++ 15:31:41 #action berick will post something to the email list about merging OpenSRF into Evergreen 15:31:55 berick++ 15:31:56 #info https://bugs.launchpad.net/opensrf/+bug/2032835 15:31:56 Launchpad bug 2032835 in OpenSRF "Discussion: Merge OpenSRF Into Evergreen?" [Wishlist,New] 15:32:15 * rfrasur has added it to hackaway lineup too. 15:32:25 I don't remember if / how it changes the appearance in the minutes, but there is also #link 15:32:35 oh 15:32:48 thanks rfrasur. there will be plenty yet to discuss 15:32:51 #link https://bugs.launchpad.net/opensrf/+bug/2032835 15:33:07 #topic LP#1999823: concurrent changes to EG and OpenSRF required; testing requested 15:33:14 I can speak to this 15:33:20 #link https://bugs.launchpad.net/opensrf/+bug/1999823 15:33:20 Launchpad bug 1999823 in OpenSRF "Name collision causes apache gateway modules to fail when mod_shib is installed" [Medium,Confirmed] 15:33:38 go ahead jeffdavis 15:33:50 Yeah, so, see above about making changes across 2 different but related projects. :D 15:34:14 basically some of the C functions in OpenSRF and EG need to be renamed to avoid collisions; it's currently an issue when using Shibboleth for SSO on Ubuntu but I think that's just one potential problem case 15:34:57 there are branches for both OpenSRF and EG making the necessary changes, this is a request for some folks besides me and JBoyer to try running those branches and see if anything breaks 15:35:26 jeffdavis: we might be candidates for testing these branches in the coming months 15:35:34 I can have a look without sso enabled. 15:35:54 that would be great! and yeah, SSO is not needed to test the branches I think 15:36:03 also, once the changes are committed to EG we'll need to update the minimum required version of OpenSRF 15:36:09 And note, if it helps, you don't necessarily have to setup a whole shibboleth setup to test them, testing them "plain" helps, as does just enabling the modules that shibboleth uses and testing then too. 15:37:09 jeffdavis: Mind if I steal the bug from you? 15:37:16 Please do! 15:37:16 jeffdavis: I was thinking that too, which means that the commits will need to take place on a major Evergreen release cycle (not bug fix cycle) 15:38:08 Well, it *could* be a bug fix cycle, but that would be a) unusual for us and b) a pain for sites to upgrade. 15:38:28 right, those reasons brought me to that thought 15:38:48 It's a bit tricky because this is a bug that prevents an existing feature from working, but the need for an OpenSRF update does make headaches 15:39:01 We've don it before, though I can think of specific release numbers. 15:39:03 jeffdavis++ 15:39:06 JBoyer++ 15:39:10 Dyrcona++ 15:39:22 s/can/can't/ 15:39:29 anyway... 15:39:38 FWIW we are hoping to go live with SSO for a few of our libraries this month, so we'll need to deploy the changes on 3.9 15:40:10 we can deal with backporting locally at Sitka but it's a bit of an added version if the changes aren't in EG until 3.12 15:40:16 *added burden 15:40:40 Well, I can test with 3.10 as well as main. 15:41:28 our container setup makes it fairly trivial to stand up a test server with certain patches on OpenSRF/Evergreen. 15:41:44 I don't think much has changed in the C code, so a backport should be trivial. 15:41:58 Would these be considered breaking changes to OpenSRF's C API? If so, should we cut a 4.0.0 of OpenSRF with these changes? 15:42:07 The Big Fix, that can't be broken by further OS updates, would be to modify our library build process to *only* export certain functions, rather than all of them. :/ 15:43:01 sandbergja, Not breaking, we can get by with only *adding* new functions, rather than removing any. So old Eg would work fine on new OSRF, but not the other way around. 15:43:07 sandbergja: I'd like to reserve 4.0 for OpenSRF over redis and merged with Evergreen, but that remains to be seen. 15:43:52 JBoyer: ahh, that makes sense. Thanks! 15:44:04 the redis change to OpenSRF does seem like a big version number increment 15:44:11 JBoyer++ 15:44:13 totally 15:44:31 #topic Announcements 15:44:36 #info Congratulations to new core committer, Josh Stompro! 15:44:37 Maybe we should jump to 5.0? 15:44:47 Stompro++ 15:44:48 Stompro++ 15:44:48 stompro++ 15:44:51 Stompro++ 15:44:52 Stompro++ # congrats! 15:44:52 Stompro++ 15:44:53 Stompro++ ! 15:44:59 Thanks, appreciate it. 15:45:05 Stompro++ 15:45:21 Stompro++ 15:45:30 Stompro++ +++++ 15:45:52 so, we have arrived at the end of the monster book 15:45:58 #info Next meeting is Tuesday, October 10th 15:46:04 :) 15:46:11 Stompro++ 15:46:12 Bmagic++ 15:46:14 #endmeeting