Time |
Nick |
Message |
04:13 |
|
mnsri_ joined #evergreen |
05:01 |
pinesol_green |
Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
05:14 |
|
sarabee joined #evergreen |
07:31 |
|
graced joined #evergreen |
07:39 |
|
jboyer-isl joined #evergreen |
07:42 |
|
ericar joined #evergreen |
07:46 |
|
collum joined #evergreen |
08:12 |
miker |
so, that test failure is due to a postgres bug fix which, by the way, we desperately want: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=79af9a1d2668c9edc8171f03c39e7fed571eeb98 |
08:12 |
miker |
I'll adjust the test to match modern PG, because everyone should upgrade to the most recent minor version in any case :) |
08:25 |
dbwells |
miker: Thanks for the commit link, I've been wondering about the history behind the change. Do you think it's going to cause problems for some of our uses? It seems like in some cases we actually just want an XML fragment, since we're going to insert into another record or whatnot. |
08:25 |
miker |
no, the fix is going to allow us to simplify all /sorts/ of xpath-using code |
08:27 |
dbwells |
Ah, I wasn't really thinking that direction. There are a bunch of places where we have to dance around not having a proper namespace. |
08:27 |
miker |
before that fix we have to write things like [local-name()="subfield"] because sometimes there's a namespace bound to the node (if we're looking at a full marcxml doc) and sometimes not (if we're looking at the result of an xpath expr) |
08:27 |
miker |
right |
08:28 |
miker |
current code will always work, but we can make it more correct and self-documenting, and much easier to read, in addition to that |
08:29 |
miker |
it's never wrong to have a redundant namespace declaration (if it's the same and simply redundant), but it's always wrong to "forget" the namespace of an element that you get from an xpath expr |
08:29 |
dbwells |
yes, that's great. Thanks for opening my eyes a bit. |
08:30 |
miker |
(being over-explain-y for the room and history ;) ) |
08:30 |
dbwells |
I still worry a bit about seeing manipulated records with a bunch of extra namespaces cluttering things, but like you say, that's cosmetic if it happens, and probably pretty easy to fix-up if it becomes an issue. |
08:32 |
miker |
I look at it like this: it's just space, which is cheap ... and, while I've certainly been known to do it, and it's currently much faster, munging xml via regex is still wrong and shameful |
08:33 |
dbwells |
but it's so fast! ;) |
08:33 |
|
Dyrcona joined #evergreen |
08:35 |
miker |
Dyrcona: sorry to pounce immediately, but I have a fix for the test failure, and as RM[aintainer] I'll just ask you: shall I wait for launchpad to load, create a bug, push a branch, and update the bug, or just push the test fix to master? :) |
08:36 |
Dyrcona |
That's what has typically been done with test fixes so far, so I'd say yes. |
08:36 |
miker |
you mean push to master? |
08:36 |
Dyrcona |
No, I mean create a bug on launchpad, etc. |
08:37 |
miker |
k |
08:38 |
dbwells |
miker: I'm happy to sign off based on what I already know about the situation, so the bug report can be pretty "lite" :) |
08:38 |
|
mmorgan joined #evergreen |
08:40 |
dbwells |
Maybe a small consolation. |
08:40 |
Dyrcona |
Well, I don't think we need much for fixing tests. Something like "test [blah] is broken, this should fix it." |
08:41 |
|
maryj joined #evergreen |
08:43 |
miker |
dbwells: bug 1496837 at ya', and thanks! |
08:43 |
pinesol_green |
Launchpad bug 1496837 in Evergreen "xml-related test is invalid" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1496837 |
08:45 |
|
mrpeters joined #evergreen |
08:47 |
pinesol_green |
[evergreen|Mike Rylander] LP#1496837: Postgres fixed a bug and broke our test - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=b06b541> |
08:47 |
dbwells |
dang, forgot the -s to sign-off. |
08:58 |
|
rjackson_isl joined #evergreen |
09:08 |
miker |
dbwells++ |
09:09 |
dbwells |
Dyrcona: bshum: berick: I went ahead and created LP milestones for 2.7.9, 2.8.5, and 2.9.1, because I needed them, but I left the other active ones as-is. Just a heads up. |
09:14 |
|
yboston joined #evergreen |
09:15 |
jeff |
hrm. there was at least one time recently where i had to use local-name in xpath and thought i had come to the conclusion that it was unavoidable in some (otherwise correct) context. |
09:16 |
jeff |
though i could be mistaken -- it was a very quick-and-dirty script to begin with. |
09:20 |
Dyrcona |
dbwells: Thanks. I was going to get around to moving bugs as the bug maintainer later. |
09:22 |
kmlussier |
miker++ dbwells++ |
09:35 |
Dyrcona |
kmlussier: I am going to build a new development vm and I will add berick's latest branch for "Angularize the Patron Editor." |
09:36 |
Dyrcona |
Now that 2.9.0 is out the door, I don't feel compelled to stick to just master and our local customizations. |
09:36 |
kmlussier |
Dyrcona++ Thanks! |
09:36 |
Dyrcona |
Is today supposed to be Angular day? |
09:38 |
kmlussier |
Looks like it! |
09:39 |
kmlussier |
Dyrcona: Speaking of special days, since I never scheduled a bug squashing day before the .0 release I was thinking it might be good to shoot for one before the next point release. So that 2.9.1. can be even better. |
09:39 |
Dyrcona |
That would be nice. |
09:45 |
pinesol_green |
[evergreen|Remington Steed] Docs: Apache config includes examples for "no image" - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=729a4b2> |
09:50 |
bshum |
dbwells++ # milestone wrangling. |
09:50 |
bshum |
I think we can close all the last round. |
09:59 |
gmcharlt |
Dyrcona: it sure is, and I fell down on the ball actually preparing for it |
10:00 |
gmcharlt |
I'll be available and willing to pitch in and answer questions... but I'll also doing a bigger-actually-prepared-for-it day in October |
10:12 |
|
mnsri joined #evergreen |
10:16 |
* dbwells |
can't decide if "fell down on the ball" is a mixed metaphor or a more extreme sports-related idiom of some kind :) |
10:17 |
* dbwells |
also generally loves mixed metaphors |
10:19 |
berick |
i'm a pro at extreme falling |
10:26 |
|
Christineb joined #evergreen |
11:00 |
Dyrcona |
Dunno what is going on exactly at the moment, but I got a 503 when trying to download the access handler for nsis from nsis.sourceforge.net. |
11:00 |
Dyrcona |
This is probably temporary. |
11:01 |
Dyrcona |
It will affect anyone trying to build a Windows client with updates or with the permachine configuration options. |
11:02 |
gmcharlt |
dbwells: it's the literal truth in my case :) |
11:05 |
jeff |
some kind of sports-related office ball chair injury has prevented gmcharlt from preparing? :-) |
11:06 |
gmcharlt |
just recovering from a case of extreme punnery inflicted by miker earlier this week ;) |
11:10 |
berick |
get thee to a punnery |
11:10 |
phasefx |
let's not get into that habit |
11:11 |
* berick |
chuckles |
11:11 |
phasefx |
we'll be nun too happy |
11:16 |
kmlussier |
csharp: Can I remvoe you as the assignee from https://bugs.launchpad.net/evergreen/+bug/1402018? |
11:16 |
pinesol_green |
Launchpad bug 1402018 in Evergreen "Acq Copy location UI scoped to registered workstation" (affected: 2, heat: 16) [Undecided,New] - Assigned to Chris Sharp (chrissharp123) |
11:17 |
kmlussier |
Would somebody be able to update the 2.8 release notes page at http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_8.html with the changes I committed yesterday. |
11:18 |
kmlussier |
I feel bad about the acknowledgements I omitted, plus the weird issue with the top header is driving me batty. |
11:18 |
|
sandbergja joined #evergreen |
11:22 |
kmlussier |
@seen csharp |
11:22 |
pinesol_green |
kmlussier: csharp was last seen in #evergreen 1 day, 21 hours, 14 minutes, and 23 seconds ago: <csharp> in my case, it's vastly overestimating the number of rows |
11:24 |
berick |
kmlussier: i can do that |
11:24 |
kmlussier |
berick++ Thanks! |
11:25 |
gsams |
Anyone ever had an issue with the patron bills screen freezing? |
11:25 |
berick |
gsams: sounds vaguely familiar, maybe patron has 100's of bills? |
11:25 |
gsams |
berick: 53 overdue items, likely 53+ bills |
11:26 |
bshum |
Yeah, every time there's lots of bills or lots of things to be summed together, it can crash with the js taking too long. |
11:26 |
bshum |
I think we mitigated some of that by using the library setting to not autoselect all the bills on launch |
11:27 |
bshum |
"Lots" is relative, depending on the available memory, etc. |
11:27 |
mmorgan |
gsams: We don't get freezing, but do get an error when there are lots of individual bills. |
11:27 |
mmorgan |
lp 1185985 |
11:27 |
pinesol_green |
Launchpad bug 1185985 in Evergreen 2.4 "Error in bill2.js, tally_all(); TypeErrorL bill.transaction is undefined" (affected: 9, heat: 42) [Medium,Confirmed] https://launchpad.net/bugs/1185985 |
11:27 |
bshum |
And we've found that actually using Linux workstations we can retrieve patrons with crazy billings, much better than Windows workstations. |
11:28 |
bshum |
So 90% of the time, they ask me or mceraso to fix a user via Linux workstations and clear fines, etc. so that they're usable again. |
11:28 |
bshum |
But that's a bad workaround, not a solution. |
11:29 |
berick |
browser client is paged. if it's installed, you could potentially fix them there, too. |
11:29 |
gsams |
I believe in this situation, if the setting works for this, that will be the solution for us for the time being. |
11:29 |
gsams |
berick: Unfortunately, not an option. I am looking forward to it though! |
11:30 |
bshum |
berick: ooooh, interesting thought! |
11:30 |
kmlussier |
@eightball will the browser client fix all things? |
11:30 |
pinesol_green |
kmlussier: The answer is certainly yes. |
11:30 |
bshum |
I'll have to try that next time around. |
11:30 |
bshum |
berick++ |
11:30 |
bshum |
kmlussier++ # haha, funny :P |
11:30 |
gsams |
berick++ bshum++ kmlussier++ |
11:30 |
kmlussier |
I have never seen @eightball give such a definitive answer before. |
11:30 |
gsams |
kmlussier: perfect timing. |
11:30 |
berick |
kmlussier: me either. spooky |
11:31 |
Dyrcona |
bshum++ # bug wrangling |
11:31 |
bshum |
Dyrcona: I'm almost done! |
11:31 |
bshum |
I think |
11:32 |
bshum |
I need to get back on top of wrangling |
11:32 |
bshum |
But maybe I'll wait till bug day |
11:32 |
bshum |
And score some points on kmlussier's charts :) |
11:32 |
Dyrcona |
To corroborate what bshum says, we see a lot less client freezing with Linux workstations, but it can still happen. |
11:33 |
bshum |
kmlussier: I was thinking, maybe an early October, before the maintenance release scheduled date, eh? |
11:33 |
berick |
kmlussier: rel. notes updated |
11:35 |
kmlussier |
berick: Thank you. |
11:35 |
berick |
thank you |
11:35 |
gsams |
Dyrcona: I've setup a few linux workstations at my library (in the past when we needed them on the fly) and they seemed snappier in general. Though we rarely run into this sort of issue, so that may just be bias or something. |
11:35 |
kmlussier |
Yay! The header is much better. I was cringing every time I pulled up the page. |
11:42 |
gsams |
well, the setting does seem to work. The screen is at least still technically responding at least |
11:42 |
gsams |
I need to slip at least another at least into that sentence. |
11:44 |
gsams |
113 billings, wow. |
11:45 |
bshum |
I think I've seen worse. |
11:46 |
bshum |
My favorites are the users with lots of billings and a partial payment applied to everything. |
11:46 |
* mmorgan |
has seen at least that many, too. |
11:46 |
mmorgan |
Children's books with very small fine amounts - but a LOT of them. |
11:49 |
gsams |
From what I can see, the billings never properly loaded unfortunately. |
11:51 |
bshum |
"Our cruisers can't repel firepower of that magnitude!" |
11:51 |
mmorgan |
gsams: I seem to remember seeing that a few times. Maybe clear the cache and retrieve the patron again? |
11:51 |
berick |
The ion cannon will fire.... |
11:52 |
gsams |
mmorgan: that did indeed work for me |
11:52 |
gsams |
mmorgan++ |
11:53 |
gsams |
113 fines for a total of $29.30 |
11:55 |
jeff |
we used to have a lot of fun because we had circulations with thousands of zero amount billing line items. |
11:55 |
bshum |
Oh, those were the days. |
11:55 |
mmorgan |
That sounds messy! Was that an old bug? |
11:57 |
jeff |
it was a migration pitfall. this would have been in the 1.2 days. i don't recall for certain, but i think changes since then have made it no longer an issue, or less of an issue. |
11:57 |
mmorgan |
Glad it's not something we've seen! :) |
11:57 |
berick |
it's def. fixed |
11:57 |
Dyrcona |
Yep. |
11:58 |
jeff |
but when the fine generator saw a bunch of newly-migrated overdue circs with no billings, daily fine of 0 and max fines of 0, it would "catch up" and generate one fine per day until the current day, THEN set a stop fines of MAXFINES. |
11:59 |
|
kitteh_ joined #evergreen |
11:59 |
jeff |
the conversation on irc went something like "should the fine generator be running right now?" "probably not. what's it doing?" "looks like making a lot of $0 fines" :-) |
12:01 |
Dyrcona |
yep. I recall a branch going in that had is skip tallying overdues when the fine rate is 0. |
12:03 |
bshum |
Oh good times. |
12:29 |
|
bmills joined #evergreen |
12:48 |
Dyrcona |
Just to followup on the nsis problem that I mentioned earlier, no Windows installer was built for my development system as a result. |
12:48 |
Dyrcona |
I have not tried it again, but I might in a few minutes. |
12:53 |
Dyrcona |
And, yes, make win-updates-client appears to be working, now. |
12:54 |
Dyrcona |
Just "one of those things." |
12:54 |
|
montgoc1 joined #evergreen |
13:00 |
Dyrcona |
Hmm... |
13:17 |
|
rfrasur joined #evergreen |
13:44 |
|
tspindler joined #evergreen |
13:50 |
bshum |
10 minutes or so till EOB meeting. |
13:51 |
* rfrasur |
is stoked. |
13:52 |
kmlussier |
rfrasur: I don't think 'stoked' is a word I've ever considered using for EOB meetings. |
13:52 |
bshum |
rfrasur++ |
13:52 |
rfrasur |
Well...it's maybe a little excessive...but I am happy to "see" everyone. |
13:52 |
bshum |
"Oh, your strength gives me strength..." |
13:52 |
rfrasur |
bshum++ |
13:53 |
rfrasur |
I have but little strength to offer right now and am particularly glad and humbled by the fortitude and enthusiasm of our library staff. |
13:54 |
* rfrasur |
has a fountain Coke though. |
13:57 |
|
sherbertbc joined #evergreen |
13:57 |
|
tanyap joined #evergreen |
14:00 |
bshum |
#startmeeting 2015-09-17 - Evergreen Oversight Board Meeting |
14:00 |
pinesol_green |
Meeting started Thu Sep 17 14:00:02 2015 US/Eastern. The chair is bshum. Information about MeetBot at http://wiki.debian.org/MeetBot. |
14:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
14:00 |
pinesol_green |
The meeting name has been set to '2015_09_17___evergreen_oversight_board_meeting' |
14:00 |
bshum |
#link agenda http://list.evergreen-ils.org/pipermail/eg-oversight-board/2015-September/001116.html |
14:00 |
bshum |
I didn't get to formally put it to wiki, but I'll link to the reminder email for now. |
14:00 |
bshum |
Let's see who's here. |
14:00 |
bshum |
#topic Introductions |
14:00 |
bshum |
#info bshum = Ben Shum, Bibliomation |
14:00 |
yboston |
#info yboston - Berklee college of music - EOB |
14:00 |
rfrasur |
#info rfrasur is Ruth Frasur, Hagerstown Public Library, Evergreen Indiana, EOB member |
14:01 |
tanyap |
#tanyap is Tanya Prokrym, SLNC, NC Cardinal |
14:01 |
montgoc1 |
#info montgoc1 is Chauncey Montgomery, Consortium of Ohio Libraries |
14:01 |
tanyap |
#info tanyap is Tanya Prokrym SLNC |
14:02 |
|
jpippin joined #evergreen |
14:02 |
bshum |
csharp told me he had a conflict with another meeting, so he probably won't make it. |
14:03 |
rfrasur |
I saw tspindler log in. |
14:03 |
yboston |
BTW, I'll need to leave early |
14:03 |
bshum |
And sherbertbc too |
14:03 |
bshum |
So we probably have enough for quorum anyways. |
14:03 |
* tspindler |
Tim Spindler (CW MARS) |
14:03 |
|
sherbertbc_ joined #evergreen |
14:03 |
tspindler |
sorry talking budgets and lost track of time |
14:03 |
bshum |
yboston: gotcha |
14:03 |
bshum |
tspindler: No problemo |
14:03 |
|
abneiman joined #evergreen |
14:04 |
bshum |
yboston: We'll probably keep this relatively short. |
14:04 |
yboston |
OK |
14:04 |
sherbertbc_ |
#info sherbertbc = Sharon Herbert, BC Libraries Cooperative |
14:04 |
tspindler |
#info Tim Spindler - C/W MARS |
14:04 |
abneiman |
#info abneiman = Andrea Buntz Neiman, Kent County Public Library |
14:04 |
bshum |
I'll keep us going for now then. |
14:04 |
sherbertbc_ |
having connection problems, sorry |
14:04 |
bshum |
#topic Minutes/actions from last meeting - http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-07-16-14.00.html |
14:05 |
bshum |
1) tspindler will announce a test meeting in the next 2 months to |
14:05 |
bshum |
use our GoToWebinar so we can test it and invite other members of the |
14:05 |
bshum |
Evergreen community to join if they want. |
14:05 |
bshum |
tspindler++ for putting that together |
14:05 |
bshum |
And thanks to all of you who participated |
14:05 |
rfrasur |
What was the verdict? |
14:05 |
bshum |
#info tspindler to test GoToWebinar with other EOB members |
14:06 |
bshum |
#info tspindler's results: http://list.evergreen-ils.org/pipermail/eg-oversight-board/2015-September/001114.html |
14:06 |
tspindler |
I think it worked well over all. Gives us some different options if you want to use it |
14:06 |
yboston |
I thought it worked well. Might want to test it with more people at once to be safe |
14:06 |
montgoc1 |
I agree. Seemed like it would be fine. |
14:07 |
yboston |
I bet it would be fine |
14:07 |
abneiman |
I'm on record before but I like the audio convo better than IRC, I'm more comfortable speaking extemporaneously than typing. Agree on testing with more members. |
14:07 |
rfrasur |
And, was the idea that it supports voice and it's recordable? |
14:07 |
tspindler |
rfrasur: yes |
14:08 |
* rfrasur |
is just restating for the log. |
14:08 |
bshum |
Okay, well maybe as the next experiment we could schedule our October meeting with the tool and see how it works out. The biggest question I'll have is how it handles if more than just EOB members sit in (like if more community members wanted to listen in / participate) |
14:08 |
montgoc1 |
abneiman: same here. |
14:08 |
tspindler |
it records the onscreen display and voice but not video images of participants |
14:08 |
yboston |
though it made me think about IRC meetings, that when I lead a meeting I need to continue to give folks a chance to write out reponses, since not everyone is a fast typicst |
14:08 |
yboston |
(of course I have gotten faster as my grammar and spelling has gotten worse) |
14:09 |
tspindler |
bshum: if we use GoToWebinar, I think make the board panelists and the community members attendees |
14:09 |
rfrasur |
Will there be an issue with hosting what I'd assume are significantly larger files for the recorded meetings? |
14:09 |
yboston |
rfrasur: excelent question |
14:09 |
rfrasur |
And is there a way to transcribe the audio other than and stenographer? |
14:09 |
tspindler |
good point, it does create some large files |
14:09 |
rfrasur |
s/and/an |
14:10 |
bshum |
tspindler: Seems logical to me. |
14:10 |
sherbertbc_ |
assume we'd still need to keep minutes to summarize discussions, track actions |
14:10 |
rfrasur |
Just things to think about. I'm in no way opposed. |
14:10 |
|
graced_ joined #evergreen |
14:10 |
rfrasur |
sherbertbc_, absolutely. |
14:10 |
yboston |
if we don't record video the files will be smaller, but we might have to take time to intruduce our names during the meeting |
14:10 |
montgoc1 |
Yes. IRC does make it easy to search for information since it includes all conversation and not summaries. |
14:10 |
rfrasur |
As it stands right now, however, a bot takes the minutes. |
14:11 |
graced_ |
#info graced is Grace Dunbar, Equinox |
14:11 |
graced_ |
sorry I'm late! |
14:11 |
rfrasur |
welcome, Grace. All is well. |
14:11 |
bshum |
Well csharp isn't here to speak in his role as board secretary, but I imagine he would be willing to help curate notes for the meeting trial. |
14:11 |
yboston |
bshum: I agree |
14:11 |
rfrasur |
We're discussing the GoToMeeting trial...and the implications to using it for meetings from time to time. |
14:12 |
bshum |
I just noticed that I didn't mark an actual date for the next meeting, but according to the calendar it's October 15. |
14:12 |
bshum |
Do we have general interest in making that a trial date to host an audio meeting? |
14:12 |
graced_ |
thanks rfrasur! |
14:12 |
tspindler |
That date works for me |
14:12 |
rfrasur |
Let's shoot for October if all are amenable. |
14:12 |
montgoc1 |
Sure. |
14:13 |
sherbertbc_ |
I'm n/a Oct 15, our annual all staff, but go ahead w/o me! |
14:13 |
bshum |
tspindler: Along the way, for those of us who weren't part of the original trial (me, for example, I'm such a slacker), I wonder if we could ask you to help set up another test in between now and then. |
14:13 |
abneiman |
10/15 should be OK with me |
14:13 |
yboston |
that date works for me |
14:13 |
bshum |
And we can do a dry run so to speak of the board procedures. |
14:14 |
bshum |
#agreed Next EOB meeting October 15 to try as audio meeting via GoToWebinar. |
14:14 |
tspindler |
bshum: i think i could squeeze a date in, I may just have to schedule it and hope it works |
14:14 |
rfrasur |
+1 |
14:14 |
bshum |
tspindler: That'd be fine, and I will hopefully find myself available this time around. |
14:14 |
tspindler |
how is the week of October 5 for a test run? |
14:15 |
bshum |
tspindler: Depends on the day of the week for me. |
14:15 |
rfrasur |
That Monday, Thursday, or Friday are fine. |
14:15 |
tspindler |
I could set up for Thursday, October 8 at 2PM EST if that works for a test for anyone |
14:15 |
bshum |
Thursday or Friday afternoon work for me |
14:15 |
bshum |
I think there's an academics meeting on that Thursday |
14:15 |
sherbertbc_ |
Mon or Fri |
14:15 |
bshum |
For Evergreen academics interest group |
14:15 |
abneiman |
I'm hit or miss (getting a new circ desk that week) but pick a day/time and I'll try to work it in |
14:16 |
tspindler |
4PM EST on October 8? |
14:16 |
bshum |
Alternatively, maybe we allott an extra 20 minutes or so before the 2 pm regular time on October 15 to work out initial technical setup/issues |
14:17 |
tspindler |
bshum: that might make more sense. |
14:17 |
rfrasur |
I like that idea. |
14:17 |
montgoc1 |
Me too. |
14:17 |
bshum |
You know, practice before we hit "record" |
14:17 |
bshum |
"EOB meeting, take 1..." |
14:17 |
|
graced_ joined #evergreen |
14:17 |
bshum |
If that's a better idea, let's try to pencil that into the schedule. |
14:17 |
abneiman |
I'm more in favor of practicing pre-meeting on the 15th |
14:18 |
rfrasur |
So...maybe 1:30 p.m. with the meeting to begin at regular time? |
14:18 |
bshum |
rfrasur: +1 |
14:18 |
abneiman |
rfrasur: +1 |
14:18 |
tspindler |
rfrasur: +1 |
14:18 |
montgoc1 |
rfrasur: +1 |
14:18 |
|
maryj joined #evergreen |
14:19 |
bshum |
#info Pre-meeting practice for GoToWebinar to occur at 1:30 pm Eastern on October 15 prior to the regular EOB meeting. |
14:19 |
bshum |
Cool deal, thanks all, and hopefully we get some good feedback on how that next meeting's test goes via audio. |
14:19 |
bshum |
Anything further on that for now? |
14:19 |
rfrasur |
And tspindler, you send out the join link? |
14:19 |
tspindler |
rfrasur: yes, I'll do that |
14:19 |
rfrasur |
tspindler++ |
14:20 |
bshum |
tspindler++ indeed. |
14:20 |
bshum |
Okay, 2) past action item |
14:20 |
bshum |
yboston will follow up with bshum and gmcharlt to review what commnads are being used to get reports from cli-ledger and ask if the SFS has any recommendations for different commands |
14:20 |
bshum |
Presumably Conservancy, not SFS :) |
14:21 |
yboston |
I did not work on this, would need to defer to newxt meeting |
14:21 |
rfrasur |
Again, tspindler++ for putting that into an xlsx |
14:21 |
bshum |
I'd like to table this action item because there'll be something we're bringing up in New Business regarding the ledger reading |
14:21 |
rfrasur |
bshum +1 |
14:21 |
yboston |
that is fine by me |
14:21 |
bshum |
#info yboston's action item for cli-ledger is deferred to later in the meeting. |
14:21 |
bshum |
#topic EG 2016 Conference Update |
14:21 |
bshum |
tanyap: Thanks for coming! |
14:22 |
tanyap |
we are working on several categories right now; |
14:22 |
rfrasur |
tanyap, can you confirm the dates? |
14:22 |
tanyap |
we just finished the sponsorship packet and grace reviewed it so we are ready to go 'a sponsoring'. |
14:22 |
tanyap |
conference is april 20 - 23, 2016. |
14:23 |
tanyap |
we are waiting on Eventbrite for registration (Tony from SFC is working on this). |
14:23 |
tanyap |
We have our call for proposals written but are working on our pre-conference descriptions. |
14:24 |
tanyap |
We are waiting to hear from our keynote speaker request. |
14:24 |
tanyap |
We hope to open registration and call for proposals by end of sept. |
14:24 |
bshum |
Excellent! |
14:25 |
graced_ |
tanyap++ |
14:25 |
tanyap |
i have two questions. |
14:25 |
tanyap |
1. should we wait for the call for proposals until registration is ready? |
14:26 |
rfrasur |
Nope. |
14:26 |
bshum |
No, I think you can go ahead with proposal call as soon as you're ready. |
14:26 |
graced_ |
I would say no, as well. |
14:26 |
abneiman |
no strong opinion on that one |
14:26 |
montgoc1 |
I personally think having proposals first helps build excitement about the conference. |
14:26 |
rfrasur |
and tanyap++, btw. Y'all are on top of things. |
14:26 |
* bshum |
agrees with montgoc1 |
14:26 |
bshum |
But sometimes time doesn't afford us all that |
14:27 |
tanyap |
thank you! |
14:27 |
sherbertbc_ |
montgoc1: agreed, many will wait to register until they see program |
14:27 |
bshum |
And some of us are bad at submitting program ideas :) |
14:27 |
graced_ |
And many of us will be there no matter what. :) |
14:27 |
rfrasur |
Yeah, I think the earlier you can get out the call for proposals, the better. |
14:27 |
tanyap |
hah! |
14:27 |
rfrasur |
graced_++ too true |
14:28 |
bshum |
tanyap: What's your second question? :) |
14:28 |
tanyap |
my second question was about exhibitors but i can ask grace later if necessary. i didn't know when they set up/ broke down. |
14:29 |
graced_ |
tanyap: I can help you figure that out based on your space and the times. |
14:29 |
graced_ |
No one should need more than a few hours. |
14:29 |
tanyap |
ok. thanks. |
14:29 |
bshum |
Cool, cool. graced++ # experience! |
14:30 |
bshum |
anything else for this topic? Or questions? |
14:30 |
tanyap |
just fyi - we are looking at keynote speakers that can talk about the next decade because of our theme. and I think that is it unless you have questions. |
14:30 |
graced_ |
tanyap++ (it bears repeating) |
14:30 |
rfrasur |
agreed tanyap++ |
14:30 |
bshum |
tanyap++ |
14:30 |
montgoc1 |
tanyap++ |
14:31 |
* rfrasur |
will be plugging the conference tomorrow...and am now more confident. |
14:31 |
abneiman |
tanyap++ great job you & the rest of the committee! I'm looking forward to it. |
14:31 |
tanyap |
thank you. i have a great group of people behind me. |
14:32 |
sherbertbc_ |
tanyap++ |
14:32 |
yboston |
tanyap++ |
14:32 |
bshum |
Okay, moving on for now |
14:32 |
bshum |
#topic Financial Report |
14:32 |
yboston |
BTW, I need to leave early and work on a server migration and a meeting |
14:32 |
bshum |
#link http://list.evergreen-ils.org/pipermail/eg-oversight-board/2015-September/001117.html |
14:33 |
bshum |
yboston: Thanks for coming, and I'll make sure to volunteer you for everything once you're gone ;) |
14:33 |
rfrasur |
yboston++ thank you for the time you could be here. |
14:33 |
bshum |
Mostly as I noted in the email, between last time and now were just updates to the ledger for final expenses. |
14:34 |
bshum |
Unless there's a specific question on that, I'll move us along in the agenda because we're going to talk more about the ledger later in new business. |
14:34 |
tspindler |
bshum: maybe this was answered at the last meeting but at the top there is Evergreen Expenses: 202,000 |
14:34 |
tspindler |
I'm assuming that is not a total of all expenses but something else? |
14:35 |
bshum |
tspindler: Okay, well |
14:35 |
bshum |
That is total expenses listed in the ledger, yes. |
14:35 |
bshum |
So you add Expenses + Income + Unearned Income to get the final tally |
14:35 |
tspindler |
because the column from banking fees to tradmark adds up to 456,180 |
14:36 |
bshum |
tspindler: Right, you can't straight add all the sub entries. |
14:36 |
bshum |
You have to look at how the indents work in the summary |
14:36 |
bshum |
For example, under Expenses, Sales Tax, there's CA and MA |
14:36 |
bshum |
You add CA + MA = the total line by Sales Tax |
14:37 |
tspindler |
i see, it was not clear to me, I understand now. |
14:37 |
bshum |
Yeah, the indents dont' display as nicely in certain email clients. |
14:37 |
tspindler |
not in gmail, which is what I looked at it in |
14:37 |
rfrasur |
It doesn't look much different than it did in August. And, just to clarify..a negative is actually income |
14:37 |
bshum |
The linked page has a better breakdown based on the space indents |
14:38 |
bshum |
rfrasur: Yeah that gets me every time that negative is a good thing :) |
14:38 |
rfrasur |
It's worth repeating in case someone new is reading the financials. |
14:38 |
bshum |
rfrasur++ |
14:39 |
bshum |
Okay |
14:39 |
bshum |
#topic Evergreen 2.9 Release Manager Report |
14:39 |
rfrasur |
I'm not sure about the historic numbers, but it seems like all is in good stead. |
14:39 |
bshum |
Dyrcona++ # 2.9.0! |
14:40 |
rfrasur |
Dyrcona++ |
14:40 |
tspindler |
Dyrcona++ |
14:40 |
montgoc1 |
Dyrcona++ |
14:40 |
graced_ |
Dyrcona++ |
14:40 |
bshum |
#link 2.9.0 release announcement blog post: http://evergreen-ils.org/evergreen-2-9-0-released/ |
14:40 |
abneiman |
Dyrcona++ |
14:40 |
bshum |
I'm not sure Dyrcona is here actually. But I'll link to the blog post for the notes. |
14:41 |
bshum |
Maybe we'll ask him to write up a summary from his viewpoint of 2.9 release process later. |
14:41 |
* bshum |
waits another beat |
14:42 |
bshum |
#topic New Business |
14:43 |
bshum |
#info kmlussier forwarded an email by interested parties to develop a web-based view of the ledger data for Conservancy projects. |
14:43 |
bshum |
kmlussier: You got two seconds to give folks some background? |
14:44 |
|
jihpringle joined #evergreen |
14:44 |
* rfrasur |
listens |
14:44 |
kmlussier |
bshum: I don't have much more background than you do. There is a person from the Sandstorm project who is interested in doing a web-based view of the ledger software the Conservancy works with. |
14:45 |
kmlussier |
bkuhn thought the Evergreen project would be a good fit for the project. Several of the other Conservancy projects don't pay as much attention to the financials as we do, I guess. |
14:45 |
graced_ |
So... they want money? development time? or what? |
14:45 |
rfrasur |
I think this sounds very intriguing. |
14:46 |
kmlussier |
graced_: They don't want anything from us. They have a volunteer who wants to do the development. |
14:46 |
kmlussier |
They just want to use us a guinea pigs. |
14:46 |
bshum |
Feedback I gathered. |
14:46 |
kmlussier |
*as* guinea pigs |
14:46 |
graced_ |
kmlussier: how would the data be protected/available? |
14:47 |
graced_ |
Or do we not have those details yet? |
14:47 |
kmlussier |
graced_: I've pretty much reported all I know. |
14:47 |
kmlussier |
I'm not on the EOB anymore, so I forwarded it to responsible parties. :) |
14:47 |
graced_ |
fair enough - it's worth talking to them to find out some more info |
14:47 |
bshum |
graced_: I think that's an important question, I just wanted to bring it to the attention that we got tapped to participate. |
14:47 |
bshum |
*attention of EOB |
14:47 |
graced_ |
If they include a toggle to turn the negatives into positives and vice versa I might get giddy. ;-) |
14:48 |
rfrasur |
agree with graced_. I think it's definitely worth finding more information. |
14:48 |
abneiman |
graced_++ agreed, need those questions answered. And on the neg-to-pos, drives me nuts :) |
14:48 |
bshum |
What I'd like to do is begin a discussion with the contact from their project and figure out how we proceed. |
14:48 |
bshum |
Just how, for now, since we have questions like the security of the data. |
14:48 |
rfrasur |
And, it might be nice to expose Evergreen to people in another project. Networking is rarely a bad thing. |
14:49 |
graced_ |
bshum: sounds good. I assume we should send you a list of any questions/concerns we have? |
14:49 |
bshum |
graced_: Sure, I'd be happy to take those with me when we initiate the discussion. |
14:50 |
graced_ |
excellent |
14:50 |
bshum |
And I'll likely look for volunteers later to gather feedback. |
14:50 |
graced_ |
consider me volunteering in advance |
14:50 |
rfrasur |
me too |
14:51 |
bshum |
Excellent. |
14:52 |
bshum |
#info bshum and yboston to discuss further details and collect more information on how the project will be initiated for web-based ledger viewing. |
14:52 |
bshum |
Anything else for New Business? Or any other topics for discussion today? |
14:53 |
rfrasur |
Not this month. Not from me. |
14:53 |
graced_ |
not from me |
14:53 |
tspindler |
the fed kept interest rates the same, no change from me |
14:53 |
bshum |
Hehe |
14:53 |
bshum |
Okay, then. |
14:53 |
* rfrasur |
chuckles |
14:53 |
bshum |
Thanks for coming everyone, and we'll meet again next month, via audio. |
14:53 |
bshum |
#endmeeting |
14:53 |
pinesol_green |
Meeting ended Thu Sep 17 14:53:52 2015 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
14:53 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-09-17-14.00.html |
14:53 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-09-17-14.00.txt |
14:53 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-09-17-14.00.log.html |
14:54 |
graced_ |
bshum++ |
14:54 |
montgoc1 |
bshum++ |
14:54 |
sherbertbc_ |
bshum++ |
14:54 |
tspindler |
bshum++ |
14:54 |
rfrasur |
bshum++ |
14:54 |
abneiman |
bshum++ |
14:54 |
rfrasur |
Okay, my lovelies...on to the next meeting. and tanyap++ again |
15:21 |
|
tspindler left #evergreen |
15:35 |
bshum |
...yeesh |
15:35 |
bshum |
bug 1496977 looks annoying |
15:35 |
pinesol_green |
Launchpad bug 1496977 in Evergreen 2.9 "Duplicate Code in O::A::Cat::AssetCommon" (affected: 1, heat: 6) [Medium,New] https://launchpad.net/bugs/1496977 |
15:42 |
bshum |
Dyrcona: pushed that for you, makes sense to me. |
15:43 |
pinesol_green |
[evergreen|Jason Stephenson] LP 1496977: Duplicate Code in OpenILS::Application::Cat::AssetCommon - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=dbb9c81> |
16:24 |
miker |
dang it ... Dyrcona: signing off on your branch and pushing |
16:24 |
miker |
doh, |
16:24 |
miker |
or not |
16:24 |
miker |
bshum++ # thanks |
16:25 |
|
jlitrell joined #evergreen |
16:44 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
16:45 |
kmlussier |
Huzzah! |
16:55 |
phasefx |
yay |
16:57 |
phasefx |
those unrecognized value "" for "ECHO"; assuming "none" warnings are also relatively new, and introduced with a change in psql |
17:03 |
|
mmorgan left #evergreen |
17:24 |
|
bmills joined #evergreen |
18:28 |
|
jlitrell joined #evergreen |
20:57 |
|
yboston joined #evergreen |