| Time |
Nick |
Message |
| 07:12 |
|
kworstell-isl joined #evergreen |
| 07:13 |
|
kworstell_isl joined #evergreen |
| 07:49 |
|
BDorsey joined #evergreen |
| 08:35 |
|
Dyrcona joined #evergreen |
| 08:39 |
|
mmorgan joined #evergreen |
| 09:08 |
pinesol |
News from commits: LP#2002435 release note <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=eae109b192b8359018128b7cc7fa81134c5d7a9c> |
| 09:08 |
pinesol |
News from commits: LP2002435: Add optional undelete action to basic admin page <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=be72a596d18fac13f35ffc14e9c62d559a3a3f10> |
| 09:08 |
pinesol |
News from commits: LP2002435: Don't allow shelving location fm-editor to change delete flag <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=3bd72a7782696ff03c8823c03459fee3be435d89> |
| 09:26 |
Bmagic |
Dyrcona: It's probably a missing/malformed environment or template making use of something that doesn't exist |
| 09:52 |
Dyrcona |
Bmagic: Maybe. I've noticed that the standard filters have not been renamed on the utility server. I'm testing that hypothesis first. |
| 09:56 |
Dyrcona |
Yeah. Renaming action_trigger_filters.json.example to action_trigger_filters.json fixed one of the two events on my test vm. (I found another that had not run since October 9.) |
| 09:57 |
Dyrcona |
Well, let's say it appeared to fix the event. |
| 09:58 |
Dyrcona |
Since one of the events has hourly granularity, I'll change it in production and see what happens in 10 to 15 minutes or so. |
| 10:03 |
Dyrcona |
Yeah, that was it. I got events for the hourly granularity event had not had an event created since 2022-10-09. Funny that no one noticed. Maybe we don't need to send out reminders that items are about to expire on the hold shelf? |
| 10:08 |
|
stephengwills joined #evergreen |
| 10:19 |
Dyrcona |
Twenty-two weeks and 5 days and no one complained about the hold shelf reminders. It took someone not getting a card expiration reminder before anyone said anything.... Maybe we don't need those notices? |
| 10:51 |
|
BDorsey joined #evergreen |
| 11:37 |
|
jihpringle joined #evergreen |
| 12:29 |
|
mantis1 joined #evergreen |
| 12:29 |
|
jvwoolf joined #evergreen |
| 13:26 |
Dyrcona |
Talking about something we did in August 2022. That seems likes ages ago. |
| 14:15 |
Stompro |
Licensing question, if I take a perl module and use it as an example to create something new, like the OpenILS::WWW::RemoteAuth module. Do I leave the "Copyright (C) 2019 BC Libraries Cooperative" line in my version, and add an additional line? |
| 14:43 |
|
mmorgan left #evergreen |
| 15:00 |
|
mantis2 joined #evergreen |
| 15:11 |
jeff |
"use it as an example" is pretty vague. the line between "inspired by" and "derivative work" may be difficult to define. |
| 15:12 |
jeff |
did you copy and paste and then modify? probably leave the copyright and note the original file and that you modified it. did you look at one thing and then write your own thing? probably polite/helpful to note the "inspired by" in a comment near the top of the page. :-) |
| 15:13 |
jeff |
in all cases, things are easier / lower stakes if the thing you're working on is licensed in the same way as the thing you're looking at / copying. |
| 15:13 |
jeff |
I am not a lawyer and not your lawyer, etc, etc. |
| 15:19 |
Stompro |
jeff, thanks. Right now I've copied the files and I'm trying to modify them to do what I want. So pretty heavily based on the original. By the time I'm done it may be much less so though. |
| 16:04 |
Dyrcona |
Stompro: It's OK to have multiple copyright lines. It's OK to have multiple names/institutions on one line. You should leave the original copyright header intact and add a new line. |
| 16:04 |
Dyrcona |
We should also keep our copyright headers up to date, but we don't. |
| 16:33 |
|
jvwoolf left #evergreen |
| 17:10 |
|
jihpringle joined #evergreen |
| 19:57 |
|
jihpringle joined #evergreen |
| 20:35 |
|
stephengwills left #evergreen |
