| Time |
Nick |
Message |
| 00:07 |
|
bshum joined #evergreen |
| 00:07 |
pinesol_green |
All hail the supreme potentate, bshum has arrived! |
| 00:09 |
|
kmlussier joined #evergreen |
| 00:11 |
|
mceraso joined #evergreen |
| 01:58 |
|
jonadab_znc joined #evergreen |
| 02:12 |
|
gsams joined #evergreen |
| 04:54 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:43 |
|
mrpeters joined #evergreen |
| 07:46 |
|
rlefaive joined #evergreen |
| 07:48 |
|
rjackson_isl joined #evergreen |
| 08:01 |
|
ericar joined #evergreen |
| 08:13 |
|
rlefaive joined #evergreen |
| 08:38 |
|
mmorgan joined #evergreen |
| 08:44 |
|
Shae joined #evergreen |
| 08:52 |
|
mrpeters joined #evergreen |
| 09:15 |
|
RoganH joined #evergreen |
| 09:17 |
|
rlefaive joined #evergreen |
| 09:32 |
|
rlefaive joined #evergreen |
| 09:39 |
|
yboston joined #evergreen |
| 09:42 |
|
akilsdonk joined #evergreen |
| 09:49 |
|
terran joined #evergreen |
| 10:13 |
bshum |
SIP-- |
| 10:16 |
|
mllewellyn joined #evergreen |
| 10:21 |
_bott_ |
I've spent the last day in the deep dark world of patron credit... |
| 10:21 |
RoganH |
OK, maybe I need more coffee but someone just asked me about the "designated borrower" feature in Evergreen. Is this something that I'm just blanking on? |
| 10:22 |
_bott_ |
I think patron credit is a little like Fight Club. I couldn't find any record, other than auditor.actor_usr_history's credit_forward_balance that it had been added to. |
| 10:25 |
_bott_ |
So, I wrote a little bit to create a grocery bill & payment to log such mystery money. Would anyone find it useful for a bug/patch? |
| 10:25 |
_bott_ |
https://github.com/grpl-eg/eg_2_8/commit/039d3a93d5da7eacf9b127e9ffde289a6f803fe6 |
| 10:27 |
|
Dyrcona joined #evergreen |
| 10:29 |
bshum |
Hmm |
| 10:29 |
bshum |
Maybe |
| 10:29 |
bshum |
I don't really deal with credits. |
| 10:30 |
mmorgan |
We have turned off patron credits, but it has never made sense to me that patron credits aren't in the money tables. It's money, after all. |
| 10:30 |
bshum |
"Republic credits? Republic credits are no good out here. I need something more real." |
| 10:30 |
_bott_ |
We started using credit for printing payments, and allow people to simply add credit, but I could find no record of the money actually being collected. |
| 10:30 |
* berick |
gives bshum some granola bars |
| 10:31 |
_bott_ |
That commit has some hard coded bits that would need to go away, but it's pretty simple in general. |
| 10:32 |
berick |
bshum: doh! i thought that was a firefly reference. |
| 10:32 |
bshum |
berick: I know I'm ashamed that I just quoted a prequel. |
| 10:32 |
berick |
bshum: you really should be |
| 10:32 |
berick |
;) |
| 10:33 |
dbs |
RoganH: The "designated borrower" rule is only in effect in the Evergreen American League, us Canucks don't know anything about it. |
| 10:33 |
RoganH |
dbs++ |
| 10:33 |
bshum |
RoganH: Maybe they mean something like someone who's allowed to check stuff out on behalf of another patron? |
| 10:33 |
RoganH |
bshum: I'm guessing that's what they mean but not sure |
| 10:33 |
bshum |
Like a family member or someone who's bringing books to homebound users? |
| 10:33 |
dbs |
That would be my more serious guess :) |
| 10:34 |
bshum |
RoganH: I think in our consortium, people call that the "alternate patron checkout" or some other randomness. |
| 10:35 |
RoganH |
bshum: is there a workflow for that? |
| 10:35 |
RoganH |
bshum: beyond just "hey they're in a group together with a note so we load up that other account and check it out" ? |
| 10:36 |
bshum |
RoganH: Basically I guess. |
| 10:36 |
bshum |
RoganH: I think it goes like this: |
| 10:36 |
bshum |
1) patron A placed an item on hold |
| 10:36 |
bshum |
2) item goes through usual capture rounds |
| 10:36 |
bshum |
3) patron B shows up to pick up item for patron A |
| 10:37 |
bshum |
4) staff complain about not being able to check out the item to patron B and conveniently fulfill hold for patron A if they're in the same group, etc. or obviously related |
| 10:37 |
bshum |
For me, the only logical way of expressing a connection is having them in the same group. |
| 10:37 |
bshum |
Otherwise, it isn't fair for the system to "just know" that those users are related. |
| 10:38 |
Dyrcona |
RoganH: IIRC, the beginnings of that and more are in the database and some spots in code, but not actually hooked up to anything. |
| 10:38 |
* Dyrcona |
could be hallucinating again, though. |
| 10:38 |
* bshum |
wants what Dyrcona's having |
| 10:39 |
Dyrcona |
@tea bshum |
| 10:39 |
* pinesol_green |
brews and pours a pot of None, and sends it sliding down the bar to bshum (http://ratetea.com/tea/foojoy/keemun-full-leaf/6686/) |
| 10:39 |
RoganH |
Dyrcona: that's what I thought, I couldn't think of anything that would actually be exposed to front line circ staff and I looked through it again since I miss things sometimes |
| 10:39 |
Dyrcona |
Yeah, seriously, just an iced tea. |
| 10:39 |
RoganH |
Tea sounds good right now, earl grey. |
| 10:39 |
bshum |
RoganH: Oh I should clarify, this is a "we wish evergreen did this" not an actual working feature. |
| 10:40 |
Dyrcona |
bshum: Step 4 needs to be developed/completed. |
| 10:40 |
RoganH |
bshum: I got that. Yeah, and I can see that as a wishlist but this was brought up by someone who doesn't follow development and as a working in production thing. |
| 10:40 |
bshum |
Right. |
| 10:40 |
Dyrcona |
It would be useful for families, and for grad students picking things up for a professor. |
| 10:41 |
RoganH |
Yep. |
| 10:41 |
Dyrcona |
Or the executive/personal assistant combination. |
| 10:41 |
* Dyrcona |
dreams of having a personal assistant. |
| 10:42 |
mmorgan |
RoganH: Could someone be remembering a throwback from another ILS? |
| 10:42 |
RoganH |
mmorgan: What I _think_ they're doing is that they're being told by front line staff about something they do manually with information in alerts and they think it's a software function. |
| 10:43 |
bshum |
RoganH: I was going to say, maybe someone is taking the "Guardian" field in the patron account too seriously. |
| 10:43 |
RoganH |
bshum: Or that. It's not a front line person so I think something is getting lost in translation. |
| 10:44 |
mmorgan |
Ah, ok. Many of our libraries do use the patron alert message for this purpose. |
| 10:44 |
bshum |
Good ol' ident_value2 |
| 10:55 |
terran |
PINES libraries use the alert field to store designated hold picker-uppers, too |
| 10:58 |
bshum |
@quote add <dbs> RoganH: The "designated borrower" rule is only in effect in the Evergreen American League, us Canucks don't know anything about it. |
| 10:58 |
pinesol_green |
bshum: The operation succeeded. Quote #122 added. |
| 11:00 |
* Dyrcona |
loves the smell of fresh VMs in the morning. |
| 11:00 |
|
pmurray left #evergreen |
| 11:00 |
Dyrcona |
Fun with naming branches for remotes: git push jasondev jasondev :) |
| 11:13 |
kmlussier |
RoganH: IIRC, the functionality that was started at the database level was called the "friends" feature. We've talked periodically about fully developing it, but it never makes it to the top of the list. |
| 11:14 |
miker |
kmlussier: there's a decent pile of API code for Friends, too. fwiw |
| 11:14 |
RoganH |
kmlussier: yeah, I remember discussion around it and partial work done but this was in the context of "something my staff use all the time" and that's what threw me. |
| 11:15 |
RoganH |
And I miss stuff sometimes since I get split in a lot of directions so I never assume I'm right though something like this (since I work circ regularly) I would usually know. |
| 11:15 |
miker |
the API is mostly complete, IIRC ... request/accept friends, assign permissions to friends, even check granted permissions, I think |
| 11:15 |
kmlussier |
heh...sounds like a patron note/alert to me. :) |
| 11:16 |
RoganH |
I got email back just a few minutes ago because I emailed and said "I don't think I know anything about this" and he went back to staff who clarified they were just using information in notes and doing stuff by hand. |
| 11:16 |
RoganH |
All of life is a game of using google translate to parsing emails back and forth until you can see how confused everyone gets. |
| 11:23 |
|
rlefaive joined #evergreen |
| 11:39 |
|
bmills joined #evergreen |
| 11:40 |
|
RoganH joined #evergreen |
| 11:43 |
Dyrcona |
Setting up a vm is taking longer than usual because I keep stopping to adjust parts of the automated process. |
| 11:43 |
Dyrcona |
I still haven't automated setting up websockets.... |
| 11:44 |
Dyrcona |
One thing, though, the already scripted bits go faster without SpiderMonkey! |
| 11:44 |
mrpeters |
Dyrcona: we have debs |
| 11:44 |
mrpeters |
crudely, but we have them |
| 11:44 |
Dyrcona |
mrpeters: I have many custom git branches. |
| 11:44 |
mrpeters |
i meant for websockets |
| 11:44 |
Dyrcona |
websockets doesn't take that long on the OpenSRF side. |
| 11:44 |
mrpeters |
from my testing so far, i can do a hand install of opensrf/evergreen |
| 11:45 |
mrpeters |
and then run the debs to install websockets, bower, and grunt |
| 11:47 |
Dyrcona |
I haven't gotten to the Evergreen bit, yet. I think I might just adjust my build and setup scripts to do those steps for me. |
| 11:47 |
Dyrcona |
Think I'll get something to eat. |
| 11:53 |
terran |
Does anyone have a moment to help me with a fieldmapper question? I'm trying to figure out how to get to acq lineitem_detail info and I can't get the syntax right... |
| 11:55 |
terran |
I'm trying to get line item details to print out with the invoice template - more details: https://docs.google.com/document/d/1WvgAcuvxfGgITzNUyHrCoafOhvNmxg39ZQzkCaUemf8/edit?usp=sharing |
| 11:58 |
|
Christineb joined #evergreen |
| 11:58 |
berick |
terran: i think you want FOREACH lid IN entry.lineitem.lineitem_details |
| 11:59 |
terran |
Thank you berick, trying now... |
| 11:59 |
berick |
and from there you can get lid.owning_lib, etc. |
| 12:01 |
mrpeters |
I'm not sure how many are still using Nagios and/or Icinga for monitoring, but I wondered if we might benefit from a git repo where we could contribute various nagios plugin scripts written specifically for evergreen |
| 12:01 |
berick |
you'll also need to make sure entries.lineitem.lineitem_details is in the event definition environment |
| 12:01 |
berick |
terran: ^-- |
| 12:02 |
berick |
and if you want to see the owning_lib name, for example, the environment will need to be extended to entries.lineitem.lineitem_details.owning_lib |
| 12:02 |
berick |
to ensure the values are loaded into the template |
| 12:02 |
* berick |
confirms the default action trigger event environment for the Inovice template does not include lineitem_details |
| 12:03 |
terran |
Oooohhh |
| 12:04 |
terran |
That explains why I'm getting nothing |
| 12:04 |
Stompro |
mrpeters, I think that is a great idea. If you set one up, add a link to the Monitoring page I made on the Wiki - http://wiki.evergreen-ils.org/doku.php?id=evergreen-admin:monitoring |
| 12:04 |
mrpeters |
ah, nice didn't know that was there |
| 12:05 |
mrpeters |
im currently migrating a bunch to a new server, and the thought crossed my mind |
| 12:05 |
mmorgan |
berick: terran: "lineitem_details" or "lineitem_detail"? |
| 12:05 |
Stompro |
It was added in July, so it hasn't been there for very long. I've been going through the process of setting up zabbix monitoring and thought it would be good to have a spot for people to start. |
| 12:05 |
terran |
mmorgan: I'm not clear on that - the schema says lineitem_detail for the table name |
| 12:06 |
berick |
mmorgan: lineitem_details |
| 12:06 |
mrpeters |
maybe a collab branch in Evergreen working would be the way to go, rather than another repo entirely |
| 12:06 |
berick |
you don't want the table name, you want the name of the field on the source object which is used to access the data in the table |
| 12:06 |
Stompro |
The presentation by Michael Tate is full of great info. |
| 12:06 |
mrpeters |
yeah ive seen that one |
| 12:07 |
* mmorgan |
still struggles to crawl up the fm_idl learning curve |
| 12:07 |
berick |
note the "lineitem_details" field in the IDL within the "jub" (acq.lineitem) class. |
| 12:07 |
Stompro |
I'm going to create a repo under working/random for the zabbix stuff I've got so far. |
| 12:08 |
mrpeters |
http://pastie.org/10331714 - check_pgbackup.pl - was the one i was messing with and it gave me the idea |
| 12:08 |
mrpeters |
if you're using eg-db-backup.sh (or really, any script) this will check for the existance of the backup, but it will report an OK status before cron has time to run the backup for that day, if you run it at say, 6AM |
| 12:09 |
mrpeters |
you don't want invalid CRITCAL icinga alerts that there is no backup if it hasn't been attempted yet |
| 12:11 |
mmorgan |
Ah. ok, I see it now. berick++ |
| 12:11 |
mrpeters |
ah, didn't think about using working/random.git thats a good idea |
| 12:12 |
mrpeters |
Stompro: want to start collab/Stompro/monitoring perhaps? |
| 12:12 |
mrpeters |
wouldn't that allow anyone to push to that collab branch? |
| 12:13 |
terran |
berick: my first time playing with action trigger environments... diving in... |
| 12:13 |
mmorgan |
terran++ |
| 12:14 |
Stompro |
mrpeters, sounds good, I'll set that up. |
| 12:15 |
berick |
terran: good luck |
| 12:21 |
terran |
berick++ |
| 12:28 |
Stompro |
mrpeters, working/random collab/stompro/monitoring is now setup. |
| 12:28 |
mrpeters |
awesome!@ |
| 12:30 |
|
bmills joined #evergreen |
| 12:34 |
|
buzzy joined #evergreen |
| 12:39 |
kmlussier |
Should we be adding release notes entries with an .adoc extension now? |
| 12:43 |
kmlussier |
I guess it's a good question for Thursday's DIG meeting. In the meantime, I'll stick with .txt. |
| 12:47 |
RoganH |
kmlussier: you could make up random extensions derived from 50s beat poetry |
| 12:47 |
kmlussier |
RoganH: Sure, I'll do that on a day when I have spare time on my hands. |
| 12:47 |
RoganH |
kmlussier: sometimes you have to make time for the important things in life |
| 12:57 |
dbs |
kmlussier: I'd go directly to .adoc personally |
| 13:04 |
kmlussier |
dbs: Since your recommendation didn't involved beat poetry, I'll go with it. Thanks! |
| 13:10 |
|
jihpringle joined #evergreen |
| 13:10 |
kmlussier |
@hates |
| 13:10 |
pinesol_green |
kmlussier hates git; Launchpad search; Internet Explorer; snow; scheduling meetings; Starbucks; negative balances; undrinkable coffee; winter; blizzards; spam; and dojo interfaces |
| 13:11 |
kmlussier |
@dontcare git |
| 13:11 |
pinesol_green |
kmlussier: The operation succeeded. kmlussier no longer hates git. |
| 13:12 |
kmlussier |
Not ready to love git yet, but I guess I can remove it from my hates. |
| 13:12 |
Dyrcona |
Anyone ever tried the web staff client with versions of node > 0.10.x, i.e. 0.11 or 0.12? |
| 13:13 |
Dyrcona |
I've successfully used 0.10.34 whereas the instructions say 0.10.28, probably 'cause it was most current at the time. |
| 13:14 |
* Dyrcona |
has hates/loves he can't remove. pinesol_green doesn't let him. |
| 13:14 |
Dyrcona |
I suppose I could try 0.12.7, the latest tag. |
| 13:14 |
kmlussier |
Maybe pinesol_green secretly knows that you still love/hate those things? |
| 13:15 |
Dyrcona |
kmlussier: Could be....Could be the presence of spaces in them. |
| 13:15 |
Dyrcona |
;) |
| 13:15 |
kmlussier |
@loves Dyrcona |
| 13:15 |
pinesol_green |
Dyrcona loves git; scripted sign off; sed; OpenBSD; gnu/emacs; and git tag |
| 13:16 |
Dyrcona |
@hates |
| 13:16 |
pinesol_green |
Dyrcona hates MARC; English orthography; Launchpad; RDA; typos; Launchpad Search; printing; NCIP; Launchpad_some_moar; billing even MOAR!; billing; futzing around in GUIs when I could actually get the work done instead of correcting all the horse shit the GUI insists on doing.; and the wifi in the office. |
| 13:16 |
Dyrcona |
I tried removing the wifi in the office. |
| 13:16 |
Dyrcona |
@dontcare "the wifi in the office" |
| 13:16 |
pinesol_green |
Dyrcona: I have no record of Dyrcona's loving or hating the wifi in the office |
| 13:17 |
kmlussier |
Oh, I just assumed you stopped hating MARC. ;) |
| 13:17 |
Dyrcona |
@dontcare the wifi in the office |
| 13:17 |
pinesol_green |
Dyrcona: I have no record of Dyrcona's loving or hating the wifi in the office |
| 13:17 |
kmlussier |
But that's one word, so I guess now. |
| 13:17 |
kmlussier |
s/now/not |
| 13:17 |
Dyrcona |
:) |
| 13:17 |
Dyrcona |
@dontcare and the wifi in the office |
| 13:17 |
pinesol_green |
Dyrcona: I have no record of Dyrcona's loving or hating and the wifi in the office |
| 13:18 |
mmorgan |
Dyrcona: the period at the end, maybe? |
| 13:18 |
jboyer-isl |
maybe including the period, as there isn't one at the end of kmlussier's hates. |
| 13:18 |
jboyer-isl |
Ah, mmorgan beat me. :D Also, leave off the and. |
| 13:19 |
mmorgan |
:-D |
| 13:19 |
Dyrcona |
@dontcare the wifi in the office. |
| 13:19 |
pinesol_green |
Dyrcona: The operation succeeded. Dyrcona no longer hates the wifi in the office.. |
| 13:19 |
Dyrcona |
heh. |
| 13:19 |
Dyrcona |
So simple. |
| 13:19 |
jboyer-isl |
Victory! |
| 13:19 |
Dyrcona |
mmorgan++ jboyer-isl++ |
| 13:19 |
Dyrcona |
Anyway, think I'll try the master branch of node.js. |
| 13:19 |
* Dyrcona |
is crazy like that. |
| 13:20 |
bshum |
Dyrcona: I think I've only tested with the version specified. But berick experimented with older versions of nodejs too |
| 13:20 |
bshum |
http://irc.evergreen-ils.org/evergreen/2014-11-05#i_135615 |
| 13:20 |
bshum |
The one that comes packaged with trusty was 0.10.25 |
| 13:21 |
Dyrcona |
OK. |
| 13:22 |
Dyrcona |
So, I could just install the package, then.... |
| 13:22 |
bshum |
In theory, yes. |
| 13:22 |
bshum |
Not sure where berick left that one. |
| 13:22 |
Dyrcona |
I know I've checked out tag 0.10.34 and used it. |
| 13:22 |
Dyrcona |
I'm lazy and thought I'd just give the master branch a whirl. :) |
| 13:23 |
* Dyrcona |
has spent more time talking/thinking about it than it would actually take to test...so much for lazy. :) |
| 13:23 |
berick |
Makefile.ubuntu-trusty installs the nodejs package |
| 13:23 |
berick |
it should do everything you need |
| 13:24 |
Dyrcona |
berick: It doesn't appear to do that. |
| 13:24 |
Dyrcona |
I've run it already and nodejs is not installed. |
| 13:24 |
bshum |
nodejs-legacy? |
| 13:25 |
Dyrcona |
nope. |
| 13:25 |
bshum |
No that's what's in the makefile |
| 13:25 |
Dyrcona |
p nodejs-legacy - evented I/O for V8 javascript |
| 13:25 |
berick |
Dyrcona: you have to use the ubuntu-trusty-developer make target |
| 13:25 |
berick |
it's not installed w/ the default install |
| 13:25 |
berick |
it's an extra step |
| 13:25 |
bshum |
Oh, developer, makes sense... |
| 13:26 |
Dyrcona |
Well, see, I don't use that target normally. |
| 13:26 |
berick |
that and ubuntu-trusty-packager are fairly recent additions |
| 13:26 |
Dyrcona |
Erm.. Why are nodejs and nodejs-legacy the same version? |
| 13:27 |
berick |
they're the same package, effecively |
| 13:27 |
berick |
nodejs-legacy just puts files in a different place |
| 13:27 |
Dyrcona |
berick: Yeah, I've noticed the targets. |
| 13:27 |
berick |
that a lot of node packages depend on |
| 13:27 |
terran |
berick: mmorgan: I'm still getting no results - I also tried connecting to distribution_formulas in case I was trying to pull from the wrong source |
| 13:27 |
Dyrcona |
ok, I'll just run makefile.install again. |
| 13:29 |
Dyrcona |
I suppose the node stuff will move when the web staff client is mainstream, he said rhetorically. |
| 13:29 |
berick |
oh, and to clarify, the installer handles node and npm. installing the node packages and bower deps is still done by hand. |
| 13:30 |
berick |
starting with "== Building, Testing, Minification ==" from /Open-ILS/web/js/ui/default/staff/README.install |
| 13:30 |
|
rlefaive joined #evergreen |
| 13:31 |
Dyrcona |
Right. It looks like node, npm, and bower get installed. |
| 13:31 |
Dyrcona |
And, yeah, was gonna say looks like that is where to start. |
| 13:38 |
Dyrcona |
Well, here goes the script... |
| 13:38 |
bshum |
"When the moon hits your eye, like a big pizza pie, that's amore..." |
| 13:40 |
Dyrcona |
Wow! That installs a lot of stuff. |
| 13:41 |
Dyrcona |
Heh. "Running uglify:build" |
| 13:42 |
Stompro |
kmlussier, I think the create_release_notes.sh will need to be updated for the adoc change, it seems to only look for *txt files right now, but maybe I'm reading it wrong. |
| 13:44 |
bshum |
Probably, Stompro |
| 13:45 |
Dyrcona |
Heh. Spent so much time fretting over node.js that I forgot about database upgrade scripts.... |
| 13:45 |
Dyrcona |
Have to run those. |
| 13:46 |
berick |
terran: if you paste your environment entries and template i'll see if anything jumps out at me |
| 13:51 |
terran |
berick: Thank you, posted: https://docs.google.com/document/d/1WvgAcuvxfGgITzNUyHrCoafOhvNmxg39ZQzkCaUemf8/edit?usp=sharing |
| 13:57 |
|
remingtron joined #evergreen |
| 13:59 |
berick |
terran: one things, since you have entries.lineitem.lineitem_details.owning_lib in the env, you don't need entries.lineitem.lineitem_details. |
| 13:59 |
berick |
the first implies the second |
| 13:59 |
berick |
don't recall if that would actually cause problems, though |
| 14:00 |
terran |
berick: thanks, I wasn't sure based on the default entries |
| 14:00 |
terran |
it has things like provider and provider.address |
| 14:00 |
berick |
those are redundant as well |
| 14:00 |
berick |
but, it sounds like they aren't breaking anything |
| 14:00 |
terran |
no, they're working fine |
| 14:01 |
terran |
I'm not even sure if my assumption is correct that lineitem_details is where I need to be pulling the info from - it might be from distribution_formulas - I tried adding that to, but still no luck |
| 14:02 |
berick |
lineitem_details is what you want to show owning libs for each copy |
| 14:02 |
berick |
you probably also want the template to be [% lid.owning_lib %]<br/> |
| 14:02 |
berick |
arg |
| 14:02 |
berick |
didn't mean to Enter there |
| 14:02 |
berick |
[% lid.owning_lib.shortname %]<br/> |
| 14:03 |
berick |
or .name, depending on which you want to show |
| 14:04 |
terran |
so would I need to change the environment trigger entry to be entries.lineitem.lineitem_details.owning_lib.shortname? |
| 14:06 |
berick |
nope |
| 14:06 |
berick |
entries.lineitem.lineitem_details.owning_lib means "give me the owning_lib object" |
| 14:06 |
terran |
okay, that makes sense |
| 14:08 |
* bshum |
rolls the dice and sees if an inplace Win8.1 to Win10 upgrade kills his laptop. |
| 14:08 |
bshum |
And if it does die, perfect excuse to wipe it all and go back to Linux. :D |
| 14:10 |
terran |
berick: I removed the unnecessary entries I added to the trigger event environment and changed to lid.owning_lib.shortname - still nothing |
| 14:11 |
|
jlitrell joined #evergreen |
| 14:14 |
berick |
terran: oh, change it to "FOREACH lid IN" -- not "in" |
| 14:15 |
terran |
oops |
| 14:16 |
terran |
OH MY GOD IT WORKED |
| 14:16 |
terran |
berick++ |
| 14:16 |
* kmlussier |
whips up an agenda page for this afternoon's meeting. |
| 14:17 |
berick |
terran: yay |
| 14:17 |
terran |
berick: I owe you a beer at the next conf! I think I can everything else I need now |
| 14:17 |
berick |
kmlussier++ |
| 14:17 |
kmlussier |
Beer? |
| 14:17 |
berick |
terran: I accept beer very graciously |
| 14:17 |
dbs |
bshum: I had no problem with the two inplace upgrades I did over the weekend |
| 14:18 |
terran |
kmlussier: I'll buy you one too, just because I'm so happy and you're standing here |
| 14:18 |
bshum |
dbs: It'll be more interesting since this is a domain joined PC and we're jumping hoops to upgrade. |
| 14:18 |
kmlussier |
terran: I need to stand by you more often! :) |
| 14:18 |
kmlussier |
terran++ |
| 14:18 |
bshum |
dbs: But I appreciate your shared optimism. :) |
| 14:19 |
terran |
kmlussier: you wouldn't have wanted to stand by me earlier when I was banging my head on my desk |
| 14:23 |
kmlussier |
http://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2015-08-05 |
| 14:23 |
bshum |
kmlussier++ |
| 14:35 |
mmorgan |
terran++ # action trigger success |
| 14:38 |
terran |
mmorgan: thanks for the moral support! |
| 14:39 |
Dyrcona |
kmlussier: Evergreen should be running on my dev vm with the web staff client and the latest branches you requested. |
| 14:39 |
kmlussier |
Dyrcona++ Thank you! |
| 14:39 |
Dyrcona |
I haven't had a chance to test it, yet, myself. |
| 14:42 |
bshum |
Well the upgrade worked. But non of the network adapters are functioning. Still it didn't completely blow up at least. |
| 14:43 |
* bshum |
continues his adventures |
| 14:56 |
|
jwoodard joined #evergreen |
| 15:01 |
* berick |
puts out call for dev meeting maestro |
| 15:05 |
ldw |
berick: I have not done it before, but I have the docs open if people willing to wait for me while I look up commands, I will act as maestro. |
| 15:05 |
berick |
ldw++ |
| 15:06 |
ldw |
should I start now? |
| 15:06 |
berick |
i think we're all happy to be patient while people learn |
| 15:06 |
berick |
ldw: yep |
| 15:06 |
berick |
people will file in |
| 15:06 |
ldw |
#startmeeting |
| 15:06 |
pinesol_green |
ldw: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee' |
| 15:06 |
ldw |
should it be Evergreen Dev Meeting? |
| 15:06 |
ldw |
with a date? |
| 15:07 |
ldw |
#startmeeting Evergreen Dev Meeting 2015-08-05 |
| 15:07 |
pinesol_green |
Meeting started Wed Aug 5 15:07:09 2015 US/Eastern. The chair is ldw. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:07 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 15:07 |
pinesol_green |
The meeting name has been set to 'evergreen_dev_meeting_2015_08_05' |
| 15:07 |
kmlussier |
ldw++ |
| 15:07 |
yboston |
ldw++ |
| 15:08 |
ldw |
Do we need to review last meetings minutes? |
| 15:08 |
kmlussier |
We usually start with introductions. |
| 15:08 |
berick |
#info http://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2015-08-05 |
| 15:08 |
kmlussier |
Sorry, I forgot to add it to the agenda. |
| 15:08 |
ldw |
#info ldw=Liam Whalen BC Libraries Cooperative |
| 15:09 |
RoganH |
#info RoganH = Rogan Hamby, SCLENDS |
| 15:09 |
berick |
#info berick King County Library System |
| 15:09 |
phasefx |
#info phasefx = Jason Etheridge, ESI |
| 15:09 |
yboston |
ldw: for the future you can type soemthng like "#topic introductions" |
| 15:09 |
yboston |
#info yboston = Yamil Suarez: Berklee College of Music |
| 15:09 |
ldw |
yboston: thanks |
| 15:09 |
Dyrcona |
#info Dyrcona = Jason Stephenson, Merrimack Valley Library Consortium |
| 15:09 |
dbwells |
#info dbwells = Dan Wells, Hekman Library (Calvin College) |
| 15:10 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 15:10 |
miker |
#info miker = Mike Rylander, ESI |
| 15:10 |
gmcharlt |
#info gmcharlt = Galen Charlton, ESI |
| 15:10 |
jlitrell |
#info jlitrell = Jake Litrell, MassLNC |
| 15:10 |
yboston |
ldw: you can soon use this… "#topic Action Items from Last Meeting" |
| 15:10 |
ldw |
#topic Action Items from Last Meeting |
| 15:11 |
terran |
#info terran = Terran McCanna, PINES |
| 15:11 |
yboston |
ldw: no you should quote the action tiem with a "#info prefix" |
| 15:11 |
yboston |
like "#info gmcharlt and eeevil to organize a webstaff client hacking day in July" |
| 15:12 |
gmcharlt |
cue up TARDIS |
| 15:12 |
ldw |
#info gmcharlt and eeevil to organize a webstaff client hacking day in July |
| 15:12 |
gmcharlt |
so speaking of the action item... we still plan to do it |
| 15:12 |
gmcharlt |
but I think realisitically it's going to be in September at this point |
| 15:14 |
ldw |
gmcharlt: are you still willing to lead on that? |
| 15:14 |
gmcharlt |
yes |
| 15:14 |
ldw |
#action gmcharlt to organize webstaff client hacking day in September |
| 15:14 |
yboston |
ldw++ |
| 15:14 |
ldw |
#info jeff will look into removing old self check interface. |
| 15:15 |
|
rlefaive joined #evergreen |
| 15:16 |
ldw |
#action ldw will follow up with jeff about removing old self check interface status |
| 15:16 |
ldw |
#info jeff will look at removing old JSPAC code. |
| 15:17 |
ldw |
#action ldw will follow up with jeff about removing old JSPAC code status |
| 15:17 |
ldw |
#info dbwells will hopefully write more neg balances tests and push whatever he has ready on July 10 |
| 15:18 |
dbwells |
they done got wrote, mostly by remingtron |
| 15:18 |
Dyrcona |
That one is done. |
| 15:18 |
ldw |
#info dbwells done got wrote'em |
| 15:19 |
Dyrcona |
#info remingtron, too. |
| 15:19 |
berick |
heh |
| 15:19 |
dbwells |
though, apparently nobody actually tried to /run/ them, since the tests immediately failed after getting pushed in (due to a missing setup file) |
| 15:19 |
gmcharlt |
dbwells: something that had existed in your setup but missed being committed? |
| 15:19 |
dbwells |
gmcharlt: yes |
| 15:20 |
gmcharlt |
thought so |
| 15:20 |
Dyrcona |
Well, that's partly 'cause I didn't get to my part. |
| 15:20 |
ldw |
Is there anything else that needs doing on this item? |
| 15:21 |
kmlussier |
I don't think so |
| 15:21 |
ldw |
#info kmlussier to complete her testing on the negative balance branch by July 8 |
| 15:21 |
kmlussier |
#info kmlussier's negative balance testing is complete. Remaining issues have been reported in bug 1479107 and bug 1479110 |
| 15:21 |
pinesol_green |
Launchpad bug 1479107 in Evergreen "Replace manual void option with an "adjust to zero" option" (affected: 1, heat: 6) [Medium,New] https://launchpad.net/bugs/1479107 |
| 15:21 |
pinesol_green |
Launchpad bug 1479110 in Evergreen "Negative balance settings used in combination with one another should interact differently" (affected: 1, heat: 6) [Medium,New] https://launchpad.net/bugs/1479110 |
| 15:22 |
ldw |
#info Dyrcona will follow up with negative balance branch after July 10. |
| 15:22 |
Dyrcona |
Well, that's basically done, but bshum did it. |
| 15:22 |
Dyrcona |
#info done did by bshum |
| 15:22 |
ldw |
#info jeff will articulate ideas on merge vs cherry-pick and start discussion/proposal on dev list |
| 15:23 |
ldw |
did this discussion start? |
| 15:23 |
Dyrcona |
No, it hasn't. |
| 15:24 |
ldw |
#action ldw will follow up with jeff on merge vs cherry-pick discussion |
| 15:24 |
dbwells |
Perhaps on test writing day we can get some more eyeballs on the neg. balance tests. They do the job, but some parts are a little funky, and may need some more thoughts about best practices. |
| 15:24 |
ldw |
#action ldw will looking into integrating neg. balance tests on test writing day |
| 15:24 |
ldw |
#info : |
| 15:25 |
ldw |
#info : |
| 15:25 |
ldw |
#info yboston to followup with ldw about a testing day. |
| 15:25 |
ldw |
done |
| 15:25 |
ldw |
#info bshum to work with berick and others on crafting more information about release maintaining and schedules |
| 15:26 |
berick |
no such crafting has occurred that I know of |
| 15:26 |
ldw |
berick: are you still able to work on this with bshum? |
| 15:26 |
berick |
ldw: yes |
| 15:27 |
ldw |
#action berick will work with bshum on crafting more information about release maintaining and schedules |
| 15:27 |
ldw |
now on to OpenSRF relase info? |
| 15:28 |
berick |
ldw: i added a few things to the agenda doc since starting. may want to refresh |
| 15:28 |
gmcharlt |
there are some pending bugs and enhancements |
| 15:28 |
ldw |
#info OpenSRF release info |
| 15:28 |
gmcharlt |
and I expect to cut a release some time in the next 6 weeks |
| 15:29 |
gmcharlt |
#Info Galen is expecting to cut another OpenSRF release in the next 6 weeks |
| 15:29 |
ldw |
gmcharlt: should I action that? |
| 15:29 |
gmcharlt |
ah, yes please |
| 15:29 |
Dyrcona |
ldw you should probably change the #topic, too. |
| 15:30 |
ldw |
#topic OpenSRF relase info |
| 15:30 |
Dyrcona |
ldw++ # for hanging in there. :) |
| 15:30 |
ldw |
thanks Dyrcona I was mistakenly using #info when I should be using #topic |
| 15:30 |
ldw |
#action gmcharlt will cut an OpenSRF release in the next 6 weeks |
| 15:31 |
ldw |
#topic Evergreen 2.8.3 planned for Aug. 19. |
| 15:31 |
berick |
not much to discuss there. just wanted to note it. |
| 15:31 |
ldw |
#topic QA Proposal |
| 15:32 |
berick |
the cal. also says that's our 2.9 beta release date.. |
| 15:32 |
berick |
oops, wrong topic |
| 15:32 |
kmlussier |
Do we need to go back to the Evergreen update topic for a 2.9 update? |
| 15:32 |
ldw |
#info go back to Evergreen 2.9 update, will resume QA Proposal after |
| 15:32 |
ldw |
#topic Evergreen 2.9 update |
| 15:32 |
kmlussier |
ldw++ |
| 15:33 |
Dyrcona |
#info The 2.9 alpha was postponed indefinitely because of questions about the negative balance branch and its release notes. |
| 15:34 |
berick |
Dyrcona: you're still planning an alpha? |
| 15:34 |
berick |
or just going to beta? |
| 15:34 |
Dyrcona |
Well, that's the question that depends on the pending bugs, I guess. |
| 15:35 |
Dyrcona |
The bug concerning settings has basically been resolved through discussion where the consensus seems to be to leave them as they are. |
| 15:36 |
Dyrcona |
The other bug concerns changes to the staff client and dbwells is taking that on. |
| 15:36 |
kmlussier |
Dyrcona: Is that the consensus? I was thinking it was, but I wasn't sure after miker posted his comments. |
| 15:36 |
miker |
I'm fine with general concensus |
| 15:37 |
kmlussier |
miker: OK, thanks! |
| 15:37 |
kmlussier |
I can update the description for those settings to add a little clarity and then update the release notes entry to reflect the consensus. |
| 15:37 |
* Dyrcona |
was just looking at the comments again. |
| 15:37 |
dbs |
#info dbs = Dan Scott, Laurentian University |
| 15:38 |
ldw |
#action kmlussier to update setting descriptions and then update the release notes to reflect consensus |
| 15:38 |
Dyrcona |
Well, I could do an alpha at any time, but I'd prefer that the negative balances feature and notes be more or less complete. |
| 15:39 |
kmlussier |
Do we have an idea on the timeframe that https://launchpad.net/bugs/1479107 can be done? |
| 15:39 |
pinesol_green |
Launchpad bug 1479107 in Evergreen "Replace manual void option with an "adjust to zero" option" (affected: 1, heat: 6) [Medium,New] |
| 15:40 |
dbwells |
I think any work I can do for the interface pieces won't be complete until close the beta cutoff. |
| 15:41 |
Dyrcona |
I could give it a shot, but I have a tendency to miss things in the staff client. |
| 15:41 |
berick |
kmlussier: that looks a lot like bug 1249398 |
| 15:41 |
pinesol_green |
Launchpad bug 1249398 in Evergreen "Clear negative balance billing option" (affected: 3, heat: 18) [Wishlist,Confirmed] https://launchpad.net/bugs/1249398 |
| 15:42 |
kmlussier |
berick: We were talking about that the other day. |
| 15:42 |
berick |
my code is probably out of date, though |
| 15:42 |
berick |
almost 2 years old |
| 15:42 |
kmlussier |
They both have different objectives. One clears the negative balance off the record. The other adjusts a bill so that the balance is zero. |
| 15:42 |
berick |
ah, ok |
| 15:42 |
berick |
nevermind, then |
| 15:43 |
dbwells |
I would prefer to see the alpha released as-is, rather than rush/delay things. Unless we feel like there is nothing else worth testing in the alpha. |
| 15:43 |
berick |
raise your hand if you will install the alpha |
| 15:43 |
kmlussier |
Well, I install master on a regular basis, but I don't need an alpha release to do so. :) |
| 15:43 |
Dyrcona |
I already have, basically. :) |
| 15:44 |
dbwells |
In my experience, the alpha was little more than a dry-run for the benefit of the RM more than anyone else :) |
| 15:44 |
berick |
s/the alpha/the alpha tarball/ |
| 15:44 |
ldw |
Dyrcona: do you want an action item regarding an alpha? |
| 15:45 |
berick |
dbwells: true, it can be useful for the RM |
| 15:45 |
Dyrcona |
Do I /want/ one? No, I don't /want/ one. :) |
| 15:46 |
* berick |
chuckles |
| 15:46 |
ldw |
#info Dyrcona protests an alpha action item ;P |
| 15:46 |
miker |
Dyrcona: thougths on pulling in the sprint2 branch at or around alpha time? |
| 15:47 |
Dyrcona |
miker: Well is sprint2 ready for testing or still work in progress? |
| 15:47 |
miker |
today, WIP, but we're closing it on it |
| 15:47 |
|
jwoodard joined #evergreen |
| 15:47 |
miker |
and, tbh, I think any working code should go in regardless of sprint boundary ... but, that's just my opinion |
| 15:48 |
kmlussier |
Are there pieces of it that could affect functionality in the existing client? |
| 15:49 |
miker |
kmlussier: not yet. we've avoided touching anything that could affect the SC, after the chunking debacle ;) |
| 15:49 |
kmlussier |
IIRC, for sprint 1, there were certain interfaces berick identified as needing extra attention because they might be impacted by the web client work. |
| 15:49 |
berick |
yeah, there were some tpac changes |
| 15:49 |
berick |
that needed confirmation of non-breakage |
| 15:50 |
miker |
there's no crossover in the post-2.8 stuff, afaict. but, I'd be happy if someone put eyeballs on that. a scan of changes to existing files should tell the tale |
| 15:50 |
gmcharlt |
the sprint2 stuff is self-contained with the exception of some things that would (in a minor way) affect the existing *webstaff* circ interface |
| 15:50 |
gmcharlt |
mostly grid improvements |
| 15:50 |
Dyrcona |
Well, I'll take a look at where sprint2 is today and get back to you. |
| 15:50 |
berick |
in general, though, i think we're still in agreement the browser client code has a lower barrier to entry (assuming no external breakage). |
| 15:50 |
berick |
correct me if i'm wrong |
| 15:51 |
* berick |
would like to see it merged in a lot more frequently |
| 15:51 |
ldw |
#action Dyrcona to investigate sprint2's integration with an alpha release |
| 15:52 |
* dbwells |
seconds more frequent merges |
| 15:52 |
bshum |
I've been testing sprint2 merges during my last two system builds with recent master. |
| 15:52 |
bshum |
It's not too crazy looking to me anyways. |
| 15:52 |
* bshum |
would say more but typing on a phone isn't so easy. |
| 15:53 |
* bshum |
will chat further with Dyrcona on that lookover. |
| 15:53 |
|
ericar_ joined #evergreen |
| 15:55 |
ldw |
Dyrcona: will you set a date for a release/skip an alpha release once you have examined the possibility of a sprint2 merge? |
| 15:55 |
Dyrcona |
Yes. |
| 15:56 |
ldw |
#action Dyrcona to determine if sprint2 can be merged into an alpha release, and will set a date for a release or skip the release depending on his findings. |
| 15:56 |
ldw |
any other 2.9 discussion? |
| 15:57 |
kmlussier |
No, but Dyrcona++ |
| 15:57 |
ldw |
Dyrcona++ |
| 15:57 |
dbwells |
Dyrcona++ |
| 15:57 |
ldw |
#topic QA Proposal - http://georgialibraries.markmail.org/thread/dl7xemr5zzzcfi6f |
| 15:57 |
Bmagic |
#info Bmagic = Blake GH, MOBIUS |
| 15:57 |
kmlussier |
I added that topic to the agenda because the status of the QA proposal seems to still be in limbo. |
| 15:58 |
kmlussier |
I added the proposed guidelines to the contributing page after gmcharlt gave it the okay in that thread, but there were concerns raised shortly thereafter. |
| 15:58 |
ldw |
My concerns are not necessary. Your comment about a developer being able to state why a test is infeasible invalidates my concerns. |
| 15:59 |
dbwells |
I only have a couple minutes before I need to run, but would like more feedback on my proposal for multiple sign-offs in lieu of the "it's too hard to write tests" clause. |
| 15:59 |
ldw |
dbwells: I like that idea. |
| 15:59 |
dbwells |
I think it might keep things a little more objective and self-correcting. |
| 16:00 |
gmcharlt |
well, I think I would like to push back a bit on the notion of sign-offs as being "objective", per se |
| 16:00 |
ldw |
Would it be necessary for us to add a negative sign-off? Incase a committer feels strongly about a test being needed? |
| 16:01 |
gmcharlt |
which is not to dismiss the proposal of trading additional review in place of a statement that automated tests can't be written for a given patch |
| 16:01 |
Dyrcona |
ldw: That's typically done in a comment on the LP bug. |
| 16:02 |
dbwells |
Certainly not all signoffs are created equal, but more-is-better should generally hold true across the aggregate. |
| 16:02 |
gmcharlt |
also, in my view a statement to the effect that a test is not infeasiable is not meant to be a flat assertion |
| 16:02 |
gmcharlt |
rather, a reasoned argument |
| 16:03 |
gmcharlt |
that said, I'm not wedded that wording |
| 16:04 |
gmcharlt |
but I am in disfavor of frequent use of infeasibility statements OR multiple signoffs purely as a mechanism for folks to avoid writing unit tests |
| 16:04 |
gmcharlt |
or to put it another way |
| 16:04 |
gmcharlt |
- more tests: generally good |
| 16:04 |
gmcharlt |
- seeking out additional reviewers: almost always good |
| 16:04 |
gmcharlt |
- not writing tests for new code or significant bugfixes - AVOID! AVOID! |
| 16:05 |
* kmlussier |
is in agreement with gmcharlt |
| 16:06 |
ldw |
do we need to have a +1 type vote on this issue? |
| 16:07 |
gmcharlt |
ldw: dbwells: give me one moment to propose a wording change |
| 16:08 |
pastebot |
"gmcharlt" at 64.57.241.14 pasted "revised QA guideline" (5 lines) at http://paste.evergreen-ils.org/22 |
| 16:09 |
dbwells |
gmcharlt++ # looks good to me |
| 16:10 |
kmlussier |
+1 |
| 16:10 |
ldw |
#info revised QA guideline |
| 16:10 |
ldw |
+1 |
| 16:10 |
terran |
+1 |
| 16:11 |
RoganH |
+1 |
| 16:11 |
phasefx |
+1 |
| 16:11 |
jlitrell |
+1 |
| 16:11 |
berick |
+1 |
| 16:11 |
dbwells |
My main concern was that leaving the judgment call to one person was going to eventually blow up and cause hard feelings, so this solves it, thanks! |
| 16:12 |
Dyrcona |
Y'know, we can do an actual vote. |
| 16:12 |
* ldw |
looks into voting |
| 16:13 |
ldw |
#startvote Should we accept gmcharlt revised QA guideline |
| 16:13 |
pinesol_green |
Unable to parse vote topic and options. |
| 16:13 |
gmcharlt |
FWIW, when I see resentment arise in other projects regarding this sort of thing... long-term resentment typically has more to do about unwillingness to help cleanup after mistakes, not for making mistakes int the first place |
| 16:13 |
ldw |
#startvote Should we accept gmcharlt revised QA guideline? Yes/No |
| 16:13 |
pinesol_green |
Begin voting on: Should we accept gmcharlt revised QA guideline? Valid vote options are Yes, No. |
| 16:13 |
pinesol_green |
Vote using '#vote OPTION'. Only your last vote counts. |
| 16:13 |
gmcharlt |
#vote Yes |
| 16:13 |
ldw |
#vote Yes |
| 16:13 |
terran |
#vote Yes |
| 16:13 |
Dyrcona |
#vote yes |
| 16:13 |
berick |
#vote yes |
| 16:13 |
kmlussier |
#vote yes |
| 16:13 |
jlitrell |
#vote yes |
| 16:14 |
phasefx |
#vote Yes |
| 16:14 |
dbwells |
#vote Yes |
| 16:14 |
dbs |
#yes |
| 16:15 |
ldw |
last call for voting |
| 16:15 |
dbs |
a proposed friendly amendment would be s/explaining that/explaining why/ but that's minor |
| 16:15 |
Dyrcona |
dbs might want to vote again. |
| 16:15 |
dbs |
#vote yes |
| 16:15 |
gmcharlt |
dbs: yeah, +1, and I think that falls in the realm of a non-controversial erratum |
| 16:17 |
ldw |
#endvote |
| 16:17 |
pinesol_green |
Voted on "Should we accept gmcharlt revised QA guideline?" Results are |
| 16:17 |
pinesol_green |
Yes (10): kmlussier, jlitrell, phasefx, berick, dbwells, Dyrcona, ldw, terran, gmcharlt, dbs |
| 16:17 |
ldw |
#topic Code sanity check appreciated for https://bugs.launchpad.net/evergreen/+bug/1468422 |
| 16:17 |
pinesol_green |
Launchpad bug 1468422 in Evergreen "Improve Password Management and Authentication" (affected: 1, heat: 258) [Undecided,New] |
| 16:18 |
berick |
oh, that's me |
| 16:19 |
berick |
so, want to keep some momentum, but also want to avoid doing more work until i get some nod that it's heading in the right direction |
| 16:19 |
berick |
so if anyone can eye/test/etc. i'd appreciate it |
| 16:19 |
berick |
that is all |
| 16:19 |
dbwells |
berick++ # glad to see this moving forward |
| 16:20 |
kmlussier |
berick++ |
| 16:21 |
dbwells |
berick: my C chops are basically non-existant, so my eyeballs won't help, but I'll plan to do some basic explosion testing. |
| 16:21 |
berick |
dbwells: well, the DB changes are my main concern |
| 16:21 |
dbwells |
ldw: action me up, good sir! |
| 16:22 |
dbwells |
berick: ah, ok |
| 16:22 |
ldw |
#action dbwells will attempt to explode berick's Password Managment and Authentication improvements |
| 16:22 |
berick |
the C/API stuff is less exotic :) |
| 16:23 |
gmcharlt |
berick: I would be very suspicious of exotic crypto code, even from you! ;) |
| 16:23 |
ldw |
Is there any new business? |
| 16:23 |
berick |
gmcharlt: what's a few rootkits between friends? |
| 16:25 |
gmcharlt |
@quote add <berick> gmcharlt: what's a few rootkits between friends? |
| 16:25 |
pinesol_green |
gmcharlt: The operation succeeded. Quote #123 added. |
| 16:26 |
ldw |
#endmetting |
| 16:26 |
ldw |
#edmeeting |
| 16:26 |
ldw |
#endmeeting |
| 16:26 |
pinesol_green |
Meeting ended Wed Aug 5 16:26:16 2015 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:26 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-08-05-15.07.html |
| 16:26 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-08-05-15.07.txt |
| 16:26 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-08-05-15.07.log.html |
| 16:26 |
berick |
ldw++ |
| 16:26 |
gmcharlt |
ldw++ |
| 16:26 |
ldw |
a little rough landing there |
| 16:26 |
gmcharlt |
ldw: only requirement is that we all walk away ;) |
| 16:26 |
dbwells |
ldw++ |
| 16:27 |
kmlussier |
ldw++ |
| 16:27 |
ldw |
do I need to update the minutes with the information from the meeting? |
| 16:28 |
gmcharlt |
ldw: yeah, that's typically done both in the page, and in the index page of dev meetings |
| 16:28 |
gmcharlt |
lots of examles to crib from |
| 16:28 |
ldw |
gmcharlt: ok, I will look around. |
| 16:29 |
terran |
ldw++ |
| 16:29 |
remingtron |
ldw++ |
| 16:31 |
|
akilsdonk joined #evergreen |
| 16:33 |
terran |
berick: thanks again for your help! Check out my results: Old / default invoice template: https://drive.google.com/file/d/0Bzwi0wcBFvR0ZFBwTTZiS18yd2c/view?usp=sharing |
| 16:33 |
terran |
versus shiny NEW invoice template: https://drive.google.com/file/d/0Bzwi0wcBFvR0Y29mNlQzR1FzbU0/view?usp=sharing |
| 16:34 |
berick |
terran++ nice |
| 16:35 |
terran |
Now on to the Purchase Order template... should be easier now that I understand more |
| 17:08 |
|
bmills joined #evergreen |
| 17:11 |
|
mmorgan left #evergreen |
| 17:15 |
dbs |
terran++ snazzy! |
| 17:32 |
jwoodard |
@weather 76227 |
| 17:32 |
pinesol_green |
jwoodard: The current temperature in Nipe Ranch, Krugerville, Texas is 101.1°F (4:27 PM CDT on August 05, 2015). Conditions: Scattered Clouds. Humidity: 41%. Dew Point: 73.4°F. Pressure: 29.85 in 1011 hPa (Falling). Heat advisory in effect until 7 PM CDT Saturday... |
| 17:45 |
|
ericar_ joined #evergreen |
| 18:00 |
jihpringle |
terran: that's beautiful, is that done in the invoice action trigger template? |
| 18:12 |
|
buzzy joined #evergreen |
| 19:40 |
|
jlitrell joined #evergreen |
| 19:54 |
|
akilsdonk joined #evergreen |
| 19:54 |
kmlussier |
terran++ indeed |
| 21:02 |
|
bmills left #evergreen |
| 21:04 |
|
dbwells joined #evergreen |
| 21:09 |
|
dbwells joined #evergreen |
| 22:04 |
|
rlefaive joined #evergreen |
