| Time |
Nick |
Message |
| 01:33 |
|
hopkinsju joined #evergreen |
| 01:42 |
|
tsbere joined #evergreen |
| 01:48 |
|
tsbere joined #evergreen |
| 01:50 |
|
ldwhalen_ joined #evergreen |
| 01:53 |
|
ldwhalen joined #evergreen |
| 01:53 |
|
Mark__T joined #evergreen |
| 04:44 |
paxed |
@later tell kmlussier docs/RELEASE_NOTES_NEXT/Circulation/disallow-pickup.txt typo "avilable" |
| 04:44 |
pinesol_green |
paxed: The operation succeeded. |
| 04:49 |
paxed |
in docs/admin_initial_setup/migrating_patron_data.txt typo "wil" |
| 05:40 |
|
fparks joined #evergreen |
| 07:07 |
|
granitize joined #evergreen |
| 07:07 |
|
granitize left #evergreen |
| 07:08 |
|
granitize joined #evergreen |
| 07:24 |
|
granitize1 joined #evergreen |
| 07:25 |
|
granitize joined #evergreen |
| 07:41 |
|
rjackson-isl joined #evergreen |
| 07:42 |
|
granitize left #evergreen |
| 08:01 |
|
collum joined #evergreen |
| 08:08 |
|
jboyer-isl joined #evergreen |
| 08:21 |
|
rfrasur joined #evergreen |
| 08:23 |
rfrasur |
jboyer-isl: do we have the all clear? Trying to decide which direction to start driving...to Hagerstown (for offline transactions) or Indianapolis (for other stuff) |
| 08:24 |
jboyer-isl |
rfrausr: everything is back on, but no email has gone out yet. I expect one will soon though. |
| 08:24 |
rfrasur |
okay...ty. It takes 45 minutes to get to Hagerstown anyway, so I'll assume that it'll be okay when I get there. |
| 08:33 |
|
akilsdonk joined #evergreen |
| 08:46 |
|
mrpeters joined #evergreen |
| 08:53 |
|
Shae joined #evergreen |
| 08:56 |
|
dbs joined #evergreen |
| 08:59 |
* csharp |
finds a typo in the example crontab |
| 09:00 |
csharp |
# Run the pending user purger |
| 09:00 |
csharp |
2 30 * * * . ~/.bashrc && $EG_BIN_DIR/purge_pending_users.srfsh |
| 09:01 |
csharp |
there is no hour "30" ;-) |
| 09:01 |
|
mmorgan joined #evergreen |
| 09:06 |
csharp |
# Run the pending user purger |
| 09:06 |
csharp |
2 30 * * * . ~/.bashrc && $EG_BIN_DIR/purge_pending_users.srfsh |
| 09:06 |
csharp |
bah - sorry |
| 09:10 |
dbs |
csharp: we need 30-hour days. |
| 09:10 |
mrpeters |
30 hour days are cool if we get to sleep 14 of them |
| 09:11 |
* csharp |
agrees |
| 09:11 |
paxed |
oh hey, i'd still be 29 if we'd be using 30-hour days... |
| 09:12 |
* csharp |
marches on toward 40 |
| 09:12 |
paxed |
s/still/only/ |
| 09:14 |
dbs |
bshum: looks like the gateway connection to UPEI (debian build slave) isn't responding, I'll poke them |
| 09:20 |
pinesol_green |
[evergreen|Chris Sharp] Fixing typo in the crontab.example file - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=2130d75> |
| 09:21 |
|
RoganH joined #evergreen |
| 09:22 |
|
kbeswick joined #evergreen |
| 09:31 |
|
remingtron joined #evergreen |
| 09:41 |
jeff |
15 days since we applied for access to the OverDrive Circulation APIs. Disappointed in their lack of response so far. |
| 09:42 |
|
yboston joined #evergreen |
| 09:42 |
|
kmlussier joined #evergreen |
| 09:42 |
RoganH |
Patience is more of a necessity than a virtue with Overdrive. |
| 09:42 |
jeff |
They claim to review applications on a "weekly basis", but we applied Oct 1 and it is now Oct 15. |
| 09:43 |
jeff |
At this rate, I could have driven down to Cleveland, spent some time with friends, and knocked on OverDrive's door for a personal interview to obtain access to the Circulation APIs and/or test environment. ;-) |
| 09:43 |
RoganH |
Time is highly subjective. |
| 09:44 |
RoganH |
They may only be counting the third hour of every meal break towards the week. |
| 09:48 |
|
misilot joined #evergreen |
| 09:48 |
jboyer-isl |
I need to know how to get in on 3 hour meal breaks. |
| 09:56 |
|
hopkinsju joined #evergreen |
| 10:05 |
pinesol_green |
[evergreen|Dan Scott] Fix TPAC account preferences - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=ed34006> |
| 10:21 |
kmlussier |
Reminder: Just 2 1/2 hours to get your agenda items in for today's dev meeting. http://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2013-10-15 |
| 10:38 |
|
misilot left #evergreen |
| 10:40 |
|
Bmagic joined #evergreen |
| 10:41 |
|
kmlussier joined #evergreen |
| 10:46 |
|
jdouma joined #evergreen |
| 10:48 |
|
jecs joined #evergreen |
| 10:51 |
|
kmlussier joined #evergreen |
| 10:58 |
|
Bmagic left #evergreen |
| 10:58 |
|
Bmagic|2 joined #evergreen |
| 11:09 |
pinesol_green |
[evergreen|Dan Wells] Serial alert notes missing commit - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=3a01d73> |
| 11:33 |
|
smyers_ joined #evergreen |
| 11:36 |
|
tsbere_ joined #evergreen |
| 11:45 |
|
akilsdonk joined #evergreen |
| 11:49 |
|
dMiller joined #evergreen |
| 11:50 |
jcamins |
@later tell rfrasur This article made me think of you, for some reason: http://www.futuristspeaker.com/2013/10/libraries-that-create-their-own-economy-opening-the-door-to-premium-services/ |
| 11:50 |
pinesol_green |
jcamins: The operation succeeded. |
| 12:02 |
berick |
jeff: angular code lives, finally |
| 12:03 |
jeff |
berick++ yay |
| 12:04 |
csharp |
berick++ |
| 12:08 |
dbwells |
berick: since you popped your head up, and I haven't posted the rc1 tarball yet, did you find a chance to look at bug #1239837 yet? |
| 12:08 |
pinesol_green |
Launchpad bug 1239837 in Evergreen 2.4 "Undefined variable prevents quick PO creation" (affected: 1, heat: 6) [High,New] https://launchpad.net/bugs/1239837 |
| 12:10 |
berick |
dbwells: looking now, sorry |
| 12:10 |
dbwells |
np |
| 12:13 |
berick |
dbwells++ looks correct, testing and signing off now |
| 12:14 |
dbwells |
berick++ # thank you, sir |
| 12:34 |
gmcharlt |
berick++ |
| 12:34 |
berick |
does this look odd to anyone else? http://dev198.esilibrary.com/eg/opac/results?query=violin&qtype=keyword |
| 12:35 |
berick |
hmm, i think something must have been cached in my browser |
| 12:35 |
pinesol_green |
[evergreen|Dan Wells] Fix typo in acq code to allow quick PO creation - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=55e1bf1> |
| 12:36 |
jcamins |
berick: the links all look wrong to me, but not knowing the system, that's probably just a sign that TPAC uses weird links. |
| 12:36 |
berick |
all the content was breaking, but now it looks fine. |
| 12:36 |
berick |
yeah, i think it was a personal problem |
| 12:36 |
csharp |
@blame personal problems |
| 12:36 |
pinesol_green |
csharp: personal problems stole bradl's tux doll! |
| 12:37 |
dbwells |
berick: I do see a lot of "Image of item" links where the images should be, but maybe that is just configuration related. |
| 12:37 |
berick |
yeah, that's local config |
| 12:38 |
berick |
it was acting /super/ crazy, but not anymore |
| 12:38 |
berick |
thanks for looking |
| 13:01 |
kmlussier |
Does anyone want to volunteer to lead today's dev meeting? :) |
| 13:04 |
|
stevenyvr2 joined #evergreen |
| 13:06 |
kmlussier |
#startmeeting 2013-10-15 - October Developers meeting |
| 13:06 |
pinesol_green |
Meeting started Tue Oct 15 13:06:24 2013 US/Eastern. The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 13:06 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 13:06 |
pinesol_green |
The meeting name has been set to '2013_10_15___october_developers_meeting' |
| 13:06 |
berick |
thanks kmlussier |
| 13:07 |
berick |
#info berick Bill Erickson, ESI |
| 13:07 |
csharp |
#info csharp Chris Sharp, GPLS |
| 13:07 |
kmlussier |
#info Agenda is at http://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2013-10-15 |
| 13:07 |
* eeevil |
watches everone but kmlussier take a step back |
| 13:07 |
jeff |
#info jeff Jeff Godin, TADL |
| 13:07 |
phasefx |
#info phasefx Jason Etheridge, ESI |
| 13:07 |
eeevil |
#info eeevil Mike Rylander, ESI |
| 13:07 |
senator |
#info senator Lebbeous Fogle-Weekley, ESI |
| 13:07 |
kmlussier |
I'm terrible at running these meetings. :) |
| 13:07 |
dbwells |
#info dbwells Dan Wells, Hekman Library (Calvin College) |
| 13:08 |
ldwhalen |
#info ldwhalen Liam Whalen, BC Libraries Coop |
| 13:08 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 13:08 |
remingtron |
#info remingtron Remington Steed, Hekman Library (Calvin College) |
| 13:08 |
RoganH |
#info RoganH, SCLENDS |
| 13:08 |
bshum |
#info bshum = Ben Shum, Bibliomation |
| 13:08 |
* bshum |
hates the 3 hour time difference |
| 13:09 |
kmlussier |
#topic Action Items from Last Meeting |
| 13:09 |
kmlussier |
#info [extra old action item from summer doldrums] Start on the 2.6 development road map page |
| 13:09 |
kmlussier |
There's no name assigned to that action item. |
| 13:10 |
berick |
I can do that |
| 13:10 |
kmlussier |
Looks like we have a start already http://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:2.6 |
| 13:10 |
* berick |
checks to make sure no one already did. |
| 13:10 |
berick |
heh |
| 13:10 |
* berick |
bows |
| 13:10 |
kmlussier |
#link http://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:2.6 |
| 13:11 |
kmlussier |
#info [extra old action item ” ” ”] bshum to summarize bug tracking based on feedback from developers |
| 13:11 |
bshum |
I think I'm going to generally loop that into a larger discussion about how much we all hate LP |
| 13:12 |
bshum |
But specifically, no, I have yet to complete a better writeup of bug procedures. |
| 13:12 |
bshum |
I do thank dbwells and remingtron for handling most of the bug shifting during this 2.5 release cycle though. |
| 13:12 |
kmlussier |
Should we be kicking off on a discussion for replacing LP? |
| 13:13 |
Bmagic|2 |
#info Bmagic = Blake GH, MOBIUS |
| 13:13 |
* kmlussier |
eyes bug 1235642 |
| 13:13 |
pinesol_green |
Launchpad bug 1235642 in Evergreen "Launchpad Too Cumbersome" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1235642 |
| 13:16 |
bshum |
Yes, I think that a place to start is probably to get some more discussion going, but I'm not entirely sure what alternatives are best in this case (or who would be able to help contribute to setting up something more distinct) |
| 13:16 |
bshum |
I did do some minor investigation during the last conference, but those didn't get too far. |
| 13:16 |
dbwells |
I think LP is serviceable, and it would be a big effort to move to something else. I am not opposed to it, but I don't think I could contribute to the effort at this point. |
| 13:16 |
berick |
might be good to start with specifics. that LP entry is pretty slim ;) |
| 13:17 |
|
smyers_ joined #evergreen |
| 13:17 |
kmlussier |
bshum: Would you be willing to kick off the discussion? Or should I volunteer Dyrcona for it since he's not here? :) |
| 13:17 |
|
DPearl joined #evergreen |
| 13:18 |
bshum |
kmlussier: I think I agree with dbwells that we haven't shown enough unhappiness with the existing approach to actually put time towards coming up with something new. |
| 13:18 |
csharp |
dbwells: +1 |
| 13:18 |
csharp |
however, if the community wants, GPLS could set up a server for experimentation |
| 13:19 |
kmlussier |
OK, so then do you want to defer your action item to summarize bug tracking to the next meeting? |
| 13:19 |
kmlussier |
bshum ^ ^ |
| 13:19 |
bshum |
kmlussier: Yes. |
| 13:19 |
kmlussier |
#action bshum to summarize bug tracking based on feedback from developers |
| 13:19 |
bshum |
And Dyrcona can put some thoughts towards that bug ticket, since he helped start it :) |
| 13:19 |
kmlussier |
#info [extra old action item ” ” ”] kmlussier to raise bug squashing day to the lists for further discussion/feedback |
| 13:20 |
kmlussier |
#info kmlussier posted message to the dev list today http://georgialibraries.markmail.org/thread/22six3nkgbhr3f3t |
| 13:21 |
kmlussier |
If anyone has anything to contribute to that discussion, feel free to send it to the list. |
| 13:21 |
kmlussier |
#info gmcharlt to release opensrf 2.2.1 soon(?) post-vacation |
| 13:21 |
gmcharlt |
#info gmcharlt to release 2.2.1 this week |
| 13:22 |
kmlussier |
gmcharlt++ |
| 13:22 |
gmcharlt |
(and KohaCon as a vacation for Koha's release manager? you jest, surely! ;) ) |
| 13:22 |
kmlussier |
#info csharp to test 2.4.2 rc so we can officialize it |
| 13:22 |
eeevil |
gmcharlt: this includes the new opensrf controller script from berick, yes? |
| 13:22 |
bshum |
Related to opensrf, is there anything in master that lends cutting of a 2.3.0? |
| 13:22 |
eeevil |
kmlussier: that happened, 2.4.3 is waiting in the wings |
| 13:22 |
bshum |
Like the control stuff |
| 13:23 |
gmcharlt |
eeevil: that's actually something to decide, I suppose -- do we want it as 2.2.1, or branch off and release a 2.3.0 as well? |
| 13:23 |
eeevil |
and, like berick, I'm not going to worry about a 2.4.4 until there's a bigger pile of fixes, or next month, whichever comes first |
| 13:24 |
* gmcharlt |
has no strong opinion one way or the other, but the new control scripts might represent a large-enough change |
| 13:24 |
berick |
eeevil: btw, i copied your 2.4.3 files into place as well (though i'm getting ahead of myself) |
| 13:24 |
dbwells |
gmcharlt: we upgraded to OpenSRF 2.2.1 (well, master) on production this past Friday. So far, so good :) |
| 13:24 |
* berick |
also has no strong opinion re: opensrf version |
| 13:24 |
eeevil |
gmcharlt: I'm for 2.3.0. enough user-visible changes, IMO |
| 13:24 |
bshum |
I agree, +1 for 2.3.0 |
| 13:25 |
bshum |
(we've been running that in production since our early September upgrade, so I feel reasonably happy about the state of opensrf master) |
| 13:26 |
dbwells |
+1 to moving to 2.3.0 on account of the control script changes |
| 13:26 |
bshum |
I suppose we just need to update the README in Evergreen to use the new control commands. |
| 13:26 |
gmcharlt |
#info gmcharlt will cut both OpenSRF 2.2.1 (to include the multipart fix) and OpenSRF 2.3.0 (to include the new signal-handling and control script stuff) this week |
| 13:26 |
jeff |
+1 to 2.3.0, but if the multipart request changes haven't made it to a point release of 2.2.x, that might be a good thing to backport/release. |
| 13:26 |
gmcharlt |
jeff: too slow! ;) |
| 13:26 |
jeff |
heh |
| 13:26 |
eeevil |
gmcharlt++ |
| 13:27 |
csharp |
so which opensrf version will be paired with EG 2.5? |
| 13:27 |
senator |
camembert |
| 13:27 |
* gmcharlt |
suggests 2.3.0 |
| 13:27 |
eeevil |
csharp: "latest" :) ... 2.2+ |
| 13:27 |
csharp |
ok |
| 13:27 |
csharp |
senator++ |
| 13:27 |
gmcharlt |
as recommended, with note that 2.2.1 is compatible |
| 13:27 |
eeevil |
(yes, 2.3+ recommended) |
| 13:28 |
kmlussier |
#info 2.3.0 will be recommended to run with EG 2.5, but 2.2.1 will be compatible as well. |
| 13:28 |
kmlussier |
Moving on to the next action item... |
| 13:28 |
kmlussier |
#info senator to find old incomplete action items to move forward (with help from the channel in making sure I get the right ones) - Done! |
| 13:29 |
kmlussier |
senator++ # Thanks for all the action items! |
| 13:29 |
kmlussier |
#info eeevil to commit a techref doc explaining how to build pgTAP test |
| 13:31 |
eeevil |
kmlussier: I have not done that yet. it's on my gtasks list, though! |
| 13:31 |
eeevil |
nor have I had time to do the next one |
| 13:31 |
kmlussier |
OK, I'll add both as action items for next time then. |
| 13:31 |
kmlussier |
#action eeevil to commit a techref doc explaining how to build pgTAP test |
| 13:32 |
eeevil |
thanks |
| 13:32 |
kmlussier |
#action o publish detailed plan about freezing baseline schemas between EG releases and using deprecates/supersedes in database upgrade scripts. This will go on the mailing list and the thread should structure further discussion of pros and cons of eeevil's plan. |
| 13:32 |
kmlussier |
That's it for action items, and I think we've also covered OpenSRF Release Info? |
| 13:33 |
kmlussier |
#topic Evergreen release info |
| 13:33 |
|
Callender_ joined #evergreen |
| 13:33 |
kmlussier |
dbwells: Should we start with 2.5? |
| 13:34 |
dbwells |
Sure. After a couple brief rounds of testing and bug squashing, RC1 is uploaded to the usual. |
| 13:34 |
dbwells |
usual place, that is |
| 13:35 |
dbwells |
Been having fun working out the release notes, but that is done as well, and will be uploaded shortly. |
| 13:35 |
|
Callender__ joined #evergreen |
| 13:36 |
kmlussier |
#info 2.5 RC1 is uploaded. Release notes will be uploaded shortly. |
| 13:36 |
kmlussier |
dbwells: Anything else to add? |
| 13:36 |
dbwells |
Since we are a day late already for the delayed version of 2.5 final, I am not sure where to pin down the timeline, but I am pretty confident things we'll get there soon. |
| 13:37 |
dbwells |
It's really all about more testing at this point, so maybe RC will inspire some folks. |
| 13:37 |
|
Callender joined #evergreen |
| 13:37 |
dbwells |
That's about it, unless folks have questions I might be able answer. |
| 13:37 |
kmlussier |
How much time do we usually allow for testing between RC1 and final? |
| 13:38 |
* csharp |
is testing beta1, but will upgrade to RC |
| 13:38 |
gmcharlt |
dbwells: apologies if it's already been mentioned, but I'd like to take this opportunity to mention the fixes for bug 1086458 |
| 13:38 |
pinesol_green |
Launchpad bug 1086458 in Evergreen 2.4 "Staff client memory leaks in 2.3 and later" (affected: 11, heat: 76) [High,Confirmed] https://launchpad.net/bugs/1086458 |
| 13:39 |
gmcharlt |
whether or not it's a candidate for inclusion in 2.5.0, I'm pretty sure lots of folks will be very happy if it makes it in by 2.5.1 |
| 13:39 |
dbwells |
gmcharlt: I haven't looked at it, but I certainly will. |
| 13:40 |
kmlussier |
I think a lot of people would love to see those patches in sooner rather than later. I'm not sure how to approach testing, though. |
| 13:41 |
csharp |
kmlussier: our approach will probably be a due diligence approach on a test server to make sure nothing breaks, then move to production as soon as we're satisfied |
| 13:41 |
dbwells |
gmcharlt: It doesn't look too bad, and if there are no objections, I can pull back RC1 and cram it in there. No formal announcements have been made yet. |
| 13:41 |
csharp |
seems like it's too difficult to simulate in a test environment |
| 13:41 |
kmlussier |
csharp++ |
| 13:42 |
csharp |
dbwells: +1 # fwiw |
| 13:42 |
eeevil |
dbwells: I know it's a pain, having just gone through packaging, but I'm +1 to that |
| 13:43 |
gmcharlt |
dbwells: thanks -- but also, TIA to anybody who tests it |
| 13:43 |
kmlussier |
Is everyone in agreement to include the memory leak patches in RC1 then? |
| 13:43 |
* gmcharlt |
will search for a suitable libation whose name encodes the concept of "at the last minute" for delivery next time I see you ;) |
| 13:44 |
dbwells |
I would also appreciate a test/sign-off/push to master on that branch by anyone else who can take a look. |
| 13:44 |
gmcharlt |
+1 |
| 13:45 |
* dbwells |
will test what he can of it, but RC1 will be out today, or BUST |
| 13:45 |
csharp |
dbwells++ |
| 13:46 |
kmlussier |
#agree dbwells will pull back RC1 and incorporate memory leak patches. Sign-off from other testers will be appreciated. |
| 13:46 |
kmlussier |
Any other questions for dbwells? |
| 13:46 |
kmlussier |
eeevil / berick: Is there anything to report on 2.3/2.4 releases other than the fact that you will be skipping this month's point release? |
| 13:47 |
berick |
just need a volunteer from the web team (a Webster?) to update the downloads page |
| 13:47 |
csharp |
ha! |
| 13:47 |
csharp |
webster++ |
| 13:47 |
* berick |
has nothing else to report on releases |
| 13:48 |
kmlussier |
bshum / moodaepo: Are either of you available to update the downloads page? |
| 13:48 |
|
sylvar joined #evergreen |
| 13:48 |
|
Callender joined #evergreen |
| 13:48 |
moodaepo |
kmlussier: available |
| 13:48 |
* dbwells |
almost called berick an acq-olyte yesterday (sorry) |
| 13:48 |
bshum |
kmlussier: I'd prefer to ask someone else to do it. I'm not a fan of my connection right now. |
| 13:48 |
csharp |
dbwells++ |
| 13:48 |
kmlussier |
moodaepo++ |
| 13:48 |
moodaepo |
bshum: go back to your poker chips |
| 13:48 |
moodaepo |
:) |
| 13:48 |
csharp |
puns++ :-D |
| 13:48 |
kmlussier |
:) |
| 13:49 |
sylvar |
berick: http://jsfiddle.net/vojtajina/js64b/14/ would make https://demo.evergreencatalog.com/ng-staff/circ/patron/search more awesome (for sorting by date of birth) |
| 13:49 |
kmlussier |
#topic Update on OmniTI Performance Work |
| 13:49 |
|
moodaepo left #evergreen |
| 13:49 |
kmlussier |
I'll make this quick. |
| 13:49 |
|
moodaepo joined #evergreen |
| 13:49 |
kmlussier |
#info OmniTI began its performance evaluation for Evergreen last month. As most of you have seen, depesz has been looking at the longest-running queries from the C/W MARS server and finding ways to optimize them. |
| 13:50 |
csharp |
depesz++ |
| 13:50 |
kmlussier |
#info They will be taking a different approach to the staff client evaluation than originally planned. With the consensus last month to move away from XULRunner and towards a web-based client, it didn't make sense to evaluate the viability of continuing with XULRunner. |
| 13:50 |
eeevil |
depesz++ indeed |
| 13:50 |
kmlussier |
#info Instead, jsime has been looking at the way the client is communicating with the backend to determine if there are ways this communication can be optimized when moving to a web-based client. |
| 13:51 |
kmlussier |
That's all I have to report at the moment, but I just wanted to keep everyone in the loop on what has been happening. I believe jsime is also available if anyone has any questions. |
| 13:51 |
csharp |
kmlussier++ |
| 13:51 |
kmlussier |
Or, conversely, if jsime has any questions for the devs. :) |
| 13:52 |
jsime |
just to toss in real quick that the main issue has so far been that parts of the staff client don't seem to always be taking advantage of features that allow grabbing the full depth of a particular object |
| 13:52 |
jsime |
e.g. a patron search which could use the flesh feature to grab both the search results' list of patrons and those patrons' details |
| 13:52 |
jsime |
instead of getting the list of patrons, then iterating through it to get each of their details in turn |
| 13:56 |
kmlussier |
I think one thing we were thinking we might do with that information is include it as part of some kind of best practices for building a new web client. Or maybe there is a better way to share that information as we proceed with the analysis? |
| 13:56 |
phasefx |
jsime: just want to make sure you've seen this: http://wiki.evergreen-ils.org/doku.php?id=dev:testing:performance_issues |
| 13:57 |
jsime |
phasefx: thanks for the link - berick's notes under General Improvement are spot on for that |
| 13:58 |
kmlussier |
OK, we're running short on time. I'm going to move on to the next agenda item. |
| 13:58 |
kmlussier |
#topic Discuss freezing of master during beta/RC phase |
| 13:59 |
berick |
yeah, i was asking about that. thanks for added that.. dbwells? |
| 13:59 |
dbwells |
This came up a few days ago, and berick suggested we discuss it at the next dev meeting, so I threw it on there. |
| 13:59 |
berick |
my main concern was that stuff would accidentally seep into the beta/RC's |
| 14:00 |
berick |
but that can probably be avoided with consensus on the plan, communication, etc. |
| 14:00 |
gmcharlt |
I see two parts of it |
| 14:00 |
eeevil |
fwiw, I'm in favor of a voluntary freeze by committer, not a branch. reason being, it avoids defocusing committer effort on bugs (though there's not much we can do to REfocus volunteers' time) |
| 14:00 |
gmcharlt |
freeze 'master' for new features to encourage folks to work on release-critical bugs |
| 14:00 |
gmcharlt |
or, freeze master to avoid stuff slipping in by accident |
| 14:01 |
gmcharlt |
the later could be addressed just by branch rel_2_5 |
| 14:01 |
gmcharlt |
*branching |
| 14:01 |
eeevil |
the reason I don't like branching is that it increases the workload for the new-version RM |
| 14:01 |
eeevil |
which is (I think dbwells and berick will agree) already pretty high |
| 14:02 |
dbwells |
yes |
| 14:03 |
berick |
indeed. so, it seems like everyone's in agreement in general. i'm also fine w/ the honor system |
| 14:04 |
berick |
so, no version branch until x.x.0 is tagged? |
| 14:05 |
dbwells |
If its ever an issue, accidental or otherwise, I think whoever is RM would notice and talking with the committer an reverting if needed wouldn't be so bad. |
| 14:06 |
eeevil |
+1 |
| 14:06 |
dbwells |
+1 |
| 14:06 |
berick |
+1 |
| 14:06 |
kmlussier |
#agree There will be no version branch until x.x.0 is tagged. There will be a feature freeze for master between beta and x.x.0. |
| 14:06 |
kmlussier |
Did I get that right? |
| 14:07 |
berick |
kmlussier++ |
| 14:07 |
kmlussier |
OK, anything else for this meeting before we wrap up? |
| 14:07 |
dbwells |
kmlussier: I imagine the bot would whine if you didn't :) |
| 14:07 |
kmlussier |
:) |
| 14:08 |
kmlussier |
#endmeeting |
| 14:08 |
pinesol_green |
Meeting ended Tue Oct 15 14:08:06 2013 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 14:08 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-10-15-13.06.html |
| 14:08 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-10-15-13.06.txt |
| 14:08 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-10-15-13.06.log.html |
| 14:08 |
jeff |
kmlussier++ |
| 14:08 |
dbwells |
kmlussier++ |
| 14:08 |
gmcharlt |
kmlussier++ |
| 14:08 |
kmlussier |
I'm happy to start taking names for volunteers to run the next dev meeting. :) |
| 14:09 |
eeevil |
kmlussier++ |
| 14:09 |
* gmcharlt |
tosses his hat in that particular ring |
| 14:09 |
berick |
kmlussier++ |
| 14:09 |
csharp |
kmlussier++ |
| 14:09 |
|
frank_____ joined #evergreen |
| 14:10 |
frank_____ |
hello everybody, I have a question, Is possible having more than one administrator account? |
| 14:11 |
eeevil |
frank_____: yes |
| 14:11 |
berick |
sylvar: yes, indeed, that's a nice example. lots of good stuff could be added. |
| 14:11 |
kmlussier |
gmcharlt: Thanks! I didn't think it was right to ask you today since you weren't as available for the meeting as usual. |
| 14:11 |
gmcharlt |
kmlussier: you're welcome |
| 14:12 |
sylvar |
sorry for barging in, y'all |
| 14:12 |
frank_____ |
eeevil: How could I do it? |
| 14:12 |
eeevil |
sylvar: no no, welcome back! ;) |
| 14:13 |
eeevil |
frank_____: the easiest way would be to give a user the EVERYTHING (-1) permission and set the superuser flag on the actor.usr record |
| 14:14 |
eeevil |
and give them a home_ou of the top of the tree, and a profile group of the top of the permission group tree |
| 14:15 |
|
kmlussier joined #evergreen |
| 14:15 |
jeff |
hah. the presence of "Thing 2" at the top navigation confused me for a moment. :-) |
| 14:16 |
gmcharlt |
jeff: sadly, Thing 1 didn't make the cut |
| 14:18 |
berick |
heh |
| 14:18 |
csharp |
@blame The Cat in the Hat |
| 14:18 |
pinesol_green |
csharp: It's all The Cat in the Hat's fault! |
| 14:24 |
frank_____ |
excellent eeevil thanks |
| 14:32 |
* jeff |
reads berick's blog post |
| 14:32 |
jeff |
one of us... one of us... |
| 14:33 |
csharp |
lots of good dev work out there these days ;-) |
| 14:34 |
csharp |
Lo, though our government crumbles around us, the State of the Evergreen Union... is strong |
| 14:35 |
sylvar |
What should I do differently from http://wiki.evergreen-ils.org/doku.php?id=dev:git#quick_start_for_evergreen_contributors if I want to improve Evergreen-DocBook? Do I need to get onto that project as well? |
| 14:35 |
sylvar |
My git-fu has atrophied. |
| 14:37 |
csharp |
sylvar: I would assume gmcharlt or tsbere could assist |
| 14:37 |
bshum |
The Evergreen Docbook is dead |
| 14:37 |
bshum |
Docs are part of the main Evergreen repos now |
| 14:38 |
sylvar |
csharp++ bshum++ |
| 14:38 |
bshum |
sylvar: There's a folder there called "docs" in the main Evergreen repo that has stuff that gets pulled and generated into the docs site |
| 14:39 |
bshum |
You'll still need to poke the git admins to get your working keys setup again I imagine. |
| 14:39 |
bshum |
But I think that's explained in the wiki page you mentioned |
| 14:40 |
sylvar |
yup, gmcharlt++ for that |
| 15:06 |
|
gsams joined #evergreen |
| 15:13 |
sylvar |
ok, I did 'git push working working_branch:user/sylvar/working_branch' and 'git request-pull origin/master working'. What next? |
| 15:14 |
* sylvar |
waits for gmcharlt to tell me "Dang it, you weren't supposed to do that." |
| 15:15 |
sylvar |
(or tsbere) |
| 15:16 |
gmcharlt |
sylvar: typical way is to tag a LP bug with 'pullrequest' |
| 15:16 |
gmcharlt |
(and a comment identifying the branch you want looked at) |
| 15:17 |
sylvar |
gmcharlt: OK, shall I file a bug for spellchecking a few docs? |
| 15:18 |
|
Eman_ joined #evergreen |
| 15:18 |
sylvar |
gmcharlt: and should I just push without request-pull next time? |
| 15:18 |
gmcharlt |
sylvar: yeah, open a bug-- DIG might have standing bugs or the like, but I don't know for sure |
| 15:18 |
gmcharlt |
and to confirm, you don't need to run git-request-pull |
| 15:21 |
Eman_ |
Hi everyone! Quick question: I was reading here: http://docs.evergreen-ils.org/2.3/_configuration_files.html that that there is more information about the KPAC configuration in the "Evergreen Repository." Where is this repository? |
| 15:22 |
berick |
Eman_: i assume it's refering to http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=docs/TechRef/KidsOPAC.txt;h=83d7875d314fa6734cb79c7e461ed82fc5dee2d2;hb=HEAD |
| 15:25 |
Eman_ |
Ah! perfect. Thanks |
| 15:37 |
sylvar |
gmcharlt: are release notes frozen in time or should typos be fixed? |
| 15:38 |
kmlussier |
+1 to fixing typos in release notes. |
| 15:39 |
kmlussier |
Speaking of release notes... |
| 15:41 |
bshum |
I think there's bug tickets on some typos? |
| 15:41 |
kmlussier |
dbwells: I had technology issues that prevented me from pushing my changes to the 2.5 release notes last week. You mentioned that you have already created the release notes for RC1? Is RC1 the time you are planning to create the RELEASE_NOTES_2_5.txt file? |
| 15:41 |
bshum |
Or am I imagining things |
| 15:41 |
kmlussier |
dbwells: I just want to make sure I make my corrections in the right files. |
| 15:41 |
bshum |
Maybe it was just emails |
| 15:42 |
kmlussier |
bshum: There were some bug reports on outdated links. Is that what you're thinking of? |
| 15:43 |
dbwells |
kmlussier: Yes, I have created a RELEASE_NOTES_2_5.txt file. How many changes do you have? |
| 15:43 |
bshum |
No, I think I remember seeing somebody mention typos in the release note entries. |
| 15:43 |
bshum |
Maybe it was just in IRC. |
| 15:43 |
* bshum |
is not in his best state of mind and probably should be quiet now. |
| 15:43 |
csharp |
@dice |
| 15:43 |
pinesol_green |
csharp: (dice <dice>d<sides>) -- Rolls a die with <sides> number of sides <dice> times. For example, 2d6 will roll 2 six-sided dice; 10d10 will roll 10 ten-sided dice. |
| 15:44 |
csharp |
@dice 2d6 |
| 15:44 |
pinesol_green |
csharp: 1 and 5 |
| 15:44 |
kmlussier |
dbwells: A bunch. But what I'll do is hold off on them until RELEASE_NOTES_2_5.txt file is pushed into the git repository and make my changes there. |
| 15:44 |
kmlussier |
I prefer editing it in one file anyway. :) |
| 15:54 |
paxed |
i did mention some typos in the release_notes_next dir, in here. |
| 15:57 |
frank_____ |
Is possible to hide a marc tag in the MARC RECORD label in TPAC? |
| 16:10 |
bshum |
frank_____: I think that's just spitting out what it grabs from marchtml (which looks like it's something in the perl stuff that just grabs the marc content and prints it out). I don't know of easy ways to modify that personally. |
| 16:12 |
bshum |
Does the tag carry significance that needs to be visible in the staff view vs. the public view? Or is it information you can throw away by pruning it from the records? |
| 16:12 |
frank_____ |
Act |
| 16:12 |
eeevil |
frank_____: you could use CSS with content-based selectors, but that won't be robust... |
| 16:13 |
frank_____ |
sorry, actually, the staff patron want to hide a marc tag value because there appear the proyect name who bought the book, so, they dont want to show this, but they want to keep the tag |
| 16:15 |
bshum |
Perhaps this is a case where using something like a copy statistical category to track and report on sources of the material might be better than using MARC conventions to track that information. |
| 16:15 |
senator |
frank_____: hiding the tag in the opac, even if manage that, won't be good enough. marc records can be grabbed through other interfaces as well. if information is meant to be secret, it must be kept out of the marc record |
| 16:15 |
bshum |
We do that in our consortium where we have a "source" copy stat cat that tracks which vendor/gift/whatever paid for the item. |
| 16:15 |
bshum |
Then run reports against those related copies. |
| 16:21 |
|
smyers_ joined #evergreen |
| 16:30 |
hopkinsju |
bshum: Is it my imagination or did the search box disappear from the new open-ils website? |
| 16:32 |
bshum |
hopkinsju: "disappear" isn't the word I would have used. More like "never existed" in the new site. |
| 16:32 |
bshum |
I believe moodaepo had indicated some work in building it again. I took a look but have been distracted with travels this week. |
| 16:33 |
moodaepo |
hopkinsju: bshum: Yea it's still being resurrected. |
| 16:33 |
bshum |
There are some WordPress plugins that make use of the custom google search engine, but google limits api use and charges money for it. |
| 16:34 |
bshum |
I think the final approach will likely require some code thinking to add a box manually and avoid the API. |
| 16:35 |
bshum |
Also making a landing search page that embeds the google framed results, I think. |
| 16:35 |
hopkinsju |
I see. Thanks guys. In the meantime I guess it's just site:open-ils.org |
| 16:35 |
bshum |
Technically evergreen-ils.org is the proper hostname. |
| 16:36 |
hopkinsju |
bshum++ |
| 16:36 |
hopkinsju |
Thanks |
| 16:36 |
bshum |
Add that to the list of things to do to push some forced redirect to the proper names. |
| 16:39 |
jeff |
oh, was it decided to drop the www? |
| 16:39 |
jeff |
i haven't been following web team discussions in a while. |
| 16:40 |
bshum |
jeff: I didn't even know that wasn't decided. The www is just one of the many aliases that work too. |
| 16:40 |
jeff |
sure, but it's the only one that i just saw that redirects to something else. |
| 16:40 |
jeff |
so i figured that was intentional. |
| 16:41 |
* bshum |
shrugs |
| 16:41 |
bshum |
Is that in the dns or apache side? |
| 16:41 |
bshum |
(i don't work with the dns stuff) |
| 16:41 |
jeff |
not dns. |
| 16:42 |
bshum |
Might just be a wordpress thing that I didn't look closely at.... |
| 16:42 |
* jeff |
nods |
| 16:43 |
|
stevenyvr2 joined #evergreen |
| 16:44 |
* bshum |
is going to go find some lunch before he becomes too much of a hermit in his hotel room. |
| 16:44 |
bshum |
Bye for now folks. |
| 16:45 |
jeff |
bshum: enjoy! |
| 16:48 |
pinesol_green |
[evergreen|Galen Charlton] LP#1086458: convert last-print information hash to JSON string before caching - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=09f8847> |
| 16:48 |
pinesol_green |
[evergreen|Galen Charlton] LP#1086458: define custom event for refreshing the checkout page - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=de7d768> |
| 16:48 |
pinesol_green |
[evergreen|Galen Charlton] LP#1086458: invoke new 'refresh_checkout' event - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d22371c> |
| 16:48 |
pinesol_green |
[evergreen|Galen Charlton] LP#1086458: remove unecessary anonymous hashes when calling xulG.set_tab() - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=aff73bf> |
| 17:09 |
|
hopkinsju joined #evergreen |
| 17:15 |
|
mmorgan left #evergreen |
| 17:45 |
pinesol_green |
[evergreen|Dan Wells] Initial compilation of release notes for 2.5 - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=8866470> |
| 17:57 |
|
Sato`kun joined #evergreen |
| 17:58 |
|
jecs left #evergreen |
| 18:08 |
|
smyers_ joined #evergreen |
| 18:48 |
|
kbeswick joined #evergreen |
| 18:50 |
|
kbeswick joined #evergreen |
| 18:58 |
|
kbeswick joined #evergreen |
| 19:02 |
|
hopkinsju joined #evergreen |
| 19:13 |
dbwells |
After much gnashing of teeth, I finally have updated RC1 bits in the usual places. Please feel free to grab them and test if you are so inclined. |
| 19:15 |
dbwells |
I haven't been able to update the downloads page, as it is currently locked by another editor. At this point, I guess that part will have to wait for tomorrow. |
| 19:16 |
* dbwells |
head for home |
| 19:18 |
* dbwells |
listens to that command to himself :) |
| 19:46 |
|
kbeswick joined #evergreen |
| 19:56 |
|
j_scott joined #evergreen |
| 20:34 |
|
stevenyvr2 left #evergreen |
| 21:11 |
|
hopkinsju joined #evergreen |
| 21:52 |
|
kbeswick joined #evergreen |
| 23:56 |
|
stevenyvr2 joined #evergreen |
| 23:57 |
|
stevenyvr2 left #evergreen |
