15:00:32 #startmeeting 2022-02-08 - Developer Meeting 15:00:32 Meeting started Tue Feb 8 15:00:32 2022 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:32 The meeting name has been set to '2022_02_08___developer_meeting' 15:00:38 #info Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2022-02-08 15:00:40 Third one today! 15:00:45 #topic Introductions 15:00:58 #info JBoyer = Jason Boyer, EOLI 15:01:00 #info gmcharlt = Galen Charlton, Equinox 15:01:02 #info Dyrcona = Jason Stephenson, CWMARS 15:01:04 #info miker == Mike Rylander, EOLI 15:01:06 #info alynn26 is Lynn Floyd, Evergreen Indiana 15:01:12 Dyrcona, hopefully not the worst of the day then 15:01:13 #info terranm = Terran McCanna, PINES 15:01:23 #info shulabear == Shula Link, GCHR/PINES 15:01:47 #info collum = Garry Collum, KCPL 15:01:51 #info berick === Bill Erickson, KCLS 15:02:17 #info abowling = Adam Bowling, Emerald Data Networks 15:02:23 #info phasefx = Jason Etheridge, EOLI 15:02:34 #info dluch = Debbie Luchenbill, MOBIUS 15:03:22 And as ever, folks arriving later can throw an #info to your channel. 15:03:28 #topic Action Items from Last Meeting 15:03:33 #info JBoyer will check out sandbergja's GH Actions branch 15:03:39 Checked out it was; checked-in it is. sandbergja++ 15:04:02 abneiman = Andrea Neiman, EOLI 15:04:03 #info mmorgan = Michele Morgan, NOBLE 15:04:33 sandbergja++ JBoyer++ 15:04:58 While github isn't the official home of the source it can be used for some useful things. It looks like GH Actions are powerful enough to investigate using for other things as well. (I especially like the ability to only trigger an action when a change is under this or that path.) 15:05:27 Not a lot happening this month re: release updates, on to docs 15:05:33 #topic Documentation Updates 15:05:35 Gitlab has similar features. 15:05:52 #info mantis = Gina Monti, Bibliomation 15:06:05 #info February DIG meeting rescheduled to 2/10, same time. 15:06:10 #info Reviewing documentation and image needs 15:06:32 DIG members, anything to add to the documentation and image needs review or is that just to say that it's ongoing? 15:07:03 it's ongoing 15:07:11 right-o 15:07:16 Just ongoing. We're going over stuff at the meeting Thursday, and all are welcome 15:07:28 Sounds good. 15:07:52 Luckily for everyone I had just enough time to pre-type some of this up, so here we go. 15:07:54 #topic Launchpad Status as today 15:07:59 #info Snapshot 15:08:04 #info Open Bugs - 2657 15:08:08 #info Pullrequests - 106 15:08:13 #info Signedoff - 49 15:08:17 #info Updates Since Last Meeting 15:08:21 #info Bugs Added - 38 15:08:25 #info Pullrequest tag Added - 17 15:08:28 #info Signedoff tag Added - 7 15:08:33 #info Fix Committed - 3 15:09:08 Progress is slow, but being made. Onward to better software! 15:10:01 #topic New Business 15:10:07 Just the one today, though certainly big enough to merit a full discussion. 15:10:15 #topic 3.9 Release Manager / Release Team 15:11:10 Does anyone have strong feelings about steering the ship that is 3.9, or at least want to put a hand on the rudder? 15:11:38 Specifically Evergreen 3.9, as I never actually mentioned the software by name there. 15:11:45 after a restful hiatus since 3.0 (IIRC?) I'm willing to throw my hat in the ring 15:12:02 miker++ 15:12:12 miker++ 15:12:19 miker++ 15:12:30 What are the duties of the release team? 15:12:43 miker++ 15:13:03 shulabear: coordinating, prodding folks to test/signoff/commit, release building 15:13:17 miker++ 15:13:31 I'm happy to be bug squash/feedback fest wrangler again 15:13:36 I didn't help a lick with the last team I was on; I'm willing to, but may need some help/direction 15:13:37 terranm++ 15:13:47 that was... going to be a question from me :) 15:14:02 terranm++ 15:14:22 I'm willing to volunteer, though I'm not sure how much help I'll be with the building part. 15:14:43 shulabear++ # the more the merrier on the release team 15:14:59 phasefx: c',mon in, the water's fine 15:15:06 +1 15:15:29 terranm: do you have a plan (or sense of one) for timing on FBF and BSW? 15:15:33 Then I'm in! 15:16:03 Anyone else interested in helping out? 4 person teams are common but not necessarily required. 15:16:08 looking at 3.7's schedule, we're starting a little late (not a problem, just an observation) 15:16:10 miker: I usually try to work back from whenever the targets are 15:16:18 * mmorgan is also willing to help out again, if there's room in the pool. 15:16:33 Unless someone else wants to jump in. 15:16:46 mmorgan++ # please do! you can commit ALL THE THINGS now :) 15:16:48 Ooh, an opportunity to try out the shiny new commit bit. :) 15:16:57 :-D 15:17:10 In that case, 15:17:12 Last year we did FF mid-Feb and BSW mid-March 15:17:57 terranm: ok ... then I will endeavor to put together a rough schedule in an email to -dev for release timing planning, does that work for you? 15:18:08 miker: sounds good! 15:18:28 #info The Evergreen 3.9 release team is miker, shulabear, phasefx, and mmorgan. 15:19:11 cool. just looking at last year's spring release, I think we can plan on that + a week or two 15:20:05 IMO, FF and BSW are probably the most important parts of the release process, so 15:20:08 terranm++ 15:20:19 miker++ 15:20:21 shulabear++ 15:20:23 phasefx++ 15:20:25 mmorgan++ 15:20:43 and indeed, terranm++ because those bugs need squashing. 15:21:04 terranm is masterful at coordinating those weeks! 15:21:14 Any other last minute new business that's too fresh for the agenda? 15:22:00 OR, any discussion re: release team before machinations begin? 15:22:17 I have a minor announcement when you're ready 15:22:22 I have a request for past RM teams 15:22:48 Quick Q from miker since it's relteam related, then on to gmcharlt 15:23:45 if you have any preexisting mechanisms that have been useful and productive in the past (side IRC channels, locations of buried skeletons, pot-holes to avoid) please feel free to throw them at me 15:23:52 that is all 15:24:03 gmcharlt: the floor is yours 15:24:18 miker: I encourage the use of duck imagery in regular community updates 15:24:37 quack quack 15:24:38 which, more seriously, means aiming for more regular updates from the release team; ducks are optional 15:24:49 gmcharlt++ 15:25:01 gmcharlt++ 15:25:02 gmcharlt++ 15:25:06 anyway, the update I have is in regards to users of the Evergreen to OverDrive integration, specifically the checkout/download API 15:25:29 as noted in bug 1951021, OverDrive is changing how downloads happen 15:25:31 Launchpad bug 1951021 in Evergreen "Support changes to Overdrive Checkouts API" [Medium,Confirmed] https://launchpad.net/bugs/1951021 15:25:37 more details http://developer.overdrive.com/overdrive-api-notices/01-sep-2021-coming-soon-changes-to-overdrive-checkouts-api 15:25:57 as I understand it, the drop-dead date has slipped over the past few months 15:26:16 but per an OverDrive rep, they're intending to flip the switch and remove the old download mechanism next week 15:26:38 so, one request: commiters looking at the pull request for that bug and signing off on my and jeffdavis' work 15:27:04 and second request: take note that you'll need that patch if you're a user of that integration and are responsible for applying your own patches 15:27:06 fub 15:27:10 er, fin 15:27:18 gmcharlt: Does it still use Dojo? 15:27:28 Dyrcona: correct, that hasn't changed 15:28:06 Do we have plans to replace it with something that doesn't use Dojo? 15:29:02 I assume the choicest signoffs will involve using an Overdrive testing account, which I ... have gotten in the past but no longer remember the level of hassle one is required to endure. Have you and jeffdavis verified the actual downloading bits so that "Doesn't break my system and looks sane" type signoffs are sufficient? 15:29:25 JBoyer: yes, we've verified it w.r.t. to real OverDrive credentials 15:29:33 gmcharlt++ 15:29:36 jeffdavis++ 15:29:57 JBoyer: Even if you have credentials the Overdrive test environment is a pain to use. 15:31:15 Though to guess at the answer to your Q Dyrcona, I haven't seen specific mention of a major update to the feature that I can recall. Depending on what Dojo is doing it could be a major undertaking. 15:31:57 And I can't say I'm surprised that it's a hassle to work with their backend. I'm still salty about the time they took away ftp access to new records. 15:32:11 eh, a plain vanilla rewrite is not huge IMO; just a question of tuits 15:32:30 it's been on my todo list forever, but yeah, finding time is the hard part 15:32:46 That's good to know. 15:33:02 I completely understand. I know about not having time for things, too. :( 15:34:23 Onward then, to saying things for the minutes. 15:34:27 #topic Announcements 15:34:35 #info Congratulations to new Core Committer Michele Morgan! 15:34:40 mmorgan++ 15:34:45 mmorgan++ 15:34:45 mmorgan++ 15:34:57 mmorgan++ 15:35:01 mmorgan++ 15:35:01 mmorgan++ 15:35:14 mmorgan++ # yay! 15:35:15 mmorgan++ 15:35:24 mmorgan++ 15:35:35 * mmorgan hopes folks will be available to help figure out exactly how to wield that shiny new bit! :) 15:35:39 mmorgan++ 15:35:41 mmorgan++ 15:35:53 mmorgan++ 15:36:22 Thanks all! 15:36:24 mmorgan++ 15:37:14 I feel like there's an easy joke about spinning up a new git-admins email list but having to wipe it out and start over every few months, but I've become too lazy to craft such a work correctly. 15:37:22 #info Next Meeting is March 08, 2022 15:37:33 poof 15:37:34 #endmeeting