15:01:08 #startmeeting 2021-03-09 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-03-09 15:01:08 Meeting started Tue Mar 9 15:01:08 2021 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:08 The meeting name has been set to '2021_03_09___developer_meeting__agenda_available_at_https___wiki_evergreen_ils_org_doku_php_id_dev_meetings_2021_03_09' 15:01:16 #topic Introductions 15:01:20 #info Dyrcona = Jason Stephenson, CW MARS 15:01:26 New meeting time, new into time. 15:01:35 #info gmcharlt = Galen Charlton, Equinox 15:01:37 #info JBoyer = Jason Boyer, Equinox 15:01:38 #info miker = Mike Rylander, EOLI 15:01:39 #info terranm = Terran McCanna, PINES 15:01:40 #info rhamby = Rogan Hamby, Equinox 15:01:46 #info shulabear = Shula Link, GCHRL 15:01:51 #info mmorgan = Michele Morgan, NOBLE 15:02:03 #info sandbergja = Jane Sandberg, Linn-Benton Community College 15:02:53 #info jeffdavis = Jeff Davis, BC Libraries Cooperative 15:02:53 #info csharp = Chris Sharp, GPLS 15:03:17 Nice to see some more names in our new time slot. Anyone else coming in later feel free to #info it up. 15:03:28 With no action items from the last meeting we'll move on to Eg updates. 15:03:32 #topic Evergreen Release Update 15:03:49 #info 3.7 Feature Freeze tomorrow 15:04:05 #link https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:3.7 3.7 Roadmap 15:04:13 #info Bug Squashing Week March 15-19 15:04:23 #info berick Bill Erickson 15:04:41 Bug Squashing spreadsheet is started here: https://docs.google.com/spreadsheets/d/1wCOjCAfG82ZLpCQckPmCbrUrpZZuCcZF7ECQJKQgc0c/edit#gid=0 15:04:54 terranm++ 15:05:02 I'd like to suggest a BSW cleanup project of the webstaffclient tag. That would involve updating all of the bugs that have it to remove that and make sure they have a more specific tag. 15:05:10 I know I need to update a couple machines for that. 15:05:41 That's not a bad idea. 15:05:45 I've got several questions, but here's one to start 15:05:46 terranm++ 15:05:59 are we comfortable making the switch to Bootstrap as the default OPAC theme for 3.7? 15:06:51 We've been running the Bootstrap OPAC with some minor customizations for almost 2 months now and we are happy with it. There are a few things that aren't available yet, like the curbside pickup functionality 15:07:30 That's coming soon 15:08:09 https://bugs.launchpad.net/evergreen/+bugs?field.tag=bootstrap-blocker 15:08:12 If we want to make *certain* that people give it a shot and report bugs rather than waiting for it to be "finished" making it the default with the option to fall back to the TPAC is probably a good idea 15:08:57 * mmorgan notices bug 1898775 which would be a blocker for us 15:08:58 Launchpad bug 1898775 in Evergreen "Bootstrap OPAC: Add to bucket broken" [Medium,Confirmed] https://launchpad.net/bugs/1898775 15:08:58 My sense is that it's a bit of a stretch, given how thinly spread local sysadmins are right now. 15:09:25 I tend to agree with JBoyer; any strong objections to that approach? 15:09:43 My preference would be to say all 3.8-targeted dev that touches the OPAC has to work with the bootstrap OPAC; and then set bootstrap as default in 3.8 15:10:11 but mine is a light objection rather than a strong objection 15:11:06 mmorgan: I think we got that working, but I'll have to go back and see what we did. It might have just been the link not getting formed correctly. 15:11:39 terranm: Thanks, good to know! 15:13:08 What does "making Bootstrap the default" actually entail? Is it just a question of changing the default value for OILSWebTemplatePath ? 15:13:10 I'm basically just suggesting we un-comment the 1-2 lines that currently prevent the bootstrap opac from displaying with an upgrade note detailing how to turn it back off. So long as folks know about it ahead of time it shouldn't be too burdensome, but we could use the feedback from people on the fence if that's enough to nudge them toward using it. 15:13:20 jeffdavis: aye 15:13:23 jeffdavis, basically un-commenting 1 or 2 lines 15:13:31 I think we should make the switch but hold off on a formal deprecation of TPAC until 3.8, though if we do that, we should decide whether we want to say that new features aren't required to be supportded in TPAC 15:13:33 I think we have too many rewrites going on and everything feels half-baked. It should be experimental until its done, then we can have a good 4.0 release in a year or so. 15:15:38 gmcharlt: holding off on deprecation, but still making bootstrap default seems good to me. 15:16:39 I don't really anticipate it ever being "finished" if it's just a thing that systems play with on test servers. It would also be hard to tell devs working on opac features they have to focus on the one that's off by default or do everything twice. 15:17:15 well, we are running it without major problems in PINES, so it's definitely beyond test server status 15:17:41 I don't think I expressed myself as well as I could have, but so be it. 15:18:24 Dyrcona: I agree with your point that we're in a half-baked status with a lot of our major UIs: bootstrap, ang OPAC, etc. 15:19:18 Heh, moving to the bootstrap opac over the course of the next couple major releases is one way to get rid of all of the dojo in the opac. :) 15:19:20 So, I'm OK with it, if we focus on dropping AngularJS, Dojo, XUL, tpac, etc. 15:19:54 * csharp watches the waves of hate for dojo emanating from his fingers as he types 15:20:20 csharp: there are laws about the handling of hazardous materials, you now ;) 15:20:25 *know 15:20:27 heh 15:20:50 * csharp hides the chemicals from OSHA inspectors at his house 15:21:08 Not being a group that's big on motions and whatnot, I would at least like some rough numbers of what people think: 15:21:42 Being in PINES, I can confirm that bootstrap is working well live. 15:21:42 #startvote Make the Bootstrap OPAC the default in 3.7 with an easy way for systems to revert to the TPAC if desired? yes no abstain 15:21:42 Begin voting on: Make the Bootstrap OPAC the default in 3.7 with an easy way for systems to revert to the TPAC if desired? Valid vote options are yes, no, abstain. 15:21:42 Vote using '#vote OPTION'. Only your last vote counts. 15:21:54 #vote yes 15:22:02 #vote yes 15:22:02 #vote yes 15:22:02 #vote yes 15:22:03 #vote yes 15:22:06 #vote abstain 15:22:09 #vote yes 15:22:17 #vote yes 15:22:33 #vote yes 15:22:35 #vote yes 15:23:06 #endvote 15:23:06 Voted on "Make the Bootstrap OPAC the default in 3.7 with an easy way for systems to revert to the TPAC if desired?" Results are 15:23:06 yes (9): JBoyer, shulabear, sandbergja, mmorgan, gmcharlt, csharp, terranm, rhamby, miker 15:23:06 abstain (1): Dyrcona 15:24:07 So it looks like the overall consensus is to aim for that. There are some patches ready or coming soon that I'm sure will help. 15:24:25 The good word from the various PINES folks about Bootstrap is encouraging. 15:24:47 pines++ 15:24:53 I'd like to ask about some of the roadmap entries as well 15:25:17 e.g., berick, the item editor - where do you think it stands w.r.t. the latest round of feedback? 15:25:37 * miker lines up behind gmcharlt 15:26:09 gmcharlt: i'm under some time constraints so I'm not sure about hitting the 3.7 deadline 15:26:19 but i have reviewed the feedback and it makes sense 15:26:34 note leaving the alerts, etc. out was not intentional 15:26:43 berick: that was my sense as well (re timing), but I wanted to make sure 15:27:10 question about the angular editor: 15:27:11 i will update the LP soon, though, either way 15:27:30 Once it goes in, there's no fallback to the current editor, true? 15:27:43 mmorgan: should still be accessible from the Classic catalog 15:27:54 or Traditional 15:28:06 Ok, thanks! 15:28:30 I think geographic sorting (bug 1863252) is close, but any testers available for today/tomorrow? 15:28:31 Launchpad bug 1863252 in Evergreen "Wish List - Ability to sort holdings in OPAC based on geographic proximity to user specified location" [Wishlist,New] https://launchpad.net/bugs/1863252 15:28:56 I'd be available to test it tomorrow. 15:29:35 also noting that we found some testing issues re consolidate patron notes/alerts/message (bug 1846354); I'm personally a bit dubious about it make it in tomorrow, but I do think that we need to get it in as early as possible during the 3.8 cycle 15:29:37 Launchpad bug 1846354 in Evergreen "wishlist: Consolidate patron notes, alerts, and messages" [Wishlist,New] https://launchpad.net/bugs/1846354 - Assigned to Galen Charlton (gmc) 15:29:41 shulabear++ 15:30:10 and a general plea for scale testers of triggered events log rewrite (bug 1207533) 15:30:11 Launchpad bug 1207533 in Evergreen "Triggered event log times out for large-data sites" [Medium,Confirmed] https://launchpad.net/bugs/1207533 15:30:24 miker: what did you want to bring up? 15:30:36 We tested notes consolidation late last week and didn't find any problems, but I didn't go through all the comments to verify 15:30:42 terranm: first, thanks for all the lasso testing so far! do you think you'd have a chance to look at the record detail copy table changes on festivus? 15:30:45 I was mainly testing conversion 15:30:57 terranm: we subsequently found issues related to it re patron merging and purging 15:31:11 miker: Yes, I can look tomorrow if that's not too late 15:31:13 but it's definitely good that the conversion is looking good to you 15:31:23 (note, but both tpac and boopac are lasso-adjusted -- they share the relevant code) 15:31:46 terranm: thanks. as for if that's too late ... 15:31:58 csharp: DYM still building on your test system? 15:32:05 gmcharlt: yep 15:32:12 is feature freeze tomorrow EOD or at midnight in 8.5 hours 15:32:14 still on "identifier" 15:32:31 7+ days so far 15:32:37 miker: tomorrow EOD 15:32:44 csharp: just on identifier? 15:33:02 releated to miker's question, could we have a refresher what feature freeze means: patches in master, bugs targeted with pullrequest, signedoff, what? 15:33:26 Dyrcona: freeze = patches in master; slush = viable pull request 15:33:28 I don't think it's been 7 days of identifier, but after 7 days it's somewhere in identifier. 15:33:35 no - it's done title, author, series, and now on identifier 15:33:45 ok 15:33:58 still have keyword and subject after that 15:34:07 Should we info some of these things for the minutes? 15:34:08 csharp: ugh ... I won't have time for a side-loader before EOD tomorrow, but I think that'll be necessary 15:34:42 haha - the dym.prime.sql file is 9GB :-) 15:34:51 didn't think to look at that before 15:36:22 I think the last roadmap bug we haven't discussed yet is bug 1901930 (SIP2 mediator) 15:36:23 Launchpad bug 1901930 in Evergreen "Evergreen SIP2Mediator Support" [Wishlist,New] https://launchpad.net/bugs/1901930 15:36:23 Dyrcona, not a bad idea; I always thought the "feature" part was the significant bit, so no more features after tomorrow (like DYM or geosort) but smaller bugfixes would still be ok. 15:36:44 ^ yeah 15:36:54 oooh - I keep meaning to test that and keep getting derailed (SIP2Mediator) 15:38:13 berick: out of curiosity, are you y'all running that in production (particularly with your sorter?) 15:38:46 gmcharlt: not yet. soon, though 15:39:15 I had been wanting to test that so I'm willing to do so tonight / tomorrow. 15:41:20 52,071,071 lines in that file (wc -l took a while) 15:42:53 I'm personally a bit dubious about rushing that one in - while it /mostly/ stands off to the side, the new interface for managing SIP2 accounts could very much give the wrong impression if you don't want to jump off SIPServer right away 15:43:41 so, are there any other new feature pull requests that anybody wants to strongly advocate for putting in tomorrow? 15:44:10 any ECDI stuff that's just sitting there? (kinda looking at terranm ) 15:44:23 Uh... I think just geosort 15:44:33 Yes, bug 1861319 15:44:35 Launchpad bug 1861319 in Evergreen "Allow Item Renewal on Expired Patron Record" [Wishlist,Confirmed] https://launchpad.net/bugs/1861319 15:44:56 * rfrasur is "listening in" (csharp, terranm) 15:45:25 bug 1885179 and bug 1904788 would be pretty easy to review, i think. one is signed off. 15:45:27 Launchpad bug 1885179 in Evergreen "Angular staff catalog Add All Search Result to Basket option" [Wishlist,New] https://launchpad.net/bugs/1885179 15:45:28 Launchpad bug 1904788 in Evergreen "Staff catalog browse paging from record list support" [Wishlist,New] https://launchpad.net/bugs/1904788 15:45:46 Dyrcona: 1861319 doesn't look too scary; I'll take a look at it 15:47:03 berick: and I previwed 1885179 a while back, so I will look at it as well 15:47:21 gmcharlt++ 15:47:28 gmcharlt++ 15:47:47 https://bugs.launchpad.net/evergreen/+bug/1853006 - This one would be good to get in even though it's only done for TPAC 15:47:48 Launchpad bug 1853006 in Evergreen "Add "limit to available" option in OPAC record view" [Wishlist,New] 15:48:08 bug 1863252 is geosort FWIW 15:48:08 Launchpad bug 1863252 in Evergreen "Wish List - Ability to sort holdings in OPAC based on geographic proximity to user specified location" [Wishlist,New] https://launchpad.net/bugs/1863252 15:48:10 * mmorgan was just going to mention 1853006 :) 15:49:05 Already discussed, but we are really hoping for Did you mean... 15:49:35 mmorgan: I think miker is gonna rejigger the upgrade 15:49:47 so probably not in time 15:49:59 I can look at bug 1207533 tomorrow. 15:50:00 Launchpad bug 1207533 in Evergreen "Triggered event log times out for large-data sites" [Medium,Confirmed] https://launchpad.net/bugs/1207533 - Assigned to Jason Stephenson (jstephenson) 15:50:00 miker++ 15:50:02 also like to see 1853006 go in, and then we can look at bootstrap update to it. 15:50:04 csharp++ 15:51:52 Looks like there's a lot of good stuff to test out tomorrow, anyone have anything else they want to bring up before we move on? 15:52:16 tick 15:52:17 tick 15:52:43 #topic DIG evaluating outstanding 3.6 documentation and turning to 3.7 15:53:03 dluch, or other DIG folks, anything to add? 15:54:33 Well, I'm sure the 3.6 documentation is outstanding; here's hoping it doesn't need too much editing to be made into 3.7. (bah-dum, psh.) 15:55:36 I'm not going to go into much detail on the LP stats since the hour is nearly up, but thank you to those who gathered them. ( mmorgan, sandbergja ?) 15:55:50 * mmorgan raises hand 15:55:57 mmorgan++ 15:56:09 FYI: There are utilities for gathering stats if you run Ubuntu: lp-tools package. 15:56:10 Just want to keep some running data points on that. 15:56:36 Dyrcona: Thanks, I'll take a look, that certainly would be helpful. 15:57:02 Dyrcona, I saw you mentioned trying that out, does it work well with our projects? (I thought there was some issue with it in the past or something like that) 15:57:51 My issue in the past seemed to be with limits on number of requests or something like that when doing mass bug updates. 15:58:14 With the discussion of the default opac in 3.7 there is one other timing / planning thing that would be good to have input on. 15:58:20 #topic New Business 15:58:33 #topic Schedule removal of XUL code from Evergreen 15:59:04 So, probably not happening tomorrow. :) Dyrcona, did you have a timeframe in mind (3.8, etc.) or something else? 15:59:15 I did some poking and it looks like some of the Dojo code relies on XUL, so the two should be dropped at the same time. 16:00:07 Mmm. Dojo can carry a larger target on its back. 16:00:16 I was thinking 3.8, but I'm less sure. We'd have to come up with replacements for some of the features that still rely on Dojo. 16:01:02 if those can be discretely identified and bug-reported, that would help us know what we're up against (I'm happy to help with that) 16:01:50 That sounds good. 16:02:27 Looking ahead, maybe we could shoot for 4.0 where everything is Angular? 16:02:36 hmm, user permission editor being a big one (of actual code under /xul/ still in use) 16:02:49 Would a couple people like to take on an action item to identify and document the dojo bits so they be can be removed? 16:03:03 Is the Reports interface using dojo? 16:03:33 The only part that could is the folder page, and I don't *think* it does. 16:03:45 Since i raised the issue. I'll volunteer to document what still uses dojo and xul. 16:03:52 Dyrcona++ 16:03:54 Dyrcona++ 16:03:54 (have not yet checked) Though that page also needs updating 16:04:00 Dyrcona++ 16:04:23 csharp, were you volunteering to help do that also or help remove some of them later? 16:05:19 #action Dyrcona to start documenting where Dojo and XUL are still required so they can be completely removed. 16:06:25 At this point in the day we may well be losing folks to the clock. 16:06:43 Does anyone else have anything to add before we call it a day? 16:07:02 I have enough to do already :) 16:07:15 #topic Announcements 16:07:18 #info Next Meeting is April 13, 2021 16:07:22 #endmeeting