| Time |
Nick |
Message |
| 00:57 |
|
dcook joined #evergreen |
| 03:13 |
|
jonadab joined #evergreen |
| 03:55 |
|
dbwells_ joined #evergreen |
| 04:31 |
|
gsams joined #evergreen |
| 06:55 |
|
TARA joined #evergreen |
| 06:57 |
|
jonadab joined #evergreen |
| 07:08 |
|
agoben joined #evergreen |
| 07:22 |
|
rjackson_isl joined #evergreen |
| 08:05 |
|
ericar joined #evergreen |
| 08:37 |
|
maryj joined #evergreen |
| 08:40 |
|
mmorgan joined #evergreen |
| 08:43 |
|
TARA joined #evergreen |
| 08:54 |
|
Callender joined #evergreen |
| 09:00 |
|
Dyrcona joined #evergreen |
| 09:08 |
|
bos20k joined #evergreen |
| 09:18 |
csharp |
so does anyone out there in Evergreen-land allow their patrons to place "unfillable holds"? we have gotten consistent suggestions for improvement from our patrons that indicate that they want to be able to place a hold on a range-protected title even if they know they won't get the copy for a while |
| 09:19 |
csharp |
I'm hoping the "unfillable holds" placement option would help with that use case |
| 09:21 |
tsbere |
csharp: I believe there is "age protection only - place anyway?" functionality in there |
| 09:21 |
mmorgan |
csharp: NOBLE allows placement of holds on on order and ttles where items are age protected. |
| 09:21 |
csharp |
oh - I'll have to look at that |
| 09:21 |
miker |
yeah, I'm pretty sure you can do that with permissions |
| 09:21 |
tsbere |
Because "unfillable" covers a lot more than just age protected. Like "this electronic resource won't ever have *copies*...." |
| 09:22 |
miker |
.OVERRIDE permissions, specifically |
| 09:22 |
csharp |
right |
| 09:24 |
mmorgan |
csharp: Our patrons have the permission ITEM_AGE_PROTECTED.override |
| 09:25 |
csharp |
oooohhh |
| 09:25 |
mmorgan |
We also have the library setting Auto-Override Permitted Hold Blocks (Patrons) set to true, so patrons don't have to click to override. |
| 09:25 |
csharp |
mmorgan++ tsbere++ miker++ # thanks for the tips |
| 09:29 |
|
jvwoolf joined #evergreen |
| 09:36 |
|
TARA joined #evergreen |
| 09:50 |
|
kmlussier joined #evergreen |
| 09:51 |
kmlussier |
Good morning #evergreen! |
| 09:52 |
kmlussier |
@coffee [someone] |
| 09:52 |
* pinesol_green |
brews and pours a cup of Kenya Mamuto Kirinyaga, and sends it sliding down the bar to kmlussier |
| 09:52 |
kmlussier |
@tea [someone] |
| 09:52 |
* pinesol_green |
brews and pours a pot of Huang Shan Mao Feng Green Tea, and sends it sliding down the bar to book` (http://ratetea.com/tea/teavivre/huang-shan-mao-feng-green-tea/6041/) |
| 09:52 |
kmlussier |
Yay! pinesol_green picked me for once! |
| 10:00 |
|
maryj joined #evergreen |
| 10:01 |
tsbere |
Anyone want to take a look at my MARC::File::USMARC changes? I would like a second opinion on them before I think about putting something like that in MVLC's production system. https://github.com/perl4lib/marc-perl/pull/4 |
| 10:08 |
|
abowling joined #evergreen |
| 10:30 |
gmcharlt |
miker: jeffdavis: please note my update on bug 1609556 |
| 10:30 |
pinesol_green |
Launchpad bug 1609556 in Evergreen "SRU/Z39.50 slowness when retrieving holdings" [Undecided,Fix committed] https://launchpad.net/bugs/1609556 |
| 10:31 |
gmcharlt |
tl;dr version: the change in output would be a blocker for backporting; my follow-up restores the previous behavior while retaining the performance speedup |
| 10:32 |
miker |
gmcharlt: applying |
| 10:33 |
miker |
gmcharlt: would you like me to apply to 2.10 as well, or did you already? |
| 10:33 |
|
Dyrcona joined #evergreen |
| 10:33 |
gmcharlt |
miker: I'll take care of backporting |
| 10:33 |
miker |
kk |
| 10:34 |
pinesol_green |
[evergreen|Galen Charlton] LP#1609556: (follow-up) restore previous 852$d output - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=67a67b7> |
| 10:38 |
pinesol_green |
[evergreen|Dan Wells] LP#1611495 Don't use .xml for MARC21 files in Vandelay Export - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=552e5fa> |
| 10:42 |
|
sarabee joined #evergreen |
| 10:44 |
|
maryj joined #evergreen |
| 10:47 |
gmcharlt |
kmlussier: around for a quick question? |
| 10:49 |
kmlussier |
gmcharlt: I'm here now |
| 10:50 |
gmcharlt |
kmlussier: I'm considering this for backporting to 2.10: http://git.evergreen-ils.org/?p=Evergreen.git;a=blobdiff;f=Open-ILS/src/templates/opac/myopac/hold_history.tt2;h=9aae602297abd647c877db4b58483f9d85bbeb5b;hp=3b8abb93108a8484a90705c0bc800f31e121271b;hb=463ac7ecfe29760e6f520e97e7145813c939ead9;hpb=4c92d095da106a4c2a54bf26e392d5ad57938f4d |
| 10:50 |
pinesol_green |
gmcharlt: [evergreen|Kathy Lussier] LP#1576502 Fulfilled holds also should not display as active - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=463ac7e> |
| 10:50 |
pinesol_green |
gmcharlt: [evergreen|Kathy Lussier] LP#1575177 Add text informing users they cannot add survey questions - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4c92d09> |
| 10:50 |
gmcharlt |
and my question is this: whence the /Active On/Activate/ in the patch? |
| 10:52 |
gmcharlt |
it feels like it snuck in; at any rate, it doesn't seem on point with respect to the bug |
| 10:52 |
kmlussier |
gmcharlt: Just a sec...it was a long time ago and I need to refresh my memory |
| 10:52 |
gmcharlt |
sure |
| 10:54 |
kmlussier |
gmcharlt: OK, it looks like I addressed it in the original bug report where I tried to add it to the Terran's original change. https://bugs.launchpad.net/evergreen/+bug/1275118/comments/3 |
| 10:54 |
pinesol_green |
Launchpad bug 1275118 in Evergreen "Holds history displays canceled holds as active" [Medium,Fix released] |
| 10:55 |
kmlussier |
gmcharlt: I think I was trying to make it consistent with what displays in the patron's list of current holds. But, you're right, it's not really on point with the bug description. |
| 10:58 |
gmcharlt |
kmlussier: I'm not a fan of "Activate" as the column heading, as it's a verb, but there's no action one can take in that column |
| 10:58 |
gmcharlt |
but that said, I don't feel strongly about it, so I'm inclined to backport as is on the basis of making things more consistent |
| 10:59 |
gmcharlt |
and discussion about the heading can be the subject of a new bug |
| 11:00 |
kmlussier |
Yes, I can see your point. At the time, I was thinking Activate was a better column heading, but today, "Active On" seems better. I could go with that as long as it's the same in both places. |
| 11:00 |
gmcharlt |
@coinflip |
| 11:00 |
pinesol_green |
gmcharlt: It reads like a Nigerian 419 scam, but I think it is a sincere question sent to the wrong list. |
| 11:00 |
gmcharlt |
@decide "Active On" or "Activate" |
| 11:00 |
pinesol_green |
gmcharlt: go with Active On |
| 11:01 |
gmcharlt |
there we have it! ;) |
| 11:01 |
gmcharlt |
I'll backport as is, then open a new bug |
| 11:06 |
kmlussier |
gmcharlt: Thanks. If you like, I can create a branch for the new bug. |
| 11:09 |
gmcharlt |
kmlussier: sure. the new bug is bug 1611815 |
| 11:09 |
pinesol_green |
Launchpad bug 1611815 in Evergreen "use "Active On" rather than "Activate" as header in TPAC holds tables" [Undecided,New] https://launchpad.net/bugs/1611815 |
| 11:11 |
kmlussier |
My memory is beginning to clear. I think the reason I didn't like "Active On" is because, for unsuspended holds, the user might think it should be listing the date the hold was placed. Maybe Activate Date is better, but it takes up more space. |
| 11:11 |
* kmlussier |
hates semantics |
| 11:12 |
tsbere |
kmlussier: "Restore On"? |
| 11:13 |
gmcharlt |
a possibility for a long-term improvement would be consolidating the "Active On", "Active", "Date Fulfilled", and "Status" column into a single status column |
| 11:14 |
kmlussier |
Yes, actually, I think that makes sense. Because you don't really care what the Activation date is unless it's suspended. Maybe I'll look at that before the 2.11 cutoff, but do the simpler branch for backport to 2.10 |
| 11:23 |
gmcharlt |
kmlussier: +1 |
| 11:42 |
JBoyer |
mmorgan, Dyrcona, either of you around for a quick CommCAT question? |
| 11:42 |
* mmorgan |
is |
| 11:43 |
JBoyer |
Do you know what depth of shortname is set as SHAREit's NCIP Agency? System or branch? |
| 11:45 |
mmorgan |
I'm pretty sure it's branch, but Dyrcona would know better. Let me look at a few notes. |
| 11:45 |
JBoyer |
NCIP To Agency is the actual setting name, had to look it up. |
| 11:46 |
JBoyer |
Next Q then, are users required to pick up requests at their home library or the main branch of a multibranch system? |
| 11:46 |
* JBoyer |
isn't enjoying all this last minute research. :-/ |
| 11:47 |
* tsbere |
assumes "home library" on that last one |
| 11:50 |
|
bmills1 joined #evergreen |
| 11:52 |
mmorgan |
Sorry, had to take a phone call. |
| 11:52 |
bshum |
@coin |
| 11:52 |
pinesol_green |
bshum: tails |
| 12:00 |
|
brahmina joined #evergreen |
| 12:03 |
|
Christineb joined #evergreen |
| 12:03 |
mmorgan |
JBoyer: Our users can pick up requests from whatever branch they choose when they login to comcat, there's no home library requirement |
| 12:04 |
tsbere |
I could have sworn that pickup library requested wasn't passed back through the NCIP request to Evergreen. I could be wrong or outdated though. |
| 12:10 |
* mmorgan |
isn't so familiar with the NCIP setup, more familiar with the user side of things. |
| 12:10 |
JBoyer |
tsbere, it's not to my knowledge, but SHAREit does have an option to allow you to just pick something that's printed on the book jacket. It will listen to what you tell it in LookupUserResponse, but I can't get that fixed in a week. (probably...) |
| 12:12 |
JBoyer |
mmorgan, do you know how that's communicated to the libs, just printed on the book jackets or do the Eg holds point to the right place, etc.? Related: there's not an entry for each branch of libraries, right? Just 1 login location per library sytem/ |
| 12:12 |
JBoyer |
? |
| 12:12 |
JBoyer |
1 login location per branch would allow this easily, but also be a lot more hassle to setup. |
| 12:15 |
mmorgan |
JBoyer: EG holds know all the correct information about the pickup point. |
| 12:15 |
tsbere |
JBoyer: I probably have old information in my head due to not previously being all that involved in the entire thing and not keeping up on what issues were fixed. |
| 12:16 |
mmorgan |
We have one login per branch. |
| 12:16 |
mmorgan |
All our actual physical libraries are at the branch level. |
| 12:17 |
JBoyer |
Aha! That's why that works without any hassle. We have 1 login per "info express pickup point" which tends to only be the main branch of a multibranch system. (maybe multiple if they're quite large) |
| 12:18 |
JBoyer |
INFo Express is our statewide library material courier system since that likely made no sense to anyone else. |
| 12:18 |
mmorgan |
That does sound more complicated. |
| 12:18 |
JBoyer |
It certainly has been so far! :) |
| 12:20 |
JBoyer |
Which means to do everything I need, I need to teach NCIPServer how to: target holds at the system level for RequestItem regardless of the ToAgencyID depth, lookup patron settings and return their preferred holds pickup library in the LookupUserResponse, and also not break anything in CommCAT. |
| 12:20 |
JBoyer |
Hurray! |
| 12:21 |
JBoyer |
I'm thinking there's going to be some ugly, ugly hardcoding in the next week, and I'll have some nicer things to share later. |
| 12:22 |
JBoyer |
Thanks for the help tsbere and mmorgan, very informative. |
| 12:22 |
JBoyer |
tsbere++ |
| 12:22 |
JBoyer |
mmorgan++ |
| 12:22 |
tsbere |
JBoyer: What if their preferred pickup point isn't actually in the ToAgencyId system? |
| 12:23 |
JBoyer |
That's another restriction that we've chosen. For the resource sharing system you pick up and return at your home library, period. So I'd just pick their home_ou in that case. |
| 12:24 |
JBoyer |
I know we'll have some of that since we have so many districts in close proximity and people go hither and yon for work. |
| 12:33 |
|
agoben joined #evergreen |
| 12:36 |
|
yboston joined #evergreen |
| 13:02 |
|
rlefaive joined #evergreen |
| 13:24 |
|
ericar_ joined #evergreen |
| 13:28 |
|
TARA joined #evergreen |
| 13:43 |
|
jvwoolf left #evergreen |
| 14:17 |
|
agoben joined #evergreen |
| 14:21 |
|
tarac_ joined #evergreen |
| 14:31 |
kmlussier |
Heads up - the developer meeting will be starting in 29 minutes |
| 14:52 |
|
agoben joined #evergreen |
| 14:56 |
|
DPearl joined #evergreen |
| 14:58 |
* kmlussier |
can run the meeting, but will gladly hand the responsibility to somebody else if they have a burning desire to run it. |
| 15:00 |
kmlussier |
crickets |
| 15:00 |
* JBoyer |
's desire doesn't burn, but is present. :) |
| 15:01 |
kmlussier |
OK, let's get this shindig started! |
| 15:01 |
kmlussier |
#startmeeting Evergreen Development Meeting, 10 August 2016 |
| 15:01 |
pinesol_green |
Meeting started Wed Aug 10 15:01:20 2016 US/Eastern. The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:01 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:01 |
pinesol_green |
The meeting name has been set to 'evergreen_development_meeting__10_august_2016' |
| 15:01 |
kmlussier |
#link http://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2016-08-10 |
| 15:01 |
kmlussier |
Please introduce yourselves with the #info command. |
| 15:01 |
miker |
#info miker = Mike Rylander, ESI |
| 15:02 |
DPearl |
#info DPearl = Dan Pearl, C/W MARS |
| 15:02 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 15:02 |
agoben |
#info agoben is Anna Goben, Evergreen Indiana |
| 15:02 |
berick |
#info berick Bill Erickson, KCLS |
| 15:02 |
JBoyer |
#info JBoyer Jason Boyer, Evergreen Indiana |
| 15:02 |
gmcharlt |
#info gmcharlt = Galen Charlton, ESI |
| 15:02 |
Dyrcona |
#info Dyrcona Jason Stephenson, C/W MARS |
| 15:02 |
dbwells |
#info dbwells is Dan Wells, Hekman Library (Calvin College) |
| 15:03 |
remingtron |
#info remingtron is Remington Steed, Hekman Library (Calvin College) |
| 15:04 |
kmlussier |
I'll move forward in the agenda, but feel free to introduce yourself if you arrive late. |
| 15:04 |
kmlussier |
#topic Action Items from Last Meeting |
| 15:04 |
kmlussier |
#info developers to continue looking at Sqitch, particularly release-building options. Bug #1521693 has been updated. berick is putting it on the back-burner for now. |
| 15:04 |
pinesol_green |
Launchpad bug 1521693 in Evergreen "Investigate using Sqitch for database change management" [Wishlist,New] https://launchpad.net/bugs/1521693 |
| 15:05 |
kmlussier |
gmcharlt to review a few outstanding OpenSRF patches/pull requests |
| 15:05 |
kmlussier |
Any updates gmcharlt? |
| 15:05 |
gmcharlt |
kmlussier: still on my plate; I will cut a 2.5-alpha on Friday |
| 15:06 |
gmcharlt |
#action gmcharlt will cut OpenSRF 2.5-alpha on 12 August |
| 15:06 |
kmlussier |
gmcharlt: Thanks! |
| 15:06 |
kmlussier |
miker will email the list with a proposed schedule for 2.11 and a list of pending bugs/pullrequests |
| 15:06 |
kmlussier |
That was done, miker, right? |
| 15:06 |
miker |
the schedule is out |
| 15:07 |
miker |
the list, I churned through a bit yesterday |
| 15:07 |
miker |
I'll be trying to set aside some time friday to build a "please look at these" list |
| 15:07 |
miker |
I've pinged a couple folks privately about a few |
| 15:08 |
miker |
and have been pinged about a couple |
| 15:08 |
kmlussier |
#info miker emailed a 2.11 schedule to the list and is working through pending bugs/pullrequests. |
| 15:08 |
kmlussier |
#action miker will build a "please look at these list" of pullrequests. |
| 15:09 |
kmlussier |
dbwells will email the list with an introduction to the 2.11 release manager and buildmasters |
| 15:09 |
kmlussier |
dbwells: Did that happen? I can't recall. |
| 15:09 |
dbwells |
That was a bogus action item, only the one after that is real. |
| 15:09 |
jeff |
that one was just a decoy... |
| 15:09 |
kmlussier |
Oh, I see. I'm so easily fooled by decoys. :) |
| 15:10 |
dbwells |
The wiki is updated :) |
| 15:10 |
kmlussier |
#info dbwells sent an introductory email to the 2.11 release manager and buildmasters |
| 15:10 |
kmlussier |
dbwells++ |
| 15:10 |
jeff |
figment of our collective imagination... like my appearance here. |
| 15:10 |
kmlussier |
gmcharlt and Dyrcona to summarize results of this discussion on the wiki for future use by release maintainers. |
| 15:10 |
|
ericar_ joined #evergreen |
| 15:11 |
kmlussier |
"This discussion" refers to guidelines for bug fix vs.new feature. |
| 15:11 |
kmlussier |
Any updates gmcharlt and Dyrcona? |
| 15:11 |
gmcharlt |
no; considered us reminded |
| 15:11 |
Dyrcona |
yeah, hasn't happened, yet. |
| 15:12 |
kmlussier |
#action gmcharlt and Dyrcona to create guidelines on the wiki to determine what is a bug fix vs. new feature. |
| 15:12 |
kmlussier |
I changed the action item a bit to help next month's meeting facilitator. |
| 15:12 |
Dyrcona |
I'm sure you'll thank yourself in the future. :) |
| 15:12 |
kmlussier |
#info dbwells created a bug report with proposed changes for ingest speed improvements. The changes have been pushed. |
| 15:13 |
dbwells |
gmcharlt++ and miker++ for getting it wrapped up |
| 15:13 |
kmlussier |
Dyrcona: If you look at the last item on the agenda, you'll see I have no intention of being next month's meeting facilitator. ;) |
| 15:13 |
* gmcharlt |
volunteers in advance to faciliate |
| 15:13 |
|
bmills joined #evergreen |
| 15:13 |
kmlussier |
gmcharlt++ |
| 15:13 |
DPearl |
gmcharlt++ |
| 15:14 |
kmlussier |
gmcharlt: I can hand over the controls right now if you want practice. |
| 15:14 |
kmlussier |
#topic OpenSRF Release Info |
| 15:14 |
gmcharlt |
so yeah... |
| 15:14 |
gmcharlt |
#info OpenSRF 2.5-alpha to be cut 12 August |
| 15:16 |
bshum |
gmcharlt: Are you planning to do anything about mod_perl and moving that over as a dependency in Evergreen instead of OpenSRF? |
| 15:16 |
gmcharlt |
hmm |
| 15:16 |
miker |
bshum: what's the aim? |
| 15:16 |
gmcharlt |
I think general release of 2.5.0 can wait to occur when EG 2.11 is released |
| 15:16 |
gmcharlt |
so we could do it then |
| 15:17 |
bshum |
miker: The reason I ask is cause we have conflicting decisions to make over how mod_perl is done right now. |
| 15:17 |
miker |
I'm still not following, sorry |
| 15:17 |
bshum |
Basically we have to add something to enable it for Jessie and Trusty builds |
| 15:17 |
gmcharlt |
and my preference is to have mod_perl end up on the Evergreen side; there's nothing in OpenSRF itself that requires mod_perl |
| 15:17 |
bshum |
There's a bug now with apache where it used to ship on, but it's been off lately, and people get errors trying to start Evergreen later cause it's disabled |
| 15:18 |
Dyrcona |
Does OpenSRF even really need Apache? |
| 15:18 |
bshum |
Moving it from OpenSRF to Evergreen is just a related issue, to making sure it's turned on in the first place |
| 15:18 |
miker |
Dyrcona: it does for the gateway/translator/websockets stuff |
| 15:18 |
miker |
but not mod_perl specifically |
| 15:18 |
bshum |
I don't really care where we have it, just so long as it gets turned on somewhere. |
| 15:18 |
gmcharlt |
for context: bug 1579219 |
| 15:18 |
pinesol_green |
Launchpad bug 1579219 in OpenSRF "don't require mod_perl as an OpenSRF dependency" [Wishlist,New] https://launchpad.net/bugs/1579219 |
| 15:19 |
bshum |
And other context https://bugs.launchpad.net/opensrf/+bug/1585042 |
| 15:19 |
pinesol_green |
Launchpad bug 1585042 in OpenSRF 2.4 "Enable mod_perl by default for new OpenSRF installations for Debian Jessie and Ubuntu Trusty" [Medium,New] - Assigned to Galen Charlton (gmc) |
| 15:20 |
miker |
I'm agnostic, as I won't likely be the implementor |
| 15:20 |
gmcharlt |
I'm more than happy to do the implementation |
| 15:21 |
kmlussier |
gmcharlt: Can I add that as an action item for something to be done in time for the .0 release? |
| 15:21 |
gmcharlt |
kmlussier: sure |
| 15:22 |
kmlussier |
#action gmcharlt to move the mod_perl dependency from OpenSRF to the Evergreen side in time for the 2.5.0 release |
| 15:23 |
kmlussier |
Is there anything else to discuss for OpenSRF? |
| 15:23 |
kmlussier |
Going once, going twice... |
| 15:23 |
kmlussier |
#topic Evergreen 2.11 update |
| 15:24 |
kmlussier |
miker: Anything to add to what you reported above? |
| 15:24 |
miker |
yes, a little |
| 15:24 |
miker |
first, dbwells quietly release the alpha last monday |
| 15:24 |
miker |
er, weds |
| 15:24 |
miker |
it builds! |
| 15:25 |
miker |
second, I have 2 questions for the room |
| 15:25 |
miker |
1) merging the webclient branch |
| 15:25 |
* miker |
gets link |
| 15:25 |
miker |
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/gmcharlt/webstaff-sprint3 |
| 15:26 |
miker |
sprint 3 (admin/reports) is done now. we may be able to slip in one more html -> ng UI update in the next week or so |
| 15:27 |
dbwells |
(7/29 was the alpha build date, and the downloads page was updated) |
| 15:27 |
miker |
would anyone like some time to play with the branch before it's merged? |
| 15:27 |
miker |
IOW, shall we merge it post-beta, as an exception |
| 15:27 |
kmlussier |
For the alpha release, should a message go out on the list so that people know about it? |
| 15:27 |
miker |
kmlussier: it should have, and that's on me |
| 15:28 |
miker |
I can send one out |
| 15:28 |
kmlussier |
miker: OK, I'll add that as an action item. |
| 15:28 |
kmlussier |
miker: Also, we'll be looking at the sprint 3 branch here, but I don't know how much testing we can do before Wednesday. I've already used some of the admin interfaces. |
| 15:29 |
kmlussier |
#action miker to send message to e-mail list announcing alpha release. |
| 15:30 |
miker |
re merging webclient, I'm happy with waiting a bit ... but, as always, it's preproduction. we will be backporting significant bug fixes, though, as agreed to before |
| 15:30 |
miker |
opinions on timing? |
| 15:30 |
dbs |
#info dbs is Dan Scott, Laurentian University |
| 15:30 |
kmlussier |
miker: Do you have an idea of whether many sites are using the web client in production? |
| 15:31 |
miker |
I don't believe there are many. maybe 1 or 2? none that I'm positive do use it |
| 15:31 |
kmlussier |
I think it affects the decision on whether we merge post-beta. If people are using it in production, there may be a higher chance of breakage happening for them at .0 release time. |
| 15:31 |
Dyrcona |
I'd prefer sprint3 going in at/before the beta rather than after. |
| 15:31 |
JBoyer |
I'd think the sooner the better provided all of the existing interfaces are still in the XUL client. If someone is using a pre-pro client in production, they should be paying enough attention to hit the testing rather hard on this update. |
| 15:32 |
miker |
JBoyer: they do exist |
| 15:32 |
gmcharlt |
we could send an olly-olly-oxen-free to open-ils-general |
| 15:33 |
kmlussier |
Looks like we just lost most of the ESI crew |
| 15:33 |
Dyrcona |
Ok. Who tripped over the phone line? ;) |
| 15:33 |
|
Shae joined #evergreen |
| 15:33 |
|
graced joined #evergreen |
| 15:33 |
|
miker joined #evergreen |
| 15:33 |
JBoyer |
And I thought I might be knocked off because of the weather here, heh. |
| 15:33 |
gmcharlt |
was it something I said? ;) |
| 15:33 |
miker |
doh... quassel core went sad |
| 15:34 |
dbwells |
I haven't perused the code in a while now, but if it is generally true that the chance of the merge breaking existing client interfaces is low, I think merging sooner is better. |
| 15:34 |
miker |
gmcharlt: we can, though I'm inclined to vote with Dyrcona and JBoyer ... and dbwells :) |
| 15:34 |
JBoyer |
Plus there's the fact that alphas are generally unstable, now's the best time to find where the problems lie. |
| 15:34 |
miker |
dbwells: it's exceedingly low (though not non-zero) |
| 15:34 |
gmcharlt |
miker: yeah, I was thinking more in terms of identifying the folks who then get asked to TEST, TEST, and MOAR TEST :) |
| 15:34 |
kmlussier |
I'm inclined to agree that we should merge before beta. I can commit to putting some testing in by next week. |
| 15:35 |
miker |
gmcharlt: +1 |
| 15:35 |
|
jyorio joined #evergreen |
| 15:35 |
gmcharlt |
but yeah, I'm also in favor in merging before beta |
| 15:35 |
|
akilsdonk joined #evergreen |
| 15:35 |
kmlussier |
Who would like to volunteer to send a message out to the list to get testers? |
| 15:36 |
miker |
I'll do it while I announce alpha |
| 15:37 |
kmlussier |
#action miker to send message to list seeking help to test web client sprint 3 |
| 15:37 |
kmlussier |
Any other updates for 2.11? Other areas where help is needed? |
| 15:37 |
miker |
second question: we have 5 weeks between beta and GA ... would anyone like to steal a week from RC and make it 4, giving us 2 more weeks until beta? |
| 15:38 |
JBoyer |
+1 |
| 15:38 |
miker |
reason being: folks (including me) have been focusing on bug fix branches recently |
| 15:38 |
kmlussier |
+1 |
| 15:38 |
miker |
so, thee will likely be fewer bugs to merge post-beta |
| 15:38 |
miker |
there |
| 15:39 |
miker |
preexisting bugs, that is |
| 15:39 |
Dyrcona |
+1 |
| 15:39 |
kmlussier |
Any objections to moving beta back a week? |
| 15:39 |
* berick |
does not object |
| 15:39 |
kmlussier |
miker: The new beta date would be August 24? |
| 15:39 |
miker |
(I'd still like to merge sprint3 by mid-next-week) |
| 15:40 |
miker |
kmlussier: yes. I'll reply to the schedule email to announce that, barring objections |
| 15:40 |
kmlussier |
I feel like this release snuck up on me, so the extra week will be nice. |
| 15:40 |
miker |
kmlussier: ME TOO |
| 15:40 |
miker |
it's been a summer... |
| 15:41 |
kmlussier |
OK, hearing no objections, it looks like it will be August 24 |
| 15:41 |
kmlussier |
#info New 2.11 beta release date to be August 24. |
| 15:41 |
kmlussier |
Anything else before we move on to the next topic? |
| 15:42 |
miker |
nope, thanks |
| 15:42 |
* kmlussier |
updated the dev calendar with the new beta date. |
| 15:42 |
kmlussier |
#topic 2016 Hack-a-way update |
| 15:43 |
kmlussier |
JBoyer, agoben: You have the floor. |
| 15:43 |
|
rhamby joined #evergreen |
| 15:43 |
|
barbara joined #evergreen |
| 15:43 |
agoben |
Things are in good shape; we're contracted for the space as shared before. |
| 15:43 |
agoben |
A couple of options for lodging that you should be aware of: |
| 15:44 |
agoben |
a) The block has to be called on if you want to get into it (and it is for the lower cost rooms) |
| 15:45 |
agoben |
Alternately, the facility has some houses. If interested, I can facilitate participation in a group reservation for one of the houses. There would be 6 private suites included at $75/night for interested parties. |
| 15:46 |
agoben |
Also, if there's anything in particular participants really do or don't want to see on the schedule for evenings, please send them my way. |
| 15:46 |
kmlussier |
Adding a link to the wiki page with the lodging info: |
| 15:46 |
kmlussier |
#link http://wiki.evergreen-ils.org/doku.php?id=hack-a-way-2016 |
| 15:47 |
agoben |
I can get the travel doc put together for participants next week. |
| 15:47 |
kmlussier |
Does anyone have any questions for agoben? |
| 15:48 |
kmlussier |
The option for a house is interesting. I assume the $75 rate is lower than the rate for a typical hotel room? |
| 15:48 |
* kmlussier |
doesn't remember seeing it anywhere. |
| 15:48 |
JBoyer |
Depending on the room they normally range from $94 to 154. |
| 15:48 |
agoben |
Yes, the pricing at the Inn ranges between $80 and $200/night depending on which room type you select. |
| 15:49 |
kmlussier |
JBoyer / agoben: Thanks! |
| 15:49 |
kmlussier |
Any other questions about the hack-a-way. |
| 15:50 |
kmlussier |
#topic Mentoring new developers in the community |
| 15:51 |
kmlussier |
I added this topic as a follow-up to the discussion we had at the last hack-a-way regarding growing contributors in the community and then the e-mail thread where I suggested a mentoring program. |
| 15:52 |
kmlussier |
I never applied for the grant because there didn't seem to be much interest from developers, but I still would like to pursue the topic a bit. Not to be resolved today, but maybe as a precursor to a discussion for the November hack-a-way. |
| 15:54 |
kmlussier |
Basically, I'm curious to people's thoughts on starting some type of mentoring program, and, if so, what you all think would be effective. Is the program I proposed something that would be workable or do you all think it's more effective to do programs like GSoC as we've done in the past? |
| 15:55 |
kmlussier |
I personally feel like GSoC and Outreach (formerly OPW) weren't particularly effective, which is why I was suggesting an alternate approach. |
| 15:55 |
kmlussier |
#link http://markmail.org/message/xts3sxx2zakad7mw |
| 15:56 |
Dyrcona |
I like the idea of a bootcamp. However, it may be too much for us to do as its own event. |
| 15:56 |
kmlussier |
Dyrcona: Too much because of time constraints? |
| 15:56 |
Dyrcona |
Perhaps, it could be done at the hack-away or as part of the hackfest at the conference? |
| 15:57 |
Dyrcona |
kmlussier: Yes, more or less. |
| 15:57 |
gmcharlt |
I think it could be done attached to the conference or hackfest |
| 15:57 |
Dyrcona |
I'm also not sure how much interest there is on the part of those being mentored. |
| 15:58 |
gmcharlt |
but as something that gets its own day (or two?) with nothing else going on |
| 15:58 |
kmlussier |
gmcharlt: Yes, I agree. If we do something, the participants should be able to focus on it. |
| 15:59 |
kmlussier |
Dyrcona: When you see see there might not be interest, do you mean not much interest in being mentored or something else? |
| 15:59 |
DPearl |
That's a lot of material to cover in one day. I think I'm more in favor of canned tutorial with exercises that could be done at the learner's pace. |
| 16:00 |
DPearl |
That could be accessed any time, so the on-ramp is available on demand. |
| 16:00 |
Dyrcona |
kmlussier: I don't hear a lot of people asking about how to get started coding for Evergreen. It comes up in IRC from time to time, but is there enough interest for a stand alone, multi-day event? |
| 16:00 |
kmlussier |
Well, it might be something that could start with an in-person boot camp and then continue remotely. I think there is a value to getting to seeing things in person. |
| 16:01 |
kmlussier |
Dyrcona: When I originally posed the question, most of the interest came from people who were interested in learning more. But you might be right. |
| 16:02 |
kmlussier |
We're at the one-hour mark, but I just wanted to put the question out there to get people started in thinking about it. Maybe we can talk some more about it as we get closer to the hack-a-way. |
| 16:03 |
kmlussier |
I'm also willing to try to find some other grant to help us fund something if we need to cover travel expenses, time spent by mentors, canned presentations, etc. |
| 16:03 |
JBoyer |
Something else to think about might be where to advertise such a thing? There may be interest if there were more awareness. |
| 16:03 |
dbwells |
remingtron and I recently gave some Evergreen tech. overview presentations at Code4Lib midwest. Could be used as part of a tech primer "course" of some sort. |
| 16:03 |
kmlussier |
JBoyer: Before getting to advertising it, I think we need to start with who the best audience is. |
| 16:04 |
JBoyer |
kmlussier, sure, those two things are related. |
| 16:04 |
kmlussier |
dbwells: Awesome! Is that something you would be willing to post to the wiki? |
| 16:04 |
Bmagic |
#info Bmagic = Blake GH, MOBIUS |
| 16:04 |
kmlussier |
JBoyer: My thought was that working with people already working with libraries is better. I think that's what the problem was with programs like GSoC. There was no reason to continue with the project once the internship was done. |
| 16:05 |
kmlussier |
But I could be wrong on that. |
| 16:05 |
JBoyer |
Makes sense. (worked for me!) |
| 16:05 |
kmlussier |
OK, I want to wrap things up. |
| 16:05 |
Dyrcona |
Yeah. I think doing something at the conference is a decent place to start. |
| 16:05 |
kmlussier |
#topic Volunteer to organize / lead the September 7, 2016 meeting |
| 16:06 |
dbwells |
kmlussier: It's very much an amalgamation of existing content, so I am not sure how much value the slides have all on their own, but I'll find a place for them on the wiki somewhere. |
| 16:06 |
kmlussier |
gmcharlt volunteered to lead the next meeting. gmcharlt do you also want to be responsible for sending out meeting notices & creating the agenda, or do you want another volunteer to handle that? |
| 16:06 |
kmlussier |
dbwells++ #Thanks! |
| 16:06 |
gmcharlt |
kmlussier: I'll take care of it all |
| 16:06 |
kmlussier |
gmcharlt++ |
| 16:06 |
JBoyer |
gmcharlt++ |
| 16:06 |
kmlussier |
#action gmcharlt will lead the September 2016 meeting. |
| 16:07 |
kmlussier |
Does anyone have anything else before we end the meeting? |
| 16:08 |
kmlussier |
#endmeeting |
| 16:08 |
pinesol_green |
Meeting ended Wed Aug 10 16:08:02 2016 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:08 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-08-10-15.01.html |
| 16:08 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-08-10-15.01.txt |
| 16:08 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-08-10-15.01.log.html |
| 16:08 |
miker |
kmlussier++ |
| 16:08 |
kmlussier |
Thanks everyone! |
| 16:08 |
JBoyer |
kmlussier++ |
| 16:08 |
Dyrcona |
kmlussier++ |
| 16:08 |
Bmagic |
kmlussier++ |
| 16:08 |
Bmagic |
yay, I made it just before it ended! Sorry I was late |
| 16:08 |
kmlussier |
Bmagic: That's okay. We volunteered you for all the things. |
| 16:08 |
gmcharlt |
kmlussier++ |
| 16:09 |
Bmagic |
haha! I figured you would! |
| 16:09 |
JBoyer |
Think he can get it all done in a week> |
| 16:09 |
JBoyer |
? |
| 16:09 |
dbwells |
kmlussier++ |
| 16:09 |
Bmagic |
I've been deep in docker. I have a docker build that makes an evergreen server! |
| 16:10 |
DPearl |
kmlussier++ |
| 16:10 |
kmlussier |
Bmagic++ |
| 16:10 |
|
DPearl left #evergreen |
| 16:15 |
dbs |
kmlussier++ |
| 16:55 |
|
jvwoolf joined #evergreen |
| 17:03 |
|
jvwoolf left #evergreen |
| 17:05 |
Bmagic |
http://docs.evergreen-ils.org/2.1/html/sipserver.html still acurate? git clone git://github.com/atz/SIPServer.git SIPServer ?? |
| 17:05 |
Bmagic |
or is it http://wiki.evergreen-ils.org/doku.php?id=evergreen-admin:sip |
| 17:06 |
Bmagic |
git://git.evergreen-ils.org/SIPServer.git |
| 17:07 |
miker |
Bmagic: the latter. not the github one |
| 17:08 |
Bmagic |
weird, I am using atz in production |
| 17:08 |
miker |
I mean, I'm sure it works. it may even track our branch |
| 17:08 |
miker |
but his is not authoritative |
| 17:11 |
|
mmorgan left #evergreen |
| 17:15 |
dbs |
I think atz's branch is way out of date. |
| 17:16 |
dbs |
yeah, by about 5 years |
| 17:48 |
Bmagic |
dang, well, I guess its good that it still works |
| 17:48 |
Bmagic |
however, I might be saved by the working branch |
| 17:48 |
Bmagic |
git remote add working git://git.evergreen-ils.org/working/SIPServer.git |
| 17:49 |
Bmagic |
then I check out 9b3ca581d92298904652f52b512dc2eb1b153977 |
| 18:13 |
|
sandbergja joined #evergreen |
| 21:10 |
|
dcook joined #evergreen |
| 21:18 |
|
Christineb joined #evergreen |
| 22:17 |
|
phasefx_ joined #evergreen |
| 23:49 |
|
sard joined #evergreen |
| 23:52 |
|
ejk joined #evergreen |
