Evergreen ILS Website

IRC log for #evergreen, 2020-03-05

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
04:43 yar joined #evergreen
04:43 ejk joined #evergreen
04:43 csharp joined #evergreen
06:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
06:52 rfrasur joined #evergreen
06:55 agoben joined #evergreen
07:09 rjackson_isl joined #evergreen
07:29 JBoyer berick, csharp, I know the beta just dropped but In your opinions is there still time to get the branch from bug 1849683 in to 3.5? It's a small permissions followup to a new feature in 3.5 but it didn't get a signoff until today.
07:29 pinesol Launchpad bug 1849683 in Evergreen "CSS From Library Setting Needs to have permissions " [Medium,New] https://launchpad.net/bugs/1849683
08:34 mantis1 joined #evergreen
08:40 collum joined #evergreen
08:44 mmorgan joined #evergreen
09:01 Dyrcona joined #evergreen
09:06 dbwells JBoyer: Feels like a bugfix to me, but I understand the caution since it touches the DB.  Also, I just noted on the bug that the seed file INSERT is missing the translation wrappers for the new strings, so we should get that squared away first.
09:27 JBoyer Ah, good catch, I'll throw on a supplemental patch for that.
09:27 JBoyer dbwells++
09:34 nfBurton joined #evergreen
09:34 StomproJ Anyone here use Hoopla and know what they want for SSH -> SIP2 connections?  The staff member I'm working with there keeps using SSL and SSH interchangably, and cannot tell me what they require.
09:34 sandbergja joined #evergreen
09:37 StomproJ I'm wondering if they use SSH like a pipe for the sip2 connection, so I need to setup an SSH user that just runs netcat to connect to the local sip port?  They don't seem to want to use SSH port forwarding.
09:40 yboston joined #evergreen
09:43 nfBurton You should be able to send SIP to 6001 without SSH?
09:44 nfBurton We have hoopla set up just with SIP2 no SSH requirement
09:44 nfBurton Or are you loading records in?
09:46 yboston joined #evergreen
09:51 mmorgan I have to reset some autorenewal action trigger events to pending that are in various states due to a trigger meltdown (which is another story).
09:51 mmorgan I'm wondering what to do about the Autorenewnotify events. Set those to pending as well? Will the reset autorenewal triggers generate new ones?
09:53 mantis1 Oddball question: can the web client be accessed and used on an iPad?
09:53 mantis1 I imagine so but I don't have one in the office at the moment to test that out.
09:55 nfBurton joined #evergreen
09:56 gmcharlt berick++
09:56 gmcharlt csharp++
09:56 mmorgan mantis1: Yes, it can, though some screens may not display well on an iPad.
09:56 nfBurton Until the new OPAC gets added ;)
09:58 mantis1 Thank you both very much!
10:01 csharp mantis1: see bug 1840950
10:01 pinesol Launchpad bug 1840950 in Evergreen "Patron expiration date & iPads" [Medium,Confirmed] https://launchpad.net/bugs/1840950
10:02 csharp (same issue exists on Safari on MacOS too)
10:20 Christineb joined #evergreen
10:26 collum joined #evergreen
10:47 mantis1 Thank you all
10:47 mantis1 csharp++
10:47 mantis1 mmorgan++
10:48 mantis1 gmcharlt++
10:48 JBoyer signoff branch for bug 1849683 has an improved supplement pushed to bring it more in line with the inserts/deletes around it.
10:48 pinesol Launchpad bug 1849683 in Evergreen "CSS From Library Setting Needs to have permissions " [Medium,New] https://launchpad.net/bugs/1849683
11:01 Dyrcona apple--
11:06 StomproJ nfBurton, sip doesn't include any encryption, so shouldn't be used without running it through stunnel or ssh.
11:09 * StomproJ too slow, nfBurton is gone :-(
11:11 pinesol [evergreen|Sam Link] LP1865951: Fixes to consistency in two files, creating uniform capitalization and use of ellipses - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f60f056>
11:11 StomproJ mmorgan, I just got excited that the Content Cafe issue was fixed, 8 requests in a row returned cover art, but then started failing again.
11:17 mmorgan StomproJ: Boo. Our newsletters are still showing revolving image/no image on reload. Response from support said they are working on it.
11:18 nfBurton joined #evergreen
11:19 StomproJ nfBurton, sip doesn't include any encryption, so shouldn't be used without running it through stunnel or ssh.
11:19 nfBurton I see....
11:28 mmorgan What does action_trigger.event.update_process refer to?
11:33 berick mmorgan: the process ID of the Perl process that last updated the event
11:33 berick primarily for debugging
11:33 Dyrcona mmorgan: It's unimportant if this is related to resetting the autorenewal events that you mentioned earlier.
11:35 mmorgan Dyrcona: I was going to reset them, but noticed some of them were still changing state in small bursts.
11:36 Dyrcona mmorgan: Oh, then leave them alone. The process is probably still running. You can check that on the server that runs the a/t runner with something like: ps -o etime $pid
11:36 Dyrcona Where $pid is the value of action_trigger.event.update_process
11:37 mmorgan So if the process is not still running, does that mean the trigger is stuck and will need to be reset?
11:37 Dyrcona I have found that it can take a while when you have thousands of them to get through. Tuesdays after long weekends are the worst.
11:37 mmorgan s/trigger/event
11:37 Dyrcona Not necessarily.
11:38 Dyrcona Do you use a special granularity for autorenewals?
11:38 mmorgan Yes.
11:39 Dyrcona Try "pgrep -af actiron_trigger" on the machine that runs a/t events. If there's one for your granularity, it is at least, still trying.
11:40 Dyrcona I ran into issues with patrons who have lots of items to renew ovetraking max_stanza_size, so I had to adjust max_stanza_size higher. I also had some queries to figure out how many items would be renewed by each event and then only reset the smaller numbers.
11:41 Dyrcona Unfortunately, this can blow up without taking out the a/t runner, but it does nothing after that.
11:41 mmorgan It was still running a few minutes ago, but it is not now, so I will reset them, but I still have the question about what to do about the autorenewnotify
11:44 Dyrcona mmorgan: I went through this between Christmas and New Years' and a bit after. You can check the IRC logs between Christmas and Dec. 31. I'll check my random SQL/ticket stuff for any useful queries that I have laying around.
11:45 Dyrcona You can tell if it is max_stanza issues by looking for JabberDisconnected in the open-ils.trigger stderr log, wherever that ends up in your system, probably in /openils/var/log
11:52 Dyrcona mmorgan: Here's a sql that gets a spreadsheet with a count of autorenewal events by user and state for a given date: https://pastebin.com/aBLB3GnY
11:52 Dyrcona You can get autorenewal-notify events by changing the event_def.
11:52 mmorgan Dyrcona: Thanks, not seeing that error in the logs.
11:53 mmorgan Right, I'm monitoring the states of the triggers I have Autorenew notify events in various states.
11:53 Dyrcona Yeah, the drones often continue working on things after the a/t runner goes away, at least that's how it looks to me.
11:53 mrisher joined #evergreen
11:53 mmorgan Just wondering how resetting the autorenewal events themselves will play with existing notify events.
11:54 Dyrcona Well, if the autorewal events are 'complete' then don't reset them.
11:54 Dyrcona Is it complete?.....
11:54 mmorgan No, I'm not touching those.
11:55 Dyrcona If the autorenewal didn't finish, I don't think the autorenewal notify event was created.
11:55 mmorgan I have collected, collecting, valid, validating, cleaning...
11:55 Dyrcona It's still working on them.
11:55 Dyrcona I find when it's done, I get only collected and complete events.
11:56 Dyrcona The ones that blow up are stuck in collected because the processing bit dies.
11:57 mmorgan Well, I had at least as many autorenewnotify events as autorenewal events when the autorenewal events had not finished. Does the notify event get added at the same time as the autorenewal event?
11:57 Dyrcona I probably have said it better in the logs somewhere between Christmas and early January.
11:57 Dyrcona The notify event is created by the autorenewal event. I'm not certain at what stage, exactly, and would have to read through the code again.
11:58 Dyrcona I've had the numbers differ slightly when there were problems.
11:58 * mmorgan will check those logs
11:58 Dyrcona Usually, they should be the same.
11:58 mmorgan I don't think they've ever been the same, even when the autorenewals have run flawlessly
11:58 Dyrcona All you have to do to reset them is set state to pending and run your a/t runner with the correct granularity and --run-pending.
11:59 Dyrcona I think they should be. Ours usually are the same, IIRC.
11:59 mmorgan Right, I'm just trying to avoid the possibilty of generating more than one notification for an autorenewal event.
11:59 Dyrcona i've run into this with courtesy notices, too. Often the same patron who has 50+ items out.
12:00 Dyrcona Right. I've not had many issues with the autorenewal itself. It has been the notify events that got stuck for us.
12:01 Dyrcona What was happening to us was that the template output exceeded the max_stanza_size in ejabberd.
12:01 mmorgan Oh, ok.
12:02 khuckins joined #evergreen
12:02 * mmorgan misunderstood, thought the issue you were having was with the autorenewals themselves.
12:02 mmorgan Don't think we've had specific issues with the autorenewnotify.
12:05 Dyrcona You should be able to delete any autorenewal-notify events that have the same target as any autorenewal events that you want to reset. That should avoid duplicates.
12:08 jihpringle joined #evergreen
12:13 mmorgan Darn. 2 patrons got duplicate autorenewnotify messages today. At least they both said the same thing ;-)
12:14 Dyrcona Yeah, that can happen when messing with the events in the database. I've done it in the past.
12:18 * mmorgan would rather not have to mess with events in the db, would rather they take care of themselves ;-)
12:18 Dyrcona Well, they usually do, just sometimes they don't.
12:19 Dyrcona I should check for errors with our evetns. I haven't done so since mid-January.
12:20 mmorgan Ours used to run smoothly, but started misbehaving occasionally early February.
12:22 Dyrcona After an upgrade?
12:22 mmorgan We are suspicious, we upgraded mid January.
12:26 Dyrcona Are you seeing autorenew events with an "error" state? I think that's normal.
12:27 mmorgan Dyrcona: I did see a few of those, but I reset them to pending and they completed.
12:30 Dyrcona I just leave them. I should take another look, though.
12:31 csharp so apparently the Safari/iOS date issue is this: https://stackoverflow.com/questio​ns/4310953/invalid-date-in-safari
12:31 Dyrcona I think action-trigger is wrong for this. It ought to be a cron job that runs and handles things withoug all of the extra overhead of a/t.
12:31 csharp where 'YYYY-MM-DD' is not valid but 'YYYY/MM/DD' is :-/
12:31 csharp (referring to bug 1840950)
12:31 pinesol Launchpad bug 1840950 in Evergreen "Patron expiration date & iPads" [Medium,Confirmed] https://launchpad.net/bugs/1840950
12:32 csharp I'm trying to fix this, but all Safari is telling me is "Invalid Date" and I can't see why
12:33 Dyrcona csharp: Because Apple, that's why.
12:33 Dyrcona Safarit doesn't follow the ECMAScript standard.
12:34 berick Dyrcona: one thing I'm doing locally for a slew of notification changes is letting A/T handle the event creation w/ NO-OP reactors, then scripting the data processing work to run outside of A/T.
12:35 berick requires more custom code :/ but much easier to manage and diagnose issues
12:36 jeff and in the end often less convoluted than some of our pre-A/T notification methods using XML notice data and/or SQL queries and API calls.
12:37 Dyrcona I just write cron jobs, but we don't really have any local notifications.
12:37 Dyrcona Too bad we can't just tell Safari user to come back with a standards-compliant browser.
12:38 Dyrcona Guess we could start using this: http://www.datejs.com/
12:39 Dyrcona This is what I dislike web development, 'cause "now, you got a dozen problems."
12:43 jeff it's okay, though! there's an npm package to help you identify which problem you want to replace your current problem with!
12:43 jeff and in case you thought i was joking: https://github.com/you-dont-need/Yo​u-Dont-Need-Momentjs#eslint-plugin
12:46 dbwells csharp: I don't think that Date issue is true any more for current Safari.  "new Date('2020-02-02')" works fine for me, and as evidenced by birth date displaying alright.  I commented on the bug with more details about what I think Safari has issues with now.
12:47 dbwells It is the lack of a colon in our timezone marking.
12:47 Dyrcona csharp: This could be fixed using the Date(year,month,day) version of the constructor.
12:47 Dyrcona Ah, but "current" is an operative term. Many people do not have "current" Safari.
12:48 dbwells Well, that bug is from 9 years ago :)
12:48 csharp dbwells: this is 13.0.5, FYI
12:48 Dyrcona I thought the problem is just "YYYY-MM-DD" with no time.
12:49 * csharp looks a dbwells's comments
12:49 Dyrcona Dates are hard, unfortunately.
12:49 csharp Dyrcona: yeah - just learned a lot of date stuff in Perl for a PINES student card project
12:50 csharp JS has always given me fits since I don't quite grok the syntax most of the time :-/
12:50 dbwells Also, unfortunately, Safari is following the ECMAScript string date standard, which is simplified from ISO 8601.  ECMAScript technically requires the colon in timezones; Firefox and Chrome are just being nice :)
12:50 Dyrcona JS has syntax? But, then again, neither does Perl. :)
12:55 * Dyrcona decides to check for himself  on his daughter's Mac Book.
13:06 Dyrcona What I'm talking about works on Safari 13.05 on Mac OS X, so I stand corrected.
13:09 Dyrcona It doess assume the date is midnight UTC, though.
13:10 Dyrcona Which is reasonable.
13:28 jeffdavis ah, the dubious joys of osrf_control --kill-with-fire
13:31 dluch 30 minute notice: DIG starts at 2 p.m. EST/11 a.m. PST
13:49 * mmorgan forgot to say
13:49 mmorgan Dyrcona++
13:55 dluch 5 minutes to the DIG Meeting!
13:59 phasefx_ joined #evergreen
13:59 rhamby joined #evergreen
13:59 miker joined #evergreen
13:59 felicia joined #evergreen
14:00 dluch #startmeeting 2020-03-05 - Documentation Interest Group Meeting
14:00 pinesol Meeting started Thu Mar  5 14:00:14 2020 US/Eastern.  The chair is dluch. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00 pinesol Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00 Topic for #evergreen is now  (Meeting topic: 2020-03-05 - Documentation Interest Group Meeting)
14:00 pinesol The meeting name has been set to '2020_03_05___documentatio​n_interest_group_meeting'
14:00 akilsdonk joined #evergreen
14:00 dluch #topic Agenda
14:00 Topic for #evergreen is now Agenda (Meeting topic: 2020-03-05 - Documentation Interest Group Meeting)
14:00 jweston joined #evergreen
14:00 dluch #info The agenda can be found here:  https://wiki.evergreen-ils.org/doku.php?id=​evergreen-docs:dig_meetings:20200305-agenda
14:00 dluch Welcome everyone!  Today's meeting will be business, followed by collaboration and working on documentation, if there's time.
14:00 dluch #topic Introductions
14:00 Topic for #evergreen is now Introductions (Meeting topic: 2020-03-05 - Documentation Interest Group Meeting)
14:01 dluch Please paste "#info <username> is <name>, <affiliation>" to identify who you are and what organization, if any, you represent.
14:01 jyorio joined #evergreen
14:01 dluch #info dluch is Debbie Luchenbill, MOBIUS
14:01 jihpringle #info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka)
14:01 abneiman #info abneiman is Andrea Buntz Neiman, Equinox
14:01 cmalm_ #info cmalm is Carissa Malmgren, Roanoke Public Library (NTLC)
14:04 dluch Thank you for coming! We are a small group today, but will be mighty! ;-) If you come in later, feel free to introduce yourself when you arrive.
14:04 dluch #topic Helpful Information: Documentation contributions and collaboration
14:04 Topic for #evergreen is now Helpful Information: Documentation contributions and collaboration (Meeting topic: 2020-03-05 - Documentation Interest Group Meeting)
14:04 dluch #info You can find the Documentation Needs List at https://wiki.evergreen-ils.org/doku.php​?id=evergreen-docs:documentation_needs
14:04 dluch #info DIG Roles can be found at https://wiki.evergreen-ils.org/doku.p​hp?id=evergreen-docs:digparticipants
14:04 dluch #topic Old and Ongoing Business
14:04 Topic for #evergreen is now Old and Ongoing Business (Meeting topic: 2020-03-05 - Documentation Interest Group Meeting)
14:05 dluch #info Previous Action Items
14:05 dluch How are we doing on these?  I think most of the people in them aren't here, but I'll take them in order...
14:05 dluch #1, sandbergja: video for proof of concept in the Quick Starts section?
14:06 dluch (I don't see her on IRC right now, so we'll move on)
14:06 dluch #2, I'm also going to skip this one, since we have more on Antora progress later
14:06 dluch #3, Everyone will test the Antora server and email the DIG list (or IRC) with problems (or suggestions)
14:06 dluch I know that sandbergja and some of her people did this, and posted to the Launchpad bug. Anyone else? Do we need to keep this as an action item?
14:07 abneiman I have not tested Antora, but if you are happy with the test outcomes so far we could probably drop the action item
14:08 alynn26 #info alynn26 is Lynn Floyd Evergreen Indiana
14:08 dluch I think they've been good. bmagic and remingtron, what do you think?
14:08 dluch Hi, Lynn!
14:09 dluch Okay, well... #4, Everyone, when adding agenda items, please include your name in parenthesis
14:09 dluch No one added any agenda items except me, lol.
14:09 dluch Let's all just keep this in mind for future meetings, please. :-) I don't think we need to keep it as an action item.
14:09 alynn26 lol
14:10 dluch So, I'm going to keep the other action items for next time...
14:10 dluch #action sandbergja will make a video for proof of concept in the Quick Starts section
14:10 dluch Ha, I guess that's it.
14:11 alynn26 hi ya'll
14:11 dluch #info Update on Documentation server move
14:11 dluch gmcharlt: how's this going?
14:12 gmcharlt dluch: stalled at present, but I would like to set a time next week with interested parties, possibly via GTM, to get back on track and ensure that credentials are distributed
14:12 gmcharlt with Wednesday, Thursday, and Friday afternoon ET being generally the best for me
14:13 dluch Awesome, sounds good. If I remember correctly, that was going to be remingtron and sandbergja, though I'll be happy to participate, too
14:13 alynn26 gmcharlt++
14:13 dluch gmcharlt++
14:14 gmcharlt dluch: I'll send a Doodle to the three of you; feel free to forward as desired
14:14 dluch Sounds great, thank you!  Is there anyone else at the meeting today that would like to be included?
14:14 * alynn26 raised hand
14:14 abneiman me, please
14:15 dluch Great!  Thanks, alynn26 and abneiman!
14:16 gmcharlt noted, thanks
14:16 dluch alynn26++
14:16 dluch abneiman++
14:16 abneiman gmcharlt++
14:16 dluch Okay, moving on...
14:16 dluch Well, this might not fly, either, lol
14:16 dluch #info Antora progress
14:17 dluch bmagic and remingtron: Where are we with Antora nav?
14:17 dluch (I'm pretty sure bmagic went to lunch)
14:17 dluch Anyone know... Did we get things done in time to be included in 3.5?
14:18 dluch (I'm thinking no, but I haven't read the release notes closely...)
14:18 abneiman dlu
14:18 abneiman dluch: not that i can tell
14:18 dluch Okay, thanks
14:19 dluch What else do we need to be doing for this project going forward? Do we know yet?
14:19 abneiman there's only one LP item for antora, and it's still open
14:19 dluch abneiman++
14:19 abneiman see remingtron's comment here for next steps: https://bugs.launchpad.net/ever​green/+bug/1848524/comments/21
14:19 pinesol Launchpad bug 1848524 in Evergreen "wishlist: Antora-ize docs " [Undecided,New]
14:21 dluch #action everyone will review all of the docs on Antora, looking for broken things and other fixes needed and report on Launchpad
14:21 dluch Any other old or ongoing business to discuss?
14:21 alynn26 I'm thinking that if we do not get them in 3.5, we so a big push at the Conference.
14:21 dluch alynn26: that's an excellent idea
14:23 dluch Okay, moving on...
14:23 dluch #topic New Business
14:23 Topic for #evergreen is now New Business (Meeting topic: 2020-03-05 - Documentation Interest Group Meeting)
14:23 dluch #info April and May Meetings
14:23 dluch Normally, we would have the April meeting on the 2nd and the May meeting on the 7th. April would be a collaboration/working time meeting and May would be a business meeting.  But, DIG will also meet at the Evergreen International Conference later in April, and will have a documentation hackfest on pre-conference day.
14:23 dluch Should we skip April and/or May?
14:24 dluch It looks like, in past years, we've often had the April meeting, had the hackfest and meeting at conference, and skipped May, but that's not always the case.
14:24 dluch I have no real preference, so will go with what the group would like.
14:24 jihpringle do we want to do anything 3.5 related before 3.5.0 is released?
14:27 dluch We're aiming for the 3.5 release to be before the conference, right?
14:27 jihpringle I'm not sure if the release date has changed, but it was slated for April 1st
14:27 alynn26 From what i know it's still slated for April 1st.
14:28 * csharp confirms April 1st
14:28 jihpringle there's a bug squashing week planned for the week of March 16th
14:29 dluch And if we had the April DIG meeting, it would be on the 2nd. But it would be all collaboration time, and we could work on 3.5 docs then, too...
14:29 dluch csharp++
14:29 dluch jihpringle: so we could push on docs during that week?
14:30 jihpringle possibly???
14:31 abneiman dluch: jihpringle: IMO no reason to not include docs work as part of Bug Squashing Week, if people are available/willing
14:31 alynn26 Yes
14:31 dluch Yeah, I think that's a good idea.  jihpringle++
14:31 alynn26 I got a couple of bugs in docs I can push that week.
14:31 dluch excellent
14:32 dluch #action DIG will work on 3.5 documentation during Bug Squashing Week, March 16-20
14:32 dluch So, also have the April meeting?
14:32 jihpringle I haven't had a chance to look at the release notes in any depth but I think the biggest changes from a docs perspective will be the angular catalogue which I don't think we've included in the 3.4 docs (after a quick skim)
14:33 dluch jihpringle: I think you're right
14:33 alynn26 yes, to the april meeting, and then most likely not the May meeting.
14:33 abneiman also there's a lot of angular admin ports, so screen shots might need updating
14:33 dluch abneiman: Yes, that's true!
14:33 alynn26 screenshots--
14:33 dluch Thanks, alynn26.  We'll plan on that, then.
14:34 jihpringle do we need to make a decision about how and when we start including the angular catalogue?
14:35 dluch Do we wait until it's all done and "standard" or make a special section for the experimental version?
14:35 alynn26 I think we do.  I think a special section for the experimental version with some basic information is needed.
14:35 abneiman If someone has tuits & the inclination, documenting (at least in part) the experimental version might be a kindness
14:35 abneiman as long as we're clear that it's still experimental
14:36 abneiman I can ask CWG next week if they might be able to pitch in on that
14:36 alynn26 I know we are looking at going to 3.4 this spring with the experimental turned on.
14:36 jihpringle I agree with having a special section to start including it
14:36 alynn26 We will start doing some basic documentation in house on it.
14:36 dluch Agreed.
14:37 alynn26 CWG++
14:37 jihpringle we're thinking about having a library or two pilot it when we move 3.5 in May so we also be starting to document it in house
14:37 dluch abneiman: thanks for asking CWG!
14:37 dluch CWG++ indeed
14:37 alynn26 If they can do some and get it to us in some form, we will translate.
14:38 dluch Yep
14:38 dluch I will probably not have time before bug squashing week, but I do want to play around with it more and can also help contribute some
14:42 dluch #agree We will begin working on documentation for the experimental catalog now
14:42 dluch #info Conference plans
14:42 dluch (I forgot to put this one on the agenda)
14:42 dluch At the January meeting, we talked about docs related programs that are happening at the conference. Usually, at the hackfest, we also have a couple of people who help to guide new folks on getting started (or folks like me, who always forget, lol).  Do we have a couple of you willing to do that? morning and/or afternoon?
14:43 alynn26 I will be available in the morning
14:43 alynn26 I have the new Dev meeting in the afternoon.
14:43 dluch alynn++
14:43 dluch oops
14:43 dluch alynn26++
14:43 alynn26 :)
14:44 alynn26 that's my alter alter alter ego
14:44 abneiman I can be available for docs hackfest, probably all of it, though I may sit in on new devs in the afternoon as well
14:44 dluch :-)
14:44 dluch abneiman++
14:44 dluch Anyone else available/willing to mentor folks in the afternoon (or also in the morning)?
14:45 dluch I'll be there all day, of course. ;-)
14:46 alynn26 So, we will get them started, then you can work with them in the afternoon, I will be on IRC most of the day
14:46 abneiman yeah, I will likewise be available for IRC pings even if I'm not in the room
14:46 dluch :-) Sounds good!  Thank you both!!
14:46 dluch Is there any other new business we need to discuss?
14:47 alynn26 I am sure bmagic and remington will be around also
14:47 dluch Yes, probably!
14:47 abneiman I think sandbergja is planning to be at the conference as well
14:48 dluch excellent
14:48 dluch #topic Collaboration time
14:48 Topic for #evergreen is now Collaboration time (Meeting topic: 2020-03-05 - Documentation Interest Group Meeting)
14:49 dluch We have 12 minutes left. Not much, but we can still work on stuff if you want.  What did everyone planning to work on today?  Let us know here, and feel free to talk and work with each other.  If you'd like extra accountability, I can make an action item to show up in the minutes, but it's not necessary.
14:50 dluch (excuse typo above.  sigh)
14:50 abneiman I have to skedaddle but I'll teport back next week about whether CWG is able to assist with experimental catalog docs
14:50 dluch abnieman: Thanks!
14:51 abneiman dluch++ # fearless leader
14:51 dluch :-)
14:51 alynn26 dluch++
14:51 dluch If everyone is amenable, I'm happy to end the meeting now...
14:52 dluch Next meeting will be April 2. Same time, same place.  It will be primarily collaboration time.  Everyone also please work on 3.5 docs during Bug Squashing Week in March!
14:52 dluch Thanks for coming, everyone!
14:52 alynn26 +1 fore ending
14:52 jihpringle thanks dluch++
14:53 cmalm dluch++
14:53 dluch #endmeeting
14:53 Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration
14:53 pinesol Meeting ended Thu Mar  5 14:53:06 2020 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:53 pinesol Minutes:        http://evergreen-ils.org/meetings/evergr​een/2020/evergreen.2020-03-05-14.00.html
14:53 pinesol Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2020/evergreen.2020-03-05-14.00.txt
14:53 pinesol Log:            http://evergreen-ils.org/meetings/evergree​n/2020/evergreen.2020-03-05-14.00.log.html
14:59 mantis1 left #evergreen
15:05 Bmagic Just got back from lunch
15:05 Bmagic sorry I missed the meeting :) dluch
15:06 dluch ruined the whole thing. JK ;-)
15:52 sandbergja joined #evergreen
16:16 jihpringle joined #evergreen
16:27 mrisher joined #evergreen
16:46 jihpringle joined #evergreen
17:16 mmorgan left #evergreen
17:56 sandbergja joined #evergreen
18:02 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:06 mikerisher joined #evergreen
20:56 RBecker joined #evergreen
21:19 sandbergja joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat