Time |
Nick |
Message |
07:01 |
|
collum joined #evergreen |
07:36 |
|
kworstell-isl joined #evergreen |
07:56 |
|
BDorsey joined #evergreen |
08:04 |
|
cbrown joined #evergreen |
08:56 |
|
mmorgan joined #evergreen |
08:57 |
|
terranm joined #evergreen |
09:14 |
|
abowling joined #evergreen |
09:16 |
Bmagic |
Any streaming options for us remote people to watch? |
09:16 |
Rogan |
https://us02web.zoom.us/j/88077861312?pwd=diZubjjUZTrVMs6PLDYRO5Rfxyn3Ao.1 |
09:16 |
|
mdriscoll joined #evergreen |
09:17 |
mmorgan |
Here's the zoom link for the hack-a-way: https://us02web.zoom.us/j/88077861312?pwd=diZubjjUZTrVMs6PLDYRO5Rfxyn3Ao.1 |
09:17 |
Rogan |
zoom link for hack-a-way ^ |
09:18 |
Bmagic |
excellent! |
09:19 |
|
smorrison joined #evergreen |
09:27 |
|
dguarrac joined #evergreen |
09:38 |
eeevil |
https://www.postgresql.org/docs/current/sql-creatematerializedview.html |
09:39 |
eeevil |
https://www.postgresql.org/docs/current/sql-refreshmaterializedview.html |
09:40 |
eeevil |
report output can be put into a bucket now |
09:40 |
eeevil |
replace or append |
09:41 |
eeevil |
counterpoint: if it's only updated every 10 min, how about cache it instead of hitting the database? |
09:41 |
eeevil |
it's not triggers |
09:41 |
eeevil |
it's a materialized view |
09:42 |
eeevil |
yes |
09:42 |
eeevil |
see: those links :) |
09:44 |
|
Dyrcona joined #evergreen |
09:44 |
abneiman |
we (EOLI) explored this a lot a few years ago, and a potential complication we uncovered is that different ways people would want to slice the data based on locations, patrons, etc etc., past statistics as just mentioned - is actually a very big problem to solve |
09:44 |
abneiman |
one-size-fits-all for a dashboard is a tall order |
09:44 |
Bmagic |
understood |
09:47 |
|
redavis joined #evergreen |
09:48 |
|
sandbergja joined #evergreen |
09:51 |
sleary |
hey Jane! we're talking about adding report data charts and graphs to the staff portal |
09:53 |
sandbergja |
heya! nice! |
09:53 |
sandbergja |
thanks for the context |
09:55 |
* eeevil |
kills another conversation... :P |
09:56 |
abneiman |
eavesdropping from across the room: just heard metabase mentioned ... the upshot is there are already 3rd party tools that do dashboarding, and the lift to do it internally is a lot (and for a honestly narrow user audience) |
09:58 |
|
smorrison joined #evergreen |
10:02 |
|
kmlussier joined #evergreen |
10:03 |
|
collum joined #evergreen |
10:05 |
kmlussier |
I scheduled the search filtering discussion for 9:30 a.m. tomorrow. |
10:05 |
Bmagic |
ty |
10:09 |
sleary |
kmlussier++ |
10:10 |
redavis |
kmlussier++ |
10:21 |
|
akilsdonk joined #evergreen |
10:29 |
berick |
fyi just added Releases/Git Discussions to agenda for 1:30pm tomorrow |
10:33 |
sandbergja |
fwiw Bmagic: there are temporal extensions to postgres to allow you to travel back in time and do queries at that point in time. I have exactly no experience with them: https://wiki.postgresql.org/wiki/Temporal_Extensions |
10:33 |
Bmagic |
wow, that's interesting |
10:33 |
Bmagic |
I bet it's slow |
10:33 |
sandbergja |
yeah, I wouldn't be surprised |
10:33 |
|
Christineb joined #evergreen |
10:36 |
phasefx |
random aside, re: redis, I've been using IRC as my message bus for hobby coding :-D |
10:38 |
berick |
phasefx: neat! |
10:38 |
Bmagic |
I might be sold on using the reporter to output files to disk for consumption for our dashboard. But! I don't think we should output the files to the same place as all the rest of the reports because of the automated deletion of those files and orphaned reports cleanup. I think these outputs are "special" |
10:39 |
phasefx |
berick: AI powered chat bot + traditional IRC bots |
10:40 |
phasefx |
(plus a chess bot, a text to speech bot, random stuff) |
10:41 |
phasefx |
thinking about building a cognitive architecture where different IRC channels serve as functional areas modeling the human brain |
10:44 |
berick |
phasefx: love it. |
10:44 |
berick |
the real metaverse begins |
10:44 |
phasefx |
old meets new |
10:45 |
phasefx |
we are borg, resistance is ---Netsplit |
10:46 |
Bmagic |
eeevil: correct me if I'm wrong, but if we hook a chart to an outputted disk file created by clark, it's possible that the staff-designed template can output stuff that's too noisy or otherwise not compatible. So, that means that we'd need to change the template interface to ensure the outputs are "dashboard compatible" |
10:46 |
phasefx |
we may want to throw IRC up on the big screen to compliment Bmagic's head |
10:46 |
Bmagic |
haha |
10:46 |
Bmagic |
there is that better |
10:47 |
phasefx |
you felt how I used big and head in the same sentence but didn't directly tease you? :-D |
10:47 |
Bmagic |
it was amazing |
10:47 |
* eeevil |
reads up |
10:49 |
Bmagic |
sorry, I should clairify: I'm thinking along the lines of clark outputting JSON to disk, and still using the dynamic chart UI on the interface |
10:53 |
eeevil |
here are the mockups from our 2021 "director's dashboard" ... thing. https://nox.esilibrary.com/~miker/Dashboard-Mockups-2021.pdf |
10:54 |
Bmagic |
this looks familiar, I think I've stumbled on this before |
10:54 |
eeevil |
chrome hates me... take the "s" outta there: http://nox.esilibrary.com/~miker/Dashboard-Mockups-2021.pdf |
10:54 |
Bmagic |
yeah, I took the s out |
10:55 |
sleary |
right now, the dashboard entries are set at the OU level, right? Not individual users? |
11:00 |
Bmagic |
solving the problem of snapshotting the stats at any given time seems to be disk. So with that as a given, maybe we can combine that idea with the guardrails idea. What if we wrote snapshotted json to disk in a special folder structure (sort of like clark) but in a controlled way. We could use memcached to hold already-retrieved disk for speed, and feed json to the staff client for chart making |
11:02 |
Bmagic |
I'm still advocating for restricting the facets to some reasonable number, like 10 to start with. So we don't have a run-away feature creep issue. |
11:03 |
eeevil |
sleary: that's ... an open implementation decision, I think. |
11:03 |
|
mdriscoll joined #evergreen |
11:06 |
Bmagic |
This feature isn't reports, at least not reports as we define them in the context of current Evergreen reports. I'm not seeing a way forward using clark as-is. It's too open-ended, and using the report template designer as a starting point will make this feature less appealing IMO. |
11:07 |
eeevil |
I don't think anyone is saying there shouldn't be sane defaults, but there are better tools for the job than One Wide Table To Rule Them All |
11:08 |
Bmagic |
I'm convienced that we shouldn't write back to the DB. I'm seeing the light with disk json. So, it's not One Wide Table To Rule Them All :) |
11:14 |
|
collum joined #evergreen |
11:15 |
eeevil |
Bmagic: are you familiar with dimensional data modeling? I don't want to overexplain ... |
11:16 |
eeevil |
for the room, in any case, here's an overview: https://www.dataversity.net/fundamentals-of-dimensional-data-modeling/ (def search for more) |
11:16 |
Bmagic |
I appreciate your willingness to engauge, please go ahead. (no, I'm not deeply familiar, just the broad strokes) |
11:17 |
Bmagic |
reading |
11:18 |
eeevil |
a "dashboard" is just a display of the very "top" of the fact table, which is fast because it's indexed on time and we're only looking at the top sliver, aggregated over the chosen dimension(s) and fed into a chart renderer |
11:18 |
kmlussier |
A gentle reminder for those attending in Beverly, if you want to sign up for a dine-around, please do so soon. https://docs.google.com/spreadsheets/d/1hgXgFMonwykEd5hXnFk--DlPrDPhLEtj_dvYrhXxgjk/edit?usp=sharing |
11:21 |
eeevil |
if we build a DW-ized stats schema /inside/ evergreen (huh, look at that, there's a schema called "stats" ...) then we could just use standard fact-dimension patterns directly and get "correct" stats -- the dimensions are /definitionally/ updated with necessary values whenever the fact table is reified. |
11:21 |
Bmagic |
ok, that tracks |
11:22 |
eeevil |
now, the noble stats page demo'd is /not/ a dashboard, because it shows old stats and lets you compare between different snapshot sets. it IS a reporter |
11:24 |
Bmagic |
ok, so you're saying that a "dashboard" doesn't use non-dynamic snapshotted data? |
11:24 |
|
dguarrac joined #evergreen |
11:26 |
eeevil |
a true DW-style data store can support both. and it /is/ storing "copies" (but not really, it's complicated) in the db. |
11:27 |
|
smayo joined #evergreen |
11:27 |
Bmagic |
I like it. And I'm getting hip to the fact table informing the dimensions. |
11:27 |
eeevil |
and I'm FOR that, but only if it's based on the very well trod ground of data warehousing. |
11:28 |
eeevil |
the hard part is not the DB stuff, IMO |
11:28 |
|
collum joined #evergreen |
11:28 |
Bmagic |
what's the hard part then? Trends and data retension? Long-views? |
11:29 |
|
Dyrcona joined #evergreen |
11:30 |
eeevil |
the thing that lets you define the chart/graph. the parts that users touch. |
11:32 |
Bmagic |
scottangel has worked out a way to integrate charts and graphs without* additional dependencies. And the fact tables become the UI dropdowns. But I think I see what you're saying: the UI can* end up insane |
11:35 |
Bmagic |
like this UI conundrum: how would you present a UI that allows the user to create "I want a bar graph that compares the last 3 years of circs, per month, with three bars per month so I can see how we're doing compared to each month of the year" |
11:36 |
Bmagic |
And any permutation of that for each and every facet |
11:37 |
eeevil |
so, this just jogged something lose in my brain. I can't remember where (LP or mailing list), but there was recently a "how about we show venn-style join type icons insead of a checkbox in the report source tree" discussion. I think we can do that with just some CSS ... [he said, ducking out of sleary's line of sight] |
11:38 |
Bmagic |
I read that somewhere too, I think LP |
11:38 |
terranm |
smayo worked on that - it's bea-ooooo-tiful |
11:41 |
Bmagic |
eeevil: the UI work for the DW schema does seem gigantic. Are you "not for" the json to disk idea? |
11:41 |
smayo |
It's not just css but it IS a page-specific template, so all the logic for how the venn diagram works isn't actually part of the tree: https://bugs.launchpad.net/evergreen/+bug/2077460 |
11:41 |
pinesol |
Launchpad bug 2077460 in Evergreen "Angular Reporter (EG 3.13) - Nullability/Join Selection is Confusing" [Medium,Confirmed] |
11:42 |
eeevil |
Bmagic: those mockups linked above are the outcome of us doing the actual investigation into what it would take to build in a guardrail-restricted dashboard (NOT reporting, so not the historical noble version) for EG. I don't have external notes/specs available (I thought I did, but no), but it is a Big(tm) project |
11:43 |
Bmagic |
what was the conclusion for the data source? |
11:43 |
eeevil |
if we were to snapshot the (full) data daily or monthly, I don't know why we would do it in JSON |
11:44 |
eeevil |
for our previous (mocked up) proposal? in the database. but in standard, well understood DW patterns. thats different from "snapshot of the output of a query" though |
11:44 |
Bmagic |
the json idea lowers the processing needs for the middle layer. Handing the data back to the client essentially directly makes sense to me. The proposed eg-chart component can eat that directly, and sum up stuff, etc. |
11:46 |
eeevil |
I mean, why is json better than anything else (that already exists)? |
11:46 |
Dyrcona |
Well, JSON is serialized JavaScript, so if you're using JavaScript... |
11:47 |
Bmagic |
I'm liking the eg-chart component (as opposed to apache-style routing to integrate an pre-created image) for the chart. Plus it's accessible, with keyboard and screen reader |
11:49 |
eeevil |
smayo: would you be open to /not/ changing the internals of eg-tree (that's used all over, and its use will expand, so I fear breaking other stuff) and just having the checkbox rendered as a venn-ish image that changes from "left" to "inner" when you click it? |
11:52 |
|
dguarrac joined #evergreen |
12:04 |
Bmagic |
eeevil: json makes it so the chart can sum the data in different ways if we want to ignore some facets in the interface. JSON > CSV/HTML. I'm saying: make a new tool and a new folder structure that just writes data to disk (whatever format, json makes sense to me), and that data can be gathered up by the middle layer, and cached, and handed off to the client for charting with the guardrailed-restricted facets as per our outputs |
12:04 |
|
collum joined #evergreen |
12:11 |
eeevil |
"the middle layer, and cached, and handed off" is doing a lot of work. if we're going to reinvent the user-level wheels, let's get that working with mock data and then plug in a real feed of data later. don't assume /anything/ about how the data is stored, or where, or any of that. if we want a list of URLs that resolve to a blob of json each, great, but go no further than that on the back or middle layer. IMO |
12:11 |
Bmagic |
or maybe a table in the DB with the outputs. One-way.... yes, what you said |
12:13 |
Bmagic |
scottangel started at the UI level, so, we're already going down the suggested path |
12:25 |
|
smorrison joined #evergreen |
12:26 |
|
kmlussier left #evergreen |
12:27 |
|
abowling joined #evergreen |
12:28 |
|
dguarrac joined #evergreen |
12:29 |
|
collum joined #evergreen |
12:32 |
|
_collum joined #evergreen |
12:33 |
|
collum joined #evergreen |
12:36 |
|
redavis joined #evergreen |
12:37 |
|
collum joined #evergreen |
12:55 |
|
collum joined #evergreen |
12:56 |
|
collum joined #evergreen |
13:07 |
|
dguarrac joined #evergreen |
13:08 |
|
smorrison joined #evergreen |
13:09 |
Rogan |
dyrcona - thanks for heads up on lp1861239 - I've done a new commit with sign off and fixed newer merge conflict |
13:16 |
|
dguarrac joined #evergreen |
13:17 |
pinesol |
News from commits: Docs: Update copy_locations.adoc - deleted shelving locations filtered by default <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=c146197fbea9af19e320f702263cbabdbd070acb> |
13:23 |
|
dguarrac joined #evergreen |
13:46 |
|
smorrison joined #evergreen |
13:47 |
|
smayo joined #evergreen |
13:57 |
|
shulabramble joined #evergreen |
14:06 |
berick |
csharp_: https://github.com/kcls/evergreen-pub/wiki/KCLS-Rust-Migration |
14:07 |
shulabramble |
53 minute warning to the Dev meeting. |
14:11 |
|
dguarrac joined #evergreen |
14:22 |
|
jihpringle joined #evergreen |
14:43 |
|
dguarrac joined #evergreen |
14:45 |
shulabramble |
15 minute warning to the dev meeting |
14:46 |
|
sandbergja joined #evergreen |
14:50 |
shulabramble |
10 minutes to dev meeting |
14:52 |
berick |
jeff++ # *sigh* i just noticed your Hatch test notes in LP. |
14:52 |
berick |
accidentally marked that email read |
14:55 |
shulabramble |
5 minutes to dev meeting! |
14:56 |
|
smayo joined #evergreen |
14:58 |
jeff |
berick++ glad you saw it! |
14:59 |
jeff |
let me know if you want to work together any further on the release part. I don't have credentials or access to move it along afaik. |
15:00 |
shulabramble |
#startmeeting 2024-11-12 - Developer Meeting |
15:00 |
pinesol |
Meeting started Tue Nov 12 15:00:09 2024 US/Eastern. The chair is shulabramble. Information about MeetBot at http://wiki.debian.org/MeetBot. |
15:00 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
15:00 |
pinesol |
The meeting name has been set to '2024_11_12___developer_meeting' |
15:00 |
shulabramble |
Agenda is here: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2024-11-12 |
15:00 |
shulabramble |
#topic Introductions |
15:00 |
|
mantis joined #evergreen |
15:01 |
shulabramble |
#intro Shula Link, GCHRL |
15:01 |
abneiman |
#info abneiman - Andrea Buntz Neiman, Equinox |
15:01 |
shulabramble |
#info Shula Link, GCHRL |
15:01 |
sandbergja |
#info sandbergja = Jane Sandberg, PUL |
15:01 |
sleary |
#info sleary = Stephanie Leary, Equinox |
15:01 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
15:01 |
JBoyer |
#info JBoyer = Jason Boyer, EOLI |
15:01 |
|
collum joined #evergreen |
15:02 |
Dyrcona |
#info Dyrcona = Jason Stephenson, CW MARS |
15:02 |
phasefx |
#info phasefx = Jason Etheridge, EOLI |
15:02 |
jeff |
#info jeff = Jeff Godin, Traverse Area District Library (TADL) |
15:02 |
collum |
#info collum = Garry Collum, KCPL |
15:02 |
terranm |
#info terranm = Terran McCanna, PINES |
15:02 |
abneiman |
jeff: you have a twin staying at the hackaway hotel because I thought I saw you last night |
15:03 |
shulabramble |
People can keep doing intros as we get going. :) |
15:03 |
eeevil |
#info eeevil = Mike Rylander, EOLI |
15:03 |
berick |
#info berick Bill Erickson KCLS |
15:03 |
shulabramble |
#topic Actions |
15:03 |
smayo |
#info smayo = Steven Mayo, PINES |
15:03 |
csharp_ |
#info csharp, Chris Sharp, GPLS |
15:04 |
Bmagic |
#info Bmagic = Blake GH, MOBIUS |
15:04 |
|
tlittle joined #evergreen |
15:04 |
Rogan |
#info rogan, Rogan Hamby EOLI |
15:04 |
shulabramble |
#topic eeevil will open a bug for cross-column stats targets |
15:04 |
|
kmlussier joined #evergreen |
15:04 |
dguarrac |
#info dguarrac = Dan Guarracino, OWWL Library System |
15:04 |
kmlussier |
#info Kathy Lussier, NOBLE |
15:04 |
eeevil |
I have not, yet. |
15:05 |
scottangel |
#info scottangel = Scott Angel, MOBIUS |
15:05 |
shulabramble |
we'll punt it on down the road then unless there's some other discussion on that? |
15:05 |
eeevil |
"move on down, move on down the road" |
15:05 |
|
ianskelskey joined #evergreen |
15:06 |
eeevil |
(yes, let us punt it) |
15:06 |
shulabramble |
don't carry nothing that could be a load |
15:06 |
shulabramble |
#action eeevil will open a bug for cross-column stats targets |
15:06 |
shulabramble |
#topic gmcharlt - create a Git commit message type and update bug 2051946 |
15:06 |
pinesol |
Launchpad bug 2051946 in Evergreen "institute a Git commit message template" [Wishlist,New] https://launchpad.net/bugs/2051946 - Assigned to Galen Charlton (gmc) |
15:06 |
csharp_ |
@decide scottangel or eeevil |
15:06 |
pinesol |
csharp_: go with scottangel |
15:07 |
abneiman |
I don't think gmcharlt is available for this meeting |
15:07 |
shulabramble |
okay then. |
15:07 |
shulabramble |
#action gmcharlt - create a Git commit message type and update bug 2051946 |
15:07 |
pinesol |
Launchpad bug 2051946 in Evergreen "institute a Git commit message template" [Wishlist,New] https://launchpad.net/bugs/2051946 - Assigned to Galen Charlton (gmc) |
15:08 |
shulabramble |
#topic waiting on gmcharlt for access to POEditor for git integration |
15:08 |
shulabramble |
And I assume the same for this unless there's any discussion to be had? |
15:08 |
abneiman |
I will ping gmcharlt in our channel about that 2nd one since Dyrcona is awaiting access |
15:09 |
shulabramble |
abneiman++ |
15:09 |
shulabramble |
#action waiting on gmcharlt for access to POEditor for git integration |
15:09 |
shulabramble |
#topic sleary and sandbergja will report progress on test writing wiki pages next month / at hackaway |
15:10 |
|
smorrison joined #evergreen |
15:10 |
sandbergja |
ooh! We did some work in the wiki. We haven't had a chance to coordinate something for the hackaway |
15:10 |
sleary |
I have not made much progress on my part of that, so let's kick that to next month, please! |
15:10 |
abneiman |
sandbergja++ sleary++ |
15:10 |
shulabramble |
sandbergja++ sleary++ got it |
15:11 |
shulabramble |
and a belated eeevil++ |
15:11 |
shulabramble |
#action sleary and sandbergja will report progress on test writing wiki pages next month / at hackaway |
15:11 |
sandbergja |
very happy if people discuss tests at hackaway though :-D |
15:11 |
shulabramble |
#topic bug 2076921 expected to get more testing and merged, and beta uploaded to store |
15:11 |
pinesol |
Launchpad bug 2076921 in Evergreen "Hatch: Chrome Extension Requires Redevelopment" [High,Confirmed] https://launchpad.net/bugs/2076921 - Assigned to Jeff Godin (jgodin) |
15:12 |
berick |
jeff did some testing, many thanks |
15:12 |
shulabramble |
jeff++ |
15:12 |
abneiman |
jeff++ |
15:12 |
sandbergja |
jeff++ |
15:12 |
Bmagic |
jeff++ |
15:13 |
berick |
there's one cosmetic issue I may try to address, but regardless we should plan the roll out |
15:13 |
berick |
to the chrome store |
15:13 |
sleary |
jeff++ berick++ |
15:13 |
shulabramble |
berick++ |
15:13 |
mmorgan |
jeff++ |
15:13 |
abneiman |
berick:++ |
15:13 |
mmorgan |
berick++ |
15:13 |
berick |
i'm not 100% on what all the options are for partial roll outs, so research needed there |
15:13 |
Dyrcona |
jeff++ berick++ |
15:14 |
shulabramble |
hooray! that's good news. |
15:14 |
sandbergja |
berick++ |
15:14 |
shulabramble |
moving along at a fair clip |
15:15 |
shulabramble |
do we need an action meeting on this for next month? |
15:15 |
berick |
shulabramble: for the Hatch stuff? |
15:15 |
shulabramble |
aye. |
15:15 |
kmlussier |
jeff++ berick++ |
15:15 |
berick |
yeah.. i'll take on figuring out a roll out plan |
15:15 |
shulabramble |
berick++ |
15:16 |
berick |
also, hopefully not necessary, but if Google forces our hand, we'll just roll out... I'm guessing |
15:16 |
shulabramble |
#action berick will work on a rollout plan for hatch update -- bug 2076921 |
15:16 |
pinesol |
Launchpad bug 2076921 in Evergreen "Hatch: Chrome Extension Requires Redevelopment" [High,Confirmed] https://launchpad.net/bugs/2076921 - Assigned to Jeff Godin (jgodin) |
15:16 |
shulabramble |
#topic Timing of string freezes w/r/t point releases |
15:16 |
abneiman |
that was me so please stand by for wall of text |
15:17 |
* shulabramble |
cedes the floor. |
15:17 |
abneiman |
I emailed several in our translations group (Linda, Eva, Jane, and Jennifer Pringle) suggesting a couple options, to wit: |
15:17 |
abneiman |
1) Adding translations in the next point release - e.g., translations for 3.13.4 will go in as part of 3.13.5 |
15:17 |
abneiman |
2) Proactively notifying translators of merged bugs with translation strings needed |
15:17 |
abneiman |
3) Calling for a mini "string freeze" a few days before the general point release freeze is called. |
15:18 |
abneiman |
the general consensus was that 2 is preferable-but-more-challenging and 3 is also OK |
15:18 |
pinesol |
News from commits: Docs: Update linked_libraries.adoc with upcoming closures info <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=06b19c1b470b968929762194e77a0a44d29dc1f3> |
15:18 |
abneiman |
We are trying to schedule a discussion for hackaway but getting the timing that will work for both Czeckia and PST is challenging |
15:18 |
abneiman |
so, that's my report if anyone has any questions / comments / thoughts, I cede the floor back :) |
15:19 |
abneiman |
and I guess all of that should've been under an info tag so |
15:20 |
abneiman |
#info please see the preceding several lines in the transcript for information on translation timing for point release |
15:20 |
shulabramble |
abneiman++ |
15:20 |
sandbergja |
abneiman++ |
15:20 |
jeff |
abneiman++ |
15:20 |
Dyrcona |
abneiman++ |
15:20 |
sleary |
would a new LP tag be helpful for denoting bugs that involve string changes? |
15:20 |
kmlussier |
abneiman++ |
15:21 |
abneiman |
sleary: yes, I think so. And it's a small concrete step that we can take :) |
15:22 |
shulabramble |
sleary: volunteering to make that new tag? :) |
15:23 |
sleary |
sure |
15:23 |
sandbergja |
sleary++ |
15:24 |
shulabramble |
#action sleary will make a new LP tag denoting bugs that involve string changes |
15:24 |
shulabramble |
sleary++ |
15:24 |
jeffdavis |
Do we have automated testing (or some such thing) to flag when a string has been added/changed? |
15:24 |
abneiman |
sleary++ |
15:24 |
shulabramble |
jeffdavis++ for the question |
15:25 |
abneiman |
jeffdavis: I do not know - sandbergja? sleary? |
15:25 |
sleary |
I do not know of any automated ways to do that at the moment |
15:26 |
sandbergja |
jeffdavis: I'm not aware of anything. I don't think that the translation files we generate are very easy to compare, at least on the PO side. |
15:26 |
sandbergja |
lots of timestamps and line number changes hide the actual string changes |
15:26 |
sandbergja |
not that it couldn't be done! |
15:27 |
sandbergja |
on the angular side it might be a bit easier |
15:28 |
shulabramble |
anyone want to look into the feasibility of that probable regex festival? |
15:28 |
jeff |
it's not a boring problem. what output/actions would be useful if we had such testing/monitoring? |
15:29 |
shulabramble |
(to be clear, I love regex problems, so that's a *good* thing) |
15:29 |
abneiman |
@band add Probably Regex Festival |
15:29 |
pinesol |
abneiman: Band 'Probably Regex Festival' added to list |
15:29 |
phasefx |
for angular at least, the build process tells us when strings aren't translated (at all?). I'm not sure how it works or if it's reliable, fwiw |
15:29 |
Dyrcona |
shulabramble: Now, you've got 2 problems. |
15:30 |
sandbergja |
jeff: good question. I don't know -- send an email to translators? |
15:31 |
sandbergja |
(but maybe not send them a new email every single time a typo is corrected?) |
15:31 |
sandbergja |
it seems like a question for the translators maybe |
15:32 |
abneiman |
if we can get a meeting scheduled at hackaway we can pose said question |
15:32 |
abneiman |
jihpringle is the only one I see in channel right now |
15:33 |
shulabramble |
it's a thing for discussion, at the least. we can come back to it in December after translator feedback? |
15:33 |
abneiman |
sure |
15:34 |
jihpringle |
if it's going to send emails we'd need a way to specify what we want the emails for (currently we only translate the OPAC) |
15:34 |
shulabramble |
jeff++ abneiman++ jihpringle++ |
15:34 |
shulabramble |
phasefx++ |
15:35 |
abneiman |
jihpringle++ |
15:35 |
shulabramble |
#action revisit feasibility of automated testing for string changes |
15:36 |
shulabramble |
alrighty, moving on |
15:36 |
shulabramble |
#topic Updates |
15:36 |
shulabramble |
There's nothing on the agenda for these, but I know we had an Evergreen update since the last meeting. |
15:37 |
shulabramble |
so 3.14 release team++ |
15:37 |
Bmagic |
+1 |
15:37 |
phasefx |
release_team++ |
15:38 |
shulabramble |
is it time to assemble a 3.15 release team? |
15:39 |
phasefx |
still think it should be 3.145 |
15:39 |
Dyrcona |
No, it's time to assemble a 4.0 release team. |
15:39 |
shulabramble |
dyrcona++ |
15:39 |
abneiman |
I believe the 3.15/4.0 release team appointment will happen this week at hackaway |
15:39 |
shulabramble |
abeneiman++ |
15:40 |
shulabramble |
abneiman++ |
15:40 |
shulabramble |
Next up: Launchpad Status was not updated on the Agenda. |
15:41 |
mmorgan |
shulabramble: did you reload? |
15:41 |
* Dyrcona |
volunteers for OpenSRF 4.0 release. |
15:41 |
shulabramble |
mmorgan: yes |
15:42 |
mmorgan |
Oops, updated the wrong page, I think. |
15:42 |
shulabramble |
mmorgan++ it happens :) |
15:43 |
sandbergja |
Dyrcona++ |
15:43 |
sandbergja |
mmorgan++ |
15:43 |
shulabramble |
dyrcona++ |
15:43 |
Bmagic |
Dyrcona++ |
15:45 |
shulabramble |
Wall of text incoming! |
15:45 |
shulabramble |
#topic Launchpad Status (as of noon Eastern) |
15:46 |
shulabramble |
#info Open Bugs - 3108 |
15:46 |
shulabramble |
#info Pullrequests - 93 |
15:46 |
shulabramble |
#info Signedoff - 13 |
15:47 |
shulabramble |
#info Needswork - 82 |
15:47 |
shulabramble |
#info Needstestplan - 3 |
15:47 |
shulabramble |
#info Needsrebase - 24 |
15:47 |
shulabramble |
#topic Launchpad Updates Since Last Meeting |
15:47 |
shulabramble |
#info Bugs Added - 76 |
15:47 |
shulabramble |
#info Pullrequest tag Added - 25 |
15:47 |
shulabramble |
#info Signedoff tag Added - 21 |
15:48 |
shulabramble |
#info Needswork tag Added - 0 |
15:48 |
shulabramble |
#info Needstestplan tag added - 0 |
15:48 |
shulabramble |
#info needsrebase tag added - 0 |
15:48 |
shulabramble |
#info Fix Committed - 20 |
15:48 |
shulabramble |
mmorgan++ thank you :) |
15:49 |
shulabramble |
#topic New Business |
15:49 |
shulabramble |
#topic Discussion of IRC as home of meetings vs. video or an alternative text platform (abneiman) |
15:49 |
abneiman |
hi again |
15:49 |
abneiman |
It's hackaway and I'm throwing that bomb |
15:49 |
sandbergja |
ker blam |
15:49 |
abneiman |
but, more seriously, this came up in the Outreadh discussion earlier today |
15:50 |
abneiman |
AFAIK all other community meetings are now held on zoom or other video chat |
15:50 |
abneiman |
I understand that many of us are text-driven people |
15:50 |
abneiman |
I understand that there are concerns about transparency |
15:50 |
abneiman |
BUT! I also consider IRC to be unfriendly and a barrier to especially new participants |
15:50 |
berick |
for this, we're just talking meetings? not wholesale irc replacement? |
15:50 |
abneiman |
so I'd like y'all, the developers, to consider moving dev meetings out of IRC into an video platform |
15:51 |
abneiman |
A wholesale IRC replacement could also be discussed (slack, discord, etc.) but my particular bone to pick is text based meetings :) |
15:51 |
sleary |
berick wholesale IRC replacement is a different discussion that we also need to have; this is just about dev meetings |
15:51 |
terranm |
+1 |
15:51 |
berick |
considering every meeting I ever do for work is a video meeting.. i'm fine with it |
15:52 |
Dyrcona |
I have a concern with a F/OSS project using proprietary software for meetings or infrastructure. |
15:52 |
|
redavis joined #evergreen |
15:52 |
abneiman |
obviously, shulabramble, as current head of the dev meetings your opinion is key here as well |
15:52 |
kmlussier |
In terms of transparency concerns, could we post the Zoom transcripts? |
15:52 |
sleary |
we use proprietary software for many other things at this point, so I don't feel that we need to make that a priority among our considerations |
15:53 |
abneiman |
+1 to Zoom transcripts |
15:53 |
shulabramble |
if so, i'll have to cede running the meetings; my current work setup restricts my ability to do video meetings as the Monday group can attest. |
15:53 |
abneiman |
hmmm |
15:53 |
sleary |
+1 to transcripts |
15:53 |
sandbergja |
There is also jitsi, if we want to use video meeting but use open source software |
15:54 |
Bmagic |
I'm fine with video meetings. I assume we've already jumped the account ownership hurdle? |
15:54 |
ianskelskey |
Im all for no more IRC |
15:54 |
shulabramble |
if the consensus is moving to Zoom or another platform, I'm fine handing over the reigns. |
15:54 |
Bmagic |
Ianskelskey: haha, one step at a time |
15:54 |
csharp_ |
I'm a pragmatist, so I'm okay with majority rule, but Dyrcona is correct that it's kind of a bad look for a F/LOSS project to use proprietary stuff |
15:54 |
ianskelskey |
It is unfriendly for new devs. |
15:54 |
sleary |
Bmagic the org has a Zoom account that are used for most of the other meetings |
15:54 |
* shulabramble |
has a sentimental attachment to IRC but agrees it's a barrier. |
15:55 |
abneiman |
I would like us to seriously consider it, especially since we (including the TEP board) has been meeting on the community Zoom account for quite some time now |
15:55 |
Bmagic |
gotcha, no problem with the account and sharing credentials, and scheduling I assume then? |
15:55 |
csharp_ |
we've already broken that seal, but this kind of drift is what happens |
15:55 |
sleary |
Bmagic right |
15:55 |
Bmagic |
cool, I vote zoom then |
15:55 |
Bmagic |
(because it's already setup) |
15:55 |
shulabramble |
csharp_++ |
15:55 |
ianskelskey |
And I think the onboarding process for new devs is one of our big weaknesses. Evergreen could be a great first open source contribution for students, new devs etc, but getting into it is kind of a nightmare. |
15:56 |
abneiman |
THIS ^^ is a problem we know we have |
15:56 |
sleary |
+1 |
15:56 |
terranm |
+1 |
15:56 |
smayo |
+1 |
15:56 |
ianskelskey |
Well. There it is from the perspective of a new dev |
15:56 |
tlittle |
+1 |
15:56 |
redavis |
ianskelskey++ |
15:56 |
* phasefx |
buries his EG2Gopher project |
15:56 |
abneiman |
And NewDevs group has done amazing work here, but trying to connect with other devs is an area where we could be better - sharing knowledge etc. is ALSO a big part of open source |
15:57 |
Bmagic |
phasefx: lol |
15:57 |
shulabramble |
ianskelskey -- it might be interesting to hear some other barriers you've noticed. |
15:57 |
Bmagic |
isn't newdev meetings held via zoom already? |
15:57 |
sandbergja |
I am not a fan of IRC, but it would be a shame to exclude shulabramble :-( |
15:57 |
sleary |
Bmagic yes |
15:57 |
shulabramble |
as i don't think IRC is one of the biggest hurdles. |
15:58 |
abneiman |
I do not want to exclude shulabramble either. And there is a text component to zoom / other video platforms but I get that it's hard for someone to run a meeting that way |
15:58 |
sleary |
Including people who participate by text is something we discussed quite a bit in Outreach! We do want to make sure that those folks can still participate (and even lead meetings)! The text chat feature in Zoom is pretty solid. |
15:58 |
shulabramble |
It's solid, but people have to actively remember to look at it. |
15:58 |
sleary |
that is true |
15:59 |
shulabramble |
and, as someone who prefers text-based communication, it's not great. it's meant to augment video communication, not be a parallel mode of primary communication in Zoom. |
15:59 |
Bmagic |
all* of the other Evergreen meetings are using our Zoom account? The only one left is the dev meeting? |
16:00 |
abneiman |
well, I don't know if it's time to call for a vote, but I did want to start the conversation and I appreciate all y'all's thoughts |
16:00 |
sleary |
Bmagic New Devs and Outreach sometimes use Google Meet. All the others use Zoom as far as I know. |
16:00 |
abneiman |
I think Outreach uses google meet |
16:00 |
sleary |
My thought was that we'd put out a survey to the devs list |
16:00 |
Bmagic |
it makes is seem like IRC is "reserved" for devs then |
16:01 |
smayo |
Can confirm I've been scared to post in IRC because I didn't know enough yet |
16:01 |
sleary |
:( |
16:01 |
Bmagic |
I felt the same way smayo |
16:01 |
abneiman |
I guess the real issues is that I find video meetings to be more productive than text meetings |
16:02 |
mmorgan |
IRC is def intimidating for some |
16:02 |
abneiman |
IMNSHO |
16:02 |
Bmagic |
I agree that when it comes to meetings, seeing faces goes a long way to convey whatever it is you're trying to convey |
16:02 |
shulabramble |
I'm an ancient of the internet; I was on IRC back as a teenager 30 years ago good lord... |
16:02 |
terranm |
Trying to communicate anything complicated is difficult in short texts |
16:02 |
abneiman |
and, since onboarding new devs is a prolem we know we have, I'd really like us to consider having dev meeting ELSEWHERE |
16:02 |
eeevil |
if zoom had an option where it didn't open 42 windows, most duplicated for SOME REASON, I could be convinced |
16:03 |
csharp_ |
(not being confrontational...) would people feel more confident posting in this chat, just on Slack or similar? |
16:03 |
csharp_ |
like the content of the chat wouldn't be that different, no? |
16:03 |
Bmagic |
csharp_: I think you're right, but that might be a different discussion |
16:04 |
JBoyer |
lobbin' some bombs because I was encouraged to mention some options: Mattermost is a good slack-like that can be self-hosted and Koha has already moved to it. Matrix is more complicated to setup / use I think but I use it for some personal stuff. |
16:04 |
Bmagic |
Or are you proposing the dev meeting remain in text format, but just on a different platform? |
16:05 |
redavis |
Are we saying that we'd like to commit to supporting a self-hosted communication tool in addition to other community stuff? |
16:05 |
csharp_ |
JBoyer: we just talked about Mattermost/Matrix at our table too |
16:05 |
csharp_ |
now we're raging against Teams |
16:05 |
eeevil |
re slack, I'd prefer free (both senses), but if some org (like TEP???) to pay for non-truncating slack, that'd be great |
16:05 |
eeevil |
but mattermost++ |
16:06 |
phasefx |
shulabramble: I remember telnet talkers, too |
16:06 |
abneiman |
but, it's also the top of the hour and I know sandbergja has a pending new biz item too. So, I can commit to making a survey for the dev list about meeting locations. |
16:06 |
Bmagic |
this seems to be shifting to non-meeting platforms? Or am I misunderstanding? |
16:06 |
redavis |
Slack would cost approximately $120 for the pro version with not-for-profit pricing. |
16:06 |
csharp_ |
suggestion: set up a mattermost instance in EC2 or similar |
16:06 |
redavis |
annually |
16:06 |
shulabramble |
abneiman++ |
16:06 |
csharp_ |
redavis: very reasonable |
16:06 |
Dyrcona |
#action csharp to setup mattermost on EC2 |
16:06 |
terranm |
I think the issue is that text-based just isn't as welcoming as video/screen-sharing based. Switching to a different text-based system wouldn't help. |
16:06 |
Bmagic |
lol |
16:07 |
abneiman |
agreed with terranm |
16:07 |
mmorgan |
also agree |
16:08 |
collum |
Could we try a video/screen-sharing meeting, just once, to see how it goes? |
16:08 |
Bmagic |
I agree with video platform for meetings. Does mattermost accomodate? |
16:08 |
sleary |
Is there a compelling reason to try out other platforms when we already have Zoom? |
16:08 |
Bmagic |
right, what sleary said |
16:08 |
|
smayo joined #evergreen |
16:09 |
Dyrcona |
sleary: Probably not so much. |
16:09 |
eeevil |
sleary: because zoom is the worst? /me ducks |
16:09 |
shulabramble |
how about we let abneiman do a survey and we can discuss on listserv? |
16:09 |
abneiman |
+1 |
16:09 |
Bmagic |
I agree with eeevil about the suckage of zoom. But it's not a hill I'm willing to die on |
16:10 |
tlittle |
I think we're having two different conversations and somewhat mixing them up: moving away from IRC for chat talking vs moving to a video meeting platform specifically for meetings |
16:10 |
abneiman |
tlittle: yes, I think they're worthy of separate listserv convos |
16:10 |
Rogan |
and I think this topic is about the meetings |
16:10 |
abneiman |
my concern here is THIS meeting |
16:10 |
shulabramble |
video chat is my ancient enemy, but this isn't me running a CotC game. |
16:10 |
shulabramble |
We're past the hour, and still have another topic to discuss, so how about we go with: |
16:11 |
Bmagic |
All* video platforms suffer from the same basic issue: the audio... the video.. the mute, everyone needs to click all the buttons and be familiar. zoom, fine |
16:11 |
shulabramble |
#action abneiman will poll concerning moving the developer's meeting from IRC to a different platform |
16:11 |
shulabramble |
and we can discuss that on the listserv |
16:11 |
abneiman |
shulabramble++ # wranglin |
16:12 |
berick |
shulabramble++ |
16:12 |
redavis |
shulabramble++ |
16:12 |
Bmagic |
shulabramble++ |
16:12 |
redavis |
abneiman++ |
16:12 |
sandbergja |
shulabramble++ |
16:12 |
sandbergja |
abneiman++ |
16:12 |
shulabramble |
abneiman++ |
16:12 |
shulabramble |
I own four cats. I have experience. |
16:12 |
scottangel |
shulabramble++ |
16:12 |
shulabramble |
#topic Okay to merge LP 2055796? berick mentioned "unclear if there's any additional decision processes re: adding github actions" |
16:12 |
pinesol |
Launchpad bug 2055796 in Evergreen "Have github actions run pgtap tests for us" [Undecided,Confirmed] https://launchpad.net/bugs/2055796 - Assigned to Bill Erickson (berick) |
16:12 |
smayo |
shulabramble++ |
16:12 |
shulabramble |
sandbergja? |
16:12 |
sandbergja |
yes, pasting some text |
16:13 |
sandbergja |
The back story: we used to have our tests automatically running regularly (2x/day?), and alerting IRC if there was a test failure. This has not worked for some time, so currently we don't find out about those bugs we've added to Evergreen until somebody runs the tests manually (which may be a while later). Github offers free infrastructure for running tests, so a year ago, we decided to explore |
16:13 |
sandbergja |
I have a pull request to get our pgtap (database) tests running automatically on github actions, berick has reviewed it but mentioned "unclear if there's any additional decision processes re: adding github actions". |
16:13 |
sandbergja |
I figured this was the place to ask. :-) |
16:13 |
phasefx |
testing would be easier with simpler installations... *runs away* |
16:13 |
sandbergja |
phasefx++ |
16:14 |
sandbergja |
100% agree |
16:14 |
redavis |
phasefx++ #also hahahahahah |
16:14 |
shulabramble |
phasefx++ |
16:14 |
smayo |
Bmagic++ docker |
16:14 |
sandbergja |
trying to install an eg-compatible ejabberd in github actions has me totally stumped |
16:14 |
sandbergja |
so I can't wait for redis to be merged |
16:14 |
sandbergja |
but I'm getting off topic hahaha |
16:15 |
berick |
any objections to running pgtap tests via github actions? going once? |
16:15 |
Bmagic |
berick says "strong +1 to merging" |
16:15 |
Bmagic |
no objections at all |
16:15 |
phasefx |
no objections to anyone maintaining testing infrastructure |
16:16 |
abneiman |
tests++ |
16:16 |
berick |
didn't think so, but it's kind of new, so.. |
16:16 |
berick |
sandbergja++ |
16:16 |
shulabramble |
sandbergja++ |
16:16 |
redavis |
sandbergja++ |
16:16 |
sandbergja |
berick++ # thanks for the review! |
16:16 |
abneiman |
sandbergja++ berick++ |
16:16 |
jeff |
other than there being some github-specific metadata files in the repo, is there any practical effect/impact that you're concerned about? |
16:17 |
berick |
jeff: nope, just covering bases |
16:17 |
mmorgan |
sandbergja++ |
16:17 |
jeff |
good deal! |
16:17 |
jeff |
sandbergja++ berick++ |
16:17 |
redavis |
berick++ |
16:18 |
shulabramble |
berick++ |
16:18 |
phasefx |
berick: just main? |
16:18 |
Bmagic |
I find it interesting that the server upon which the test run, presumabely don't have the perl dependencies? But that's fine for the scope of the tests? |
16:18 |
* phasefx |
belatedly pulls up the ticket |
16:19 |
shulabramble |
#action it is okay to merge lp2055796, sandberg and berick will attend |
16:19 |
shulabramble |
wrangling before we go a full half hour over |
16:19 |
shulabramble |
#topic Announcements |
16:20 |
berick |
phasefx: yes just main |
16:20 |
berick |
i'm assuming, anyway |
16:20 |
sandbergja |
I just want it merged somewhere :-D |
16:20 |
shulabramble |
#info Next Dev Meeting on 2024-12-10 |
16:20 |
shulabramble |
Any other announcements? |
16:20 |
|
redavis joined #evergreen |
16:21 |
Bmagic |
Evergreen rocks |
16:21 |
mantis |
Bmagic++ |
16:21 |
shulabramble |
bmagic++ |
16:21 |
Bmagic |
:) |
16:21 |
shulabramble |
#info "Evergreen Rocks" -- bmagic, 2024-11-12 |
16:22 |
abneiman |
so say we all |
16:22 |
* berick |
salutes |
16:22 |
Dyrcona |
shulabramble++ |
16:22 |
shulabramble |
so mote it be, y'all. and if there's nothing further. |
16:22 |
shulabramble |
#endmeeting |
16:22 |
pinesol |
Meeting ended Tue Nov 12 16:22:44 2024 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
16:22 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2024/evergreen.2024-11-12-15.00.html |
16:22 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2024/evergreen.2024-11-12-15.00.txt |
16:22 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2024/evergreen.2024-11-12-15.00.log.html |
16:22 |
mmorgan |
shulabramble++ |
16:22 |
|
mantis left #evergreen |
16:23 |
Bmagic |
shulabramble++ |
16:23 |
abneiman |
shulabramble++ |
16:23 |
sleary |
shulabramble++ |
16:24 |
kmlussier |
shulabramble++ |
16:26 |
sandbergja |
Bmagic: correct, it doesn't have all the Perl dependencies (becuase I couldn't figure out how to install the perl dependencies without also installing OpenSRF, and couldn't figure out how to install OpenSRF with ejabberd in github actions...) It just installs the postgres dependencies and libdbi-perl: https://github.com/sandbergja/Evergreen/blob/11c4c04137506a4a7cfd1f7de6eb433e5ccf64b3/.github/wo |
16:26 |
Bmagic |
pretty neat |
16:27 |
Bmagic |
I'm not surprised that we would have issues automating third party tools to install Evergreen. It's a, uh, weird installation, as we all know (and love?). |
16:28 |
sandbergja |
heh |
16:40 |
|
smorrison joined #evergreen |
16:43 |
|
kworstell-isl joined #evergreen |
16:47 |
|
mmorgan left #evergreen |
17:08 |
|
jihpringle joined #evergreen |
17:24 |
|
kmlussier joined #evergreen |
17:40 |
jeffdavis |
Speaking of installing OpenSRF, I wonder if we should be putting bug 2032835 on the 4.0 roadmap |
17:40 |
pinesol |
Launchpad bug 2032835 in OpenSRF "Discussion: Merge OpenSRF Into Evergreen?" [Wishlist,New] https://launchpad.net/bugs/2032835 |
17:41 |
sandbergja |
+1 |
17:42 |
Bmagic |
+1 |
17:48 |
pinesol |
News from commits: LP2055796: run pgtap tests on Github Actions <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=7e83c5de8ca1e7530853878bc7562d961ce348c4> |
17:50 |
Bmagic |
sandbergja++ berick++ |
18:08 |
|
phasefx joined #evergreen |
18:08 |
|
abneiman joined #evergreen |
18:08 |
|
sleary joined #evergreen |
18:19 |
|
kmlussier left #evergreen |
19:32 |
|
jihpringle joined #evergreen |
19:38 |
|
dguarrac joined #evergreen |