Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Tuesday, October 19th, 2010

< Monday, October 18th, 2010Raw Log FileWednesday, October 20th, 2010 >
#TimeNickMessage
#00:23:36shadowspar has quit IRC
#00:34:42shadowspar has joined #evergreen
#03:05:31brendan2 has joined #evergreen
#03:36:24finnapz has quit IRC
#03:50:13finnapz has joined #evergreen
#03:52:34Dre__ has joined #evergreen
#03:54:23Dre__hello
#03:54:36Dre__is evergreen run in ubuntu
#03:54:40Dre__or debian
#03:54:50Dre__any one here
#03:54:58Dre__how r you
#03:55:13Dre__are you really chating
#03:55:17Dre__i m waiting your response
#03:55:25Dre__make some noise yo
#04:52:05Dre__ has quit IRC
#05:06:16artunit has quit IRC
#05:21:31artunit has joined #evergreen
#05:49:55jeffdavis has quit IRC
#05:49:55leed has quit IRC
#05:49:55Dmagick has quit IRC
#05:50:46Dmagick has joined #evergreen
#05:50:47jeffdavis has joined #evergreen
#05:52:01leed has joined #evergreen
#07:50:49kmlussier has joined #evergreen
#08:16:33phasebb has quit IRC
#08:40:10collum has joined #evergreen
#08:41:02bshum has joined #evergreen
#08:56:47r123 has joined #evergreen
#08:57:28Aaron has joined #evergreen
#09:01:37Dyrcona has joined #evergreen
#09:06:52Meliss has joined #evergreen
#09:19:30leed has quit IRC
#09:19:34leed has joined #evergreen
#09:21:03eguest309 has joined #evergreen
#09:21:37eguest309 has left #evergreen
#09:26:09afterl has joined #evergreen
#09:30:26AaronZ has joined #evergreen
#09:31:05Aaron has quit IRC
#09:44:15jenny has joined #evergreen
#10:02:17kcollier has joined #evergreen
#10:47:18kcollier has quit IRC
#10:48:32kcollier has joined #evergreen
#10:50:53dbs has joined #evergreen
#10:58:56r1231 has joined #evergreen
#11:00:21r1231 has quit IRC
#11:17:03abeNd-org has quit IRC
#11:21:33gdunbar has quit IRC
#11:22:26gdunbar has joined #evergreen
#11:40:35yboston has joined #evergreen
#11:44:20granitize has joined #evergreen
#11:57:06jamesrf has joined #evergreen
#11:58:43dbs has quit IRC
#12:14:30av has joined #evergreen
#12:21:29jamesrf has quit IRC
#12:48:45dbs has joined #evergreen
#12:48:45dbs has joined #evergreen
#12:52:48jamesrf has joined #evergreen
#13:12:14jcpl-jasonb has joined #evergreen
#13:12:26parsr has joined #evergreen
#13:22:48parsrQuiet day today -- Three cheers for Evergreen! Long Live the developer geeks! Great work all you contributors! Kudos to library managers who finally gave us some support to do the right thing! (Anything else?)
#13:23:29tsberedown with my vm environment for not giving me networking!
#13:26:05bshumHip, hip, huzzah!
#13:28:54dbsparsr: http://evergreen-ils.org/dokuwiki/doku.php?do=recent gives some ideas of recent activity
#13:45:21parsrdbs: irc seemed unusually quiet today - but agreed 'activity meter' remains high as usual.
#13:51:36rsoulliere has joined #evergreen
#13:56:18eeevilT-4min
#13:57:11av_ocls has joined #evergreen
#13:57:16b_bonner has joined #evergreen
#13:59:52JimTheWebsiteGuy has joined #evergreen
#14:00:07Michele_ has joined #evergreen
#14:00:19gmcharltT-0
#14:00:22katesheehan has joined #evergreen
#14:00:22gmcharltgood afternoon all
#14:00:23ocls-damon has joined #evergreen
#14:00:30dbsHail and welcome, travellers
#14:00:33Dyrconahi
#14:00:38berickhi
#14:00:38ocls-damon:)
#14:00:40gmcharltmeeting starting now, the agenda is at http://www.open-ils.org/dokuwiki/doku.php?id=dev:meetings:2010-10
#14:00:47b_bonnergood afternoon
#14:00:54LBA has joined #evergreen
#14:00:57rayner has joined #evergreen
#14:00:57slipscomb has joined #evergreen
#14:01:00gmcharltfirst item is introductions - let's state our names and affiliations for the record
#14:01:04IN_wendy has joined #evergreen
#14:01:06gmcharlt = Galen Charlton, Equinox
#14:01:16eeevil is Mike Rylander, Equinox
#14:01:16Meliss= Melissa Lefebvre, Bibliomation
#14:01:19bshum = Ben Shum, Bibliomation
#14:01:19afterl = Amy Terlaga, Bibliomation
#14:01:25Dyrcona = Jason Stephenson Merrimack Valley Library Consortium
#14:01:25phasefx = Jason Etheridge, Equinox, and I approve this message
#14:01:27b_bonnerb_bonner = Bradley Bonner, KCLS
#14:01:32StephenGWills has joined #evergreen
#14:01:35jenny= Jenny Turner, PALS
#14:01:36sylvar = Ben Ostrowsky, Equinox
#14:01:42senator = Lebbeous Fogle-Weekley, Equinox
#14:01:58LBALori Ayre - Galecia Group/RSCEL/KCLS
#14:01:59slipscombSuzannah Lipscomb, Equinox
#14:02:06jamesrf = James Fournie, SITKA
#14:02:07ocls-damondamon wood, orange county library system
#14:02:18berickBill Erickson, Equinox
#14:02:18av_oclsamy vanschaik, orange county library system
#14:02:24StephenGWillsStev3 Wills, LYRASIS
#14:02:32jeff = Jeff Godin, TADL
#14:02:34_bott_ Bill Ott, Grand Rapids Public
#14:02:49dbs = Dan Scott, Laurentian University / Conifer
#14:02:53kmlussierKathy Lussier, Massachusetts Library Network Cooperative
#14:03:04katesheehankate sheehan, Bibliomation
#14:03:22kcollierKaren Collier, Kent County Public Library
#14:03:24finnapzsteve sheppard, DIG
#14:03:44jeffdavis = Jeff Davis, SITKA
#14:03:47r123 = Robin Isard Algoma University / Conifer
#14:04:01shadowspar := Rick Scott, Wishart Library @ Algoma university / Conifer
#14:04:04kbeswick_ = Kevin Beswick, Laurentian University / Conifer
#14:04:36rsoulliereRobert Soulliere, Mohawk College
#14:04:37eeevilI move that quorum has been reached ;)
#14:04:44Dyrcona:)
#14:04:45gmcharltok - if you pop in, feel free to introduce yourself, but let's move to the next agenda item,
#14:04:46gmcharltReview Action Items from previous meeting
#14:05:07gmcharltfirst one - dbs to review the versioning wiki page
#14:05:13gmcharltdbs: 30 seconds to say anythinng about it
#14:05:48dbsPlease review my draft!
#14:05:55dbshttp://evergreen-ils.org/dokuwiki/doku.php?id=versioning
#14:06:04dbs(comments on mailing list or later on IRC, please)
#14:06:09gmcharltding-ding-ding (thanks, dbs)
#14:06:12gmcharltnext up - Release notes and future expected features
#14:06:52gmcharltI know that slipscomb and gdunbar and others have been writing up 2.0 release note information for the features we've been wokring on
#14:07:43afterlI think that KCLS was also working on some documents
#14:07:49slipscombdraft versions of the release notes are in the works and close to completion
#14:08:12gmcharltslipscomb: thanks
#14:08:35gmcharltwe hope to get them up to the wiki soon - hopefully so that, if nothing else, this isn't an action item for the December meeting
#14:08:45gmcharltnext item - 2.0 alpha testing
#14:08:51bshumA bunch of us have installed 2.0 alpha4 to local installations on a variety of OS platforms, mostly Ubuntu Lucid or Debian Squeeze.
#14:09:04gmcharltfirst, a big thanks to all who have been testing 2.0 in test installations (or production!)
#14:09:10tsbere pops in, Thomas Berezansky / Merrimack Valley Library Consortium
#14:09:11eeevilindeed ... there's been good success and good feedback
#14:09:35eeeviloverall, this is by far the best pre-release period we've seen, so thanks much folks!
#14:09:36bshumSpecial cheers to rsoulliere for posting his findings on the upgrade from 1.6.1 to 2.0; we'll be poking at that soon ourselves.
#14:09:49gmcharltso general word - please test, please file bugs, please send patches, please write up what you find
#14:09:58gmcharltnext item - List projects in progress in a central location: Code repositories - drafted
#14:10:06gmcharltaka - http://www.open-ils.org/dokuwiki/doku.php?id=dev:code_repositories
#14:10:30gmcharltgeneral call - if you have a branch of Evergreen or related software, please add yourself to that wiki page
#14:10:45gmcharltnext item - Follow up with DIG on integration between wiki pages and Book of Evergreen
#14:11:07gmcharltrsoulliere: kcollier: thoughts/update on that?
#14:11:29kcollierNotes have been made on Wiki pages where content was taken with links to the files in the github repository and links to the html document (some links will need updating). Moreover, links have been added to the documentation outline http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:outline indicating the corresponding wiki content for various sections.
#14:11:50gmcharltkcollier++
#14:11:51gmcharltdig++
#14:12:09gmcharltnext item - Web Committee member to email DIG list requesting contact info
#14:12:35kcollierIt was determined that using the DIG list is a good place for communication from the web committee for questions, suggestions, etc... Other communication means will be used as needed.
#14:12:36gmcharltafterl: LBA: update?
#14:12:45gmcharltok, cool
#14:12:55LBAposting update...
#14:13:02lisppasteLBA pasted "EG Communication Committee Update" at http://paste.lisp.org/display/115713
#14:13:08gmcharltlast item from previous meeting - Report Taskforce to follow-up with Jeff & Ben on automation of reports
#14:13:17afterlbshum has an update
#14:13:43bradl Brad LaJeunesse, Equinox #poking head in, but heading to another meeting, just wanted to give a big YEE-HAW to the group :)
#14:13:43gmcharltbshum: please go ahead
#14:13:48afterlbshum?
#14:13:55bshumThis was a short summary I put together: http://paste.lisp.org/+2HA7
#14:14:10bshumDescribing our current work for automating SQL reports
#14:14:20gmcharltok, thanks
#14:14:29gmcharlton to the next item
#14:14:41gmcharltCirc scripts – deprecate in 2.0 (not untenable)? kill them altogether (booooo!)? something else? – vs tsbere's due-date ceiling alternate implementation patch: where should it go?
#14:14:49eeevil grabs the mic
#14:14:51gmcharltlet's have five minutes for discussion
#14:15:12eeevilso ... there's a really compelling patch from tsbere to change the implementation of yet-unreleased hard-due-date code
#14:15:36eeeviland, during the discussion of that, I raised the question of deprecating circ scripts
#14:16:02eeevilso ... the question to the community is: do we deprecate circ scripts (but not remove or cripple them) in 2.0?
#14:16:13jamesrfcan you clarify what you mean by deprecate if they are not removed or crippled?
#14:16:18eeevil(discuss)
#14:16:18phasefx has a fondness for the circ scripts, but mainly because they're turing complete and he hasn't learned in-db circ yet :-)
#14:16:36Dyrconadeprecation means their use is discouraged and they could be removed at a future time.
#14:16:43eeeviljamesrf: say "in some future version, scripts will be either removed or not have access to all features
#14:17:05eeevilno, when any of those happens is a question for the future
#14:17:18eeevilon the table ATM is just, do we start down that road
#14:17:40eeevil1) it will focus attention on improving in-db for those cases where phase-of-the-moon, etc, are important
#14:17:44tsbereI was originally under the impression that road was started on due to the config option including the word "legacy"
#14:17:54eeevil2) it will give folks time to start moving to in-db
#14:17:59afterlI am in favor of deprecating. However, we use in-db.
#14:18:01eeevil(and impetus)
#14:18:09jeffdavisI know sitka has some circ policies that can't be handled via in-db circ in its current form; I'd prefer not to see them deprecated just yet
#14:18:10dbs supports deprecating scripts, simply to avoid having to perpetually support two different & complex code paths, even though we currently rely on scripts
#14:18:25afterldbs++
#14:18:25LBA raises hand
#14:18:33deb has joined #evergreen
#14:18:47eeevildbs: that is the point, yes. not to remove, just to send up a warning flag
#14:18:50DyrconaI vote for deprecation, but I'm using in-db now.
#14:19:14jamesrfi think i'm ok with that then, we are using them but planning to migrate away from them
#14:19:14phasefxjust pie in the sky, but how painful would it be to use that modularity of Evergreen and have an alternate circ module using the scripts live in ILS-Contrib if some folks really want it?
#14:19:40eeeviljeffdavis: well, the problem I see is that if we wait until all possilbe cases are covered (without someone putting in the time to confirm that), they'll never go away
#14:20:03LBAjust so you know that if this is supposed to be a community meeting and not a developers meeting...you are going to have to reduce the jargon load. depracate, in-db circ versus circ scripts....may all need defining.
#14:20:21gmcharltphasefx: anything can live in ILS-Contrib, but as far as trunk is concerned, if we deprecate, that means that trunk isn't obligated to keep compatibility
#14:20:22_dkyle_I'd like to see some fall through option in the code for custom scripts - maybe plperl functions
#14:20:22eeevilphasefx: not technically hard, however it would require that all circ modules be independently maintained, and their feature sets would diverge
#14:20:31jeffif a clear signal is put up for "these are the old, in-db is the new" and deprecation is stated, hopefully it will bring out more concrete examples of "this is what in-db can't do yet", and perhaps patches.
#14:21:02eeeviljeffdavis: yes, that's the hope
#14:21:07dbsthat five minutes for discussion is just about up: move to -dev list for further discussion?
#14:21:08gmcharltLBA: this is a term of art known to people who have set up circ rules in Evergreen
#14:21:11jeffdaviswell I don't feel strongly enough about it to be the only dissenting voice
#14:21:15gmcharltit's not just techie-speak, just mostly
#14:21:32phasefxeeevil: enough for me to know it's not that hard; I'm personally not motivated enough to do such a thing, just curious
#14:21:36gmcharlt(I think we do need to assume some basic familiarity or willingness to learn EG functionality)
#14:21:41eeevildbs: this bears on another disucssion, so I'd like to let it go on for another minute or two...
#14:21:53LBAokay thanks, gmchrlt
#14:22:05berickwe could deprecate w/ the caveat that final script removal is dependent on an in-db script callback alternative
#14:22:09jamesrfquick qeustion on the in-db, where is tsbere's patch to be found?
#14:22:18brian_f has joined #evergreen
#14:22:23phasefxberick++
#14:22:23StephenGWillsI'm willing, just slow and dumb as a post. in-db means Dan ate it, right?
#14:22:25gmcharltjamesrf: http://www.mvlc.org/chdd.patch
#14:22:35gmcharltok, I think we should move the discussion to the list
#14:22:47gmcharltbesides, we'll need to hear from a couple current users
#14:22:51LBA:-D
#14:22:58eeevilok ...well, the other point on that bullet is something else
#14:23:00phasefxin-db means circulation policy that can be configured with a user interface in the staff client
#14:23:12phasefxeffectively :)
#14:23:17gmcharltnext item - (* min) Evergreen branches prior to 2.0 - status and plans
#14:23:17StephenGWillsoh. i want that
#14:23:26afterlin-db lowers the bar for playiing with EG!
#14:23:27gmcharlt5 minutes for this
#14:23:28eeevilgmcharlt: please hold on
#14:23:44eeevilso, we've tabled deprecation of circ scripts for the meeting
#14:23:44csharp Chris Sharp, PINES
#14:23:47eeevilbut
#14:23:58eeevilwe need to discuss http://www.mvlc.org/chdd.patch and where it should go
#14:24:18eeevilthere is one specific blocker: the rule that we not add schema changes after alpha2
#14:24:20Dyrconarel_2_0, but I'm partial.
#14:24:23eeevilthat is, in fact, my rule
#14:24:31eeevilhowever, I would like to push it in
#14:24:50eeevilthe code is clean, and the functionality looks safe, and has been written to be back-compat
#14:24:57eeevilwith circ scritps
#14:24:58dbseeevil: hmm, in my "Versioning" document I had said alpha changes include db schema changes, as features were expected to be mostly complete at that point
#14:25:00eeevilscripts
#14:25:07phasefxif it makes in-db easier to use, I say go for it
#14:25:35eeevildbs: do you mean "yes, schema changes are fine" or "don't do that"?
#14:25:40eeevil(sorry, not following
#14:25:46dbscutting off db schema changes at some alpha, but putting out subsequent alphas with a restriction on any further db schema changes, would be confusing to me
#14:25:51gmcharlteeevil: the patch itself looks OK; I think the real question is how much "just-one-more-thing" we want for rel_2_0
#14:25:55eeevilalso, I want this to go into trunk, 2.0 AND 1.6
#14:25:56dbsso - I vote it goes into alpha5
#14:26:00asimon has joined #evergreen
#14:26:15eeevildbs: and that's the other question ... does this delay beta
#14:26:17dbs(and then once we put out the first beta, no more db schema changes!)
#14:26:20gmcharlteeevil: 1.6 for 1.6.2, I assume?
#14:26:26eeevilgmcharlt: yes
#14:26:34b_bonnerFor those of us live on 2.0, what impact will this have?
#14:26:35tsbereI am partial (having written it) but would vote trunk, 2.0, and 1.6 as well.
#14:26:49eeevilb_bonner: more functionality if you want to use it
#14:27:28dbsI'm not so keen on 1.6 myself
#14:27:34eeevilre "does it delay", by that I mean, shall we push it in and cut a5 now-ish
#14:27:43b_bonnereeevil: thanks, just confirming we won't have breakage of existing policies
#14:28:00eeevildbs: I wouldn't be, except for the easing of upgrade from the current hard-due-date in 1.6
#14:28:20eeevildbs: but because of that (upgrade ease) I'm for it
#14:28:32Dyrconais anyone using the hard due date in 1.6?
#14:28:40bshumWe will be. Someday.
#14:28:41eeevilDyrcona: it's not in a release
#14:28:43dbseeevil: yes, I would push it in to rel_2_0 and cut alpha5 now-ish
#14:29:26afterlSince Biblio (and others) are paying for the hard due dates, we would love to see this in rel_2_0
#14:29:40gmcharltok, it sounds like we have concensus on trunk, rel_2_0, and cutting a5 soon
#14:29:51eeevilgmcharlt: your "just-one-more-thing" point is well taken, but this is the only just-one-more we've considered relenting to (so far ;) )
#14:29:52gmcharltno consensus yet for rel_1_6
#14:30:15gmcharlteeevil: I will kill any further 'just-one-more-things' on sight ;)
#14:30:17gmcharlt(not really)
#14:30:17eeevilwell, there's an implementation, divergent from this, in trunk and 1.6 now
#14:30:26eeevilpushing it into 1.6 would unify that
#14:30:35berick+1 for rel_1_6 for upgrade-ease
#14:30:37rsoulliere has quit IRC
#14:30:40Dyrcona+1 for 1.6
#14:30:42gmcharlt+1 to rel-1_6 as well
#14:30:45phasefx+1
#14:30:54jamesrfthis would be for release in 1.6.2?
#14:30:59eeeviljamesrf: yes
#14:31:03jamesrfok +1
#14:31:37eeevildbs: feel strongly against 1.6, or just meh?
#14:32:05dbsmostly meh; not keen on the additional testing in 1.6 that should accompany it, but meh
#14:32:09phasefxyou extend it you maintain it :)
#14:32:17eeevilphasefx: heh
#14:32:18gmcharltdbs: 1.6.2 will need testing anyway
#14:32:31eeevilok ... I'll accept "meh"
#14:32:37gmcharltsince we've been discussing a5, I'm going to reorder the agenda slightly
#14:32:38dbsgmcharlt: yes, but the more changes in a "minor" branch, the more testing
#14:32:39eeevilso ... I'm done for now :)
#14:32:41gmcharltnext up is - (* min) 2.0 alpha4 to 2.0 gold - works in progress, discuss of what will make it in for general release, hash out schedule
#14:32:51gmcharlt5 minutes for that
#14:33:05eeevil1) ^- that
#14:33:07gmcharltso - we now know that a5 will be cut soonish after tsbere's patch is put in
#14:33:19eeevil2) ui cleanup (vandelay in particular)
#14:33:51dbson behalf of Repke / IISH, per his email to the lists - IISH hopes to go live on the 2.0 beta in November-ish, assuming there is a beta in November
#14:33:53eeevil... ui/bug fixes ... testing
#14:34:00berick3) some smoothing of ACQ processes/bugs
#14:34:22rickd has joined #evergreen
#14:34:27dbwells has joined #evergreen
#14:34:35eeevildbs: IMO, that's very do-able ... (I'll propose beta1 at the start of nov at the latest, barring data-loss bugs)
#14:34:55rsoulliere has joined #evergreen
#14:35:05dbsspeaking of 2.0 alpha4 to 2.0 gold - any further serials work to merge in 2.0? or is the rest going in trunk?
#14:35:15Dyrconaso in two weeks, roughly, for the beta?
#14:35:18dbs craftily noted dbwells' arrival :)
#14:35:30eeevilDyrcona: my hope, yes ... testing will tell
#14:35:51eeevildbs: or his crafty arrival?
#14:36:01Dyrconatimely arrival
#14:36:14eeeviltimeily crafty?
#14:36:15berickdbs: we're applying small serials tweaks/fixes, etc to 2.0 as we can. but no show stoppers ATM (that I'm aware of)
#14:36:15senatorfor serials, nothing new planned by me. bugfixes, but nothing new
#14:37:10dbwells:) my hope is yes, too. Really doing my best to catch up with everyone else at this point.
#14:37:17jcpl-jasonbFor those of us interested in looking, where are serials currently in 2.0? Nothing stands out to me that says "Click here to check in a magazine," etc.
#14:38:08rickd__ has joined #evergreen
#14:38:25senatorjcpl-jasonb: you'll find the jumping-off points for serials if you pull up a bib record in the catalog in the staff client, and click the "Actions for this Record" menu
#14:38:39rickd has quit IRC
#14:38:41rickd__ is now known as rickd
#14:38:43gmcharltany thing else for beta 1?
#14:38:48dbsat a meta-level, are there docs for all of the new features in 2.0? Is the DIG in sync on all of that? I know they're focused on 1.6 at the moment, and release notes are in the hands of slipscomb / gdunbar / KCLS, but might be good to capture details while still fresh in devs' minds
#14:38:54jcpl-jasonbAh, thanks.
#14:38:55dbs<-- troublemaker
#14:39:13StephenGWills eyes dan. I KNEW it!
#14:39:28jamesrfthere is no documentation of new features in 1.6.1
#14:39:50kcollierI'm not aware of any DIG involvement in documenting 2.0 yet.
#14:39:54phasefxbooking has some documentation, doesn't it?
#14:40:13eeeviljamesrf: there is: http://open-ils.org/dokuwiki/doku.php?id=booking (2 pdfs linked there)
#14:40:22kcollierThough we'd love to get our hands on any info out in the wild on it.
#14:41:28rsoulliereAlso added a bit regarding password reset from OPAC.
#14:41:30gdunbarslipscomb and I will have ESI's 2.0 documents out by next Tuesday at the latest - it should cover all the new features we're aware of
#14:41:39b_bonnerKCLS is *slowly* working up documentation as we use/learn it, mostly from an end-users point of view
#14:41:52DyrconaKCLS++
#14:42:09jeffgdunbar++ slipscomb++
#14:42:16eeevilre bullet: schedule hash => a5, RSN -> b1, RSN+~2wk
#14:42:18dbskcollier++ rsoulliere++ gdunbar++ b_bonner++ slipscomb++
#14:42:25LBAand I will nominate Brian_f to help out with documentation with KCLS and Gdunbar. He's running alpha4 right now for a possible demo server on the Amazon cloud
#14:42:38rsoullierePlease foward any documentation to DIG. I will try to put together an outline page for 2.0 on wiki.
#14:42:45gmcharltok - to sum up
#14:42:50phasefxare our commit messages helping? any room for improvement there?
#14:42:58gmcharltbits of documentaiton are making their way to DIG for corralling
#14:42:59gmcharlta5 soon
#14:43:04gmcharltb1 by early November
#14:43:23eeevilwe skipped "back branches" ... shall we go back to that?
#14:43:24gmcharlteeevil: what do you think, one beta? two betas? before general release?
#14:43:36gmcharlteeevil: yep, we'll go back to that in a minute
#14:43:46dbsnote release schedule for 2.0 is roughly at https://launchpad.net/evergreen/2.0 -
#14:43:53eeevilgmcharlt: testing will tell, but I suspect 1 beta and one RC to become 2.0
#14:43:56JimTheWebsiteGuy has left #evergreen
#14:44:06gmcharlteeevil: thanks
#14:44:07eeeviljust a hunch
#14:44:15gmcharltok, moving on (or back)
#14:44:17gmcharlt (* min) Evergreen branches prior to 2.0 - status and plans
#14:44:29dbs will adjust dates accordingly
#14:44:58eeevil would like to kill 1.6 after 1.6.2, concurrent with 2.NEXT
#14:45:32afterleeevil++
#14:45:47phasefx is down with that
#14:45:56eeevilalso, release of 2.0 should likewise kill 1.6.0, though 1.6.1 will probably need to hang on for as long as 1.6.2
#14:46:20jeffdaviswhere "kill" = "stop doing any work (including backporting) on"?
#14:46:25eeevil(note, though, that 1.6.0 /will/ be getting a new release, maybe RSN)
#14:46:52gmcharltjeffdavis: yes, unless somebody else wants to champion and mantain the branch
#14:46:53eeeviljeffdavis: short of critical fixes, yes. 1.6.1 is less buggy and more featureful
#14:46:56phasefxjeffdavis: unless someone wants to volunteer to maintain such a branch
#14:46:58jeffeeevil: were you saying 1.6.1 would "need to hang on" until 1.6.2 is released -- or something else?
#14:47:03eeevilgmcharlt: (or that, yes)
#14:47:32eeeviljeff: that 1.6.1 and 1.6.2 will probably die at or near the same time
#14:47:39jamesrfi think it makes the most sense to maintain 1.6.1 until 1.6.2 is released and considered stable, and i see no reason to declare that 1.6.2 will be the last 1.6.x branch it may be premature
#14:47:40eeevilor, that would be my preference
#14:47:47jeffeeevil: thank you for the clarification.
#14:48:12afterleeevil, suicide pact?
#14:48:28gmcharltwe're running short of time - I move that we continue discussing 1.6.x on the lists
#14:48:38Dyrconaseconded
#14:48:56gmcharltmoving on - (* min) After Evergreen 2.0; roundup of projects that people are working on
#14:49:15gmcharltlet's keep this short - one minute to blast new projects that people are working on
#14:49:48phasefx wants to try moving all remote xul to chrome in the staff client. tsbere: are you interested in such a thing too?
#14:49:50eeevilthat's actively working on
#14:49:58phasefxoh
#14:50:01dbsFor 2.1-ish, EG-Social = Activity Streams + XFN + TT2-based user / item pages (possibly a basis for a new OPAC?)
#14:50:02eeeviltsbere's fallthrough
#14:50:39tsbereI also have some work started on the toolbar opening in new tabs instead of current, as an option and with a modifier (ctrl) held on click
#14:50:39gmcharltok - no doubt there's more, but it can wait
#14:50:44gmcharltnext up - (* min) DIG report
#14:50:48gmcharltkcollier?
#14:50:51bshumtsbere++
#14:50:58afterltsbere+++
#14:51:03kcollierHi, this is Karen Collier reporting for the Documentation Interest Group (DIG).
#14:51:13kcollierDIG has made a good deal of progress collecting, writing, and editing documentation, and converting it to DocBook format.
#14:51:28kcollierThe new host for the documentation site is: http://docs.evergreen-ils.org/ Eventually, this url will lead to a jump page with links to all the various versions and formats of the documentation.
#14:51:38kcollierThe current and only version is the draft version of the 1.6 documentation: http://docs.evergreen-ils.org/1.6/draft/html/
#14:51:52kcollierThe documentation outline shows which areas are complete and which areas still need work. http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:outline
#14:52:01kcollierJeremy Buhler from Sitka contributed a docbook style guide: http://docs.evergreen-ils.org/style_guide/html/
#14:52:12kcollierAs of the last meeting, the documentation was being refreshed manually. It is now generated automatically. On a nightly basis, the documents are pulled from the github repository and the HTML PDF files are generated on the server.
#14:52:24jeffautomation++
#14:52:30kcollierrsoulliere++ for contributing to the DIG updates I've posted. Do you have anything to add that I haven't said?
#14:52:32dbsDIG++
#14:52:38jeffDIG++
#14:52:48rsoulliereThat about covers it
#14:52:59gmcharltthanks
#14:53:03gmcharltnext up - (* min) Reports Taskforce report
#14:53:10afterljenny has that update
#14:53:13jennysmall post coming...
#14:53:17lisppastejenny pasted "Reports" at http://paste.lisp.org/display/115716
#14:53:47afterlNotes from our last taskforce meeting: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-reports:meeting_20100908-notes
#14:54:13afterlWe meet tomorrow!
#14:54:31gmcharltone update on the Equinox reports - with KCLS' help, we've verified that they work in 2.0
#14:54:44jennyWe could definitely use a few more people; if you're interested, let one of the current Rerports people know.
#14:54:58afterlKCLS++
#14:55:02jennygmcharlt++
#14:55:15Dyrcona will see if he can get someone from here to joint the reports task force.
#14:55:17gmcharltmy_staff++
#14:55:25afterlDyrcona+
#14:55:28afterl+
#14:55:30gmcharltok, next up
#14:55:32gmcharlt (* min) Website Team report and discussion
#14:55:35gmcharltLBA?
#14:55:38LBA pasted an update from the Communications Committee at http://paste.lisp.org/display/115713 (which was also sent out to the open-ils-general list)
#14:56:14gmcharlt makes a pitch for people to review and respond to LBA's open-ils-general post
#14:56:23afterl seconds that
#14:56:44LBAYes, respond on general list please. :)
#14:57:11gmcharltok, thanks
#14:57:14gmcharltnext up - (* min) Governance Committee report and discussion (see Governance Structure)
#14:57:22afterldbs has an update
#14:57:25dbsAn update to the update at http://evergreen-ils.org/dokuwiki/doku.php?id=governance:structure:status20101019 - the director of the Software Freedom Conservancy (Bradley Kuhn) said in IRC that invitations to new member projects will go out today - including to Evergreen
#14:57:34jeffhooray!
#14:57:40bshumWhoo!
#14:57:41afterlwoo-hoo!
#14:57:46jennyyea!
#14:57:51LBAsweeeeet.
#14:57:59afterldbs++
#14:58:05berickindeed, dbs++
#14:58:07ocls-damon has quit IRC
#14:58:11artunitalways, dbs++
#14:58:15dbsAlso, from today's governance meeting, expect more membership proposals to get kicked around on the lists
#14:58:50dbsc'est tout from me
#14:58:59gmcharltthanks
#14:59:02gmcharltso, final item
#14:59:09gmcharltchoosing the time for the next meeting
#14:59:22gmcharltshall we say Tueday, 23 November at 2:00 EST?
#14:59:28gmcharltor even Tuesday
#14:59:44dbs+1
#14:59:44tsbere is having issues with the 2:00 EST meetings, as he leaves work at that time currently
#14:59:50tsbereat least on tuesdays
#15:00:11dbsAdditionally, we probably should have a separate dev meeting, there's enough dev-specific content to justify that methinks
#15:00:20berick agrees w/ dbs
#15:00:38eeevilyes ... and sooner than nov23, IMO
#15:00:42brian_falso Thanksgiving week might be hard for people traveling
#15:01:13gmcharlton the theory that beta1 will be out by then, 9 November for a dev meeting, 23 November for a general community meeting?
#15:01:32afterlgmcharlt: nice, tight meeting - can you bring it in under an hour?
#15:01:33Dyrcona can change tsbere's schedule if tsbere would like.
#15:01:34eeevilgmcharlt: or, dev on nov 2
#15:01:40eeeviler
#15:01:40eeevil1
#15:01:47eeevilin prep for beta1
#15:01:51jcpl-jasonb has quit IRC
#15:01:52eeevilto clear up any final issues
#15:01:55gmcharltok
#15:02:06gmcharltso 11/1 dev (and shall we say 11 a.m.)
#15:02:11eeeviland, for tsbere (with his patch going it
#15:02:14eeevilright, earlier
#15:02:25gmcharlt11/23 for general meeting (2 p.m., as usual time)
#15:02:29bshumgmcharlt: 11 EST?
#15:02:36gmcharltbshum: yes
#15:02:42tsbereMondays aren't a problem for me time-wise if you want to do it later.
#15:02:43eeevilis 8am Pacific too earlier for westerners?
#15:03:01dbsI can make the first half hour of 11/1 at 11
#15:03:07b_bonnera little early for me, but I mostly lurk anyway
#15:03:16eeeviltsbere: monday_meetings-- (wow... alliteration with symbols)
#15:03:21Dyrconawhy not the usual 2pm time.
#15:03:45eeevilhrm... we need our dbs if we can have him
#15:03:45tsbereeeevil: 11/1 is a monday on my calendar.
#15:03:55Dyrconamine, too. :)
#15:03:56eeevildur
#15:03:58eeevilso it is
#15:04:06gmcharltback to 11/2 ?
#15:04:11dbseeevil works an 8-day week, it's the secret of his productivity
#15:04:29Dyrconahe needs to upgrade to my 9-day week.
#15:04:33eeevildbs: it's the secret ... of my productivity is yet to be seen
#15:04:34Dyrcona:)
#15:04:47gmcharltok, since we're spinning
#15:04:52gmcharltlet's say 11/23 for the general meeting
#15:04:58gmcharlt11/1 or 11/2 for the dev meeting
#15:05:00dbs11/2++
#15:05:00eeevil11/1@2pm EST
#15:05:03eeeviler
#15:05:05StephenGWills11/2++
#15:05:06eeevilor not ;)
#15:05:09gmcharltwith the time to be nailed down on the maiing lists?
#15:05:14StephenGWillsdoctor appt on 11/1 at 2
#15:05:15eeevil11/2 @11am EST?
#15:05:26phasefxsounds good to me # re: mailing list
#15:05:30tsbereI am ok with 2:15 instead of 2:00 on tuesdays (or thursdays). Just give me a few min of travel time ;)
#15:05:30eeevilgmcharlt: sure, lists it is
#15:05:44Dyrcona11/2 @ 2pm EST would work. I can change tsbere's hours for the day.
#15:05:52Dyrconaunless he objects.
#15:06:03gmcharltok - so tenatively 11/2 at 2 p.m. EST for dev meeting
#15:06:08gmcharltand to be confirmed on list
#15:06:12gmcharlt moves to adjourn
#15:06:18jeffsecond!
#15:06:22Dyrconathird
#15:06:25berickgmcharlt++
#15:06:29deb has quit IRC
#15:06:44Dyrconagmcharlt++++: best mc around.
#15:06:58bshumAgreed.
#15:06:58StephenGWillsoh yo!
#15:07:01afterl pats gmcharlt on the back. Three minutes over - not bad!
#15:07:04eeevilDyrcona: not better than mc hammer
#15:07:07rsoulliere has quit IRC
#15:07:13Dyrconalol
#15:07:29eeeviland smaller pants, too ... not sure if that's a plus or minus, though
#15:07:41eeevil steps away for a minute
#15:07:45StephenGWillsdon't touch that
#15:07:54afterl groans
#15:07:56LBAu can't touch ...that
#15:08:17StephenGWillsoh look...work to do.
#15:08:20Dyrconanot with a 3-meter cattle prod.
#15:08:24StephenGWillsthanks y'all
#15:08:41av_ocls has quit IRC
#15:09:01kcollier has left #evergreen
#15:09:44Michele_ has quit IRC
#15:10:10Dyrcona goes to see if he can talk someone into joining either or both of DIG and the Communications committee.
#15:10:29bshumDyrcona: May the force be with you.
#15:10:43katesheehan has quit IRC
#15:11:51tsbereOn the subject of my hard due dates patch: I have yet to write an upgrade script, the patch currently has none (but upgrade scripts for the previous incarnation do exist). Should I add that to my todo list, and if so, should it try and maintain data from testing the pre-patch version?
#15:15:09Dyrconatsbere: if alpha5 isn't ready tomorrow, we'll apply your patch when I "upgrade" the main test server here.
#15:15:30Dyrconawe're just running on rel_2_0 at the moment, right?
#15:15:38Dyrconanot any specific alpha?
#15:15:55Dyrconaoh, and I succeeded there should be more person for DIG.
#15:16:52Dyrcona goes to check on the answers to his questions himself.
#15:16:56finnapz has left #evergreen
#15:17:08StephenGWills_ has joined #evergreen
#15:17:50tsbereDyrcona: I think we are on svn checkout of rel_2_0, yes
#15:18:51Dyrconawe haven't applied your patch on that server, right? you're testing on a virtual machine?--just for the record. :)
#15:19:20tsbereDyrcona: Yea, a virtual machine on my workstation. I haven't gotten a functional one on the new servers yet. :(
#15:20:33Dyrconaall right. i'll do an upgrade tomorrow and a fresh load on thursday, and hopefully everyone will be happy on Monday while I'm on vacation. :)
#15:21:02StephenGWills has quit IRC
#15:21:02StephenGWills_ is now known as StephenGWills
#15:27:34kmlussierDyrcona: Oh, nice. i didn't realize you would be on vacation. Can I have your cell? ;-)
#15:28:45Dyrconakmlussier: I can send you the information that you need tomorrow afternoon. Including a windows installer for the client if necessary.
#15:29:21kmlussierDyrcona++
#15:30:21DyrconaIt looks like we won't have our training server up and stable enough in time, so we'll just use the one that we have been using.
#15:30:34DyrconaOr, at least, I won't plan on it being up.
#15:30:39tsberevirtual networking is unhappy with me this week. :(
#15:30:59Dyrconahard drives have been unhappy with me this week.
#15:49:32kmlussier has quit IRC
#15:50:08bshum has quit IRC
#15:59:36Meliss has quit IRC
#16:02:46tildeequals has joined #evergreen
#16:05:39bshum has joined #evergreen
#16:12:36brendan2 has quit IRC
#16:12:49brendan2 has joined #evergreen
#16:13:38rayner has quit IRC
#16:16:42IN_wendy has quit IRC
#16:17:25collum has left #evergreen
#16:23:53granitize has quit IRC
#16:37:36moodaepotsbere: I missed the meeting earlier, if I want to try out in-db circ I'm guessing the patch needs to checkout the rel_2_0 branch and apply it to the code for a clean fresh install?
#16:38:43jamesrf has quit IRC
#16:44:15moodaepobshum: Are you still looking at PG Agent to auto-schedule SQL reports?
#16:44:39bshummoodaepo: I got lazy and just went with the tried and true of using cron.
#16:45:06tsberemoodaepo: Which indb circ patch you looking to test? I don't have any fallthrough ones that will deal with the hard due date stuff yet.
#16:45:14moodaepoWould there have been any advantage to PG Agent?
#16:46:07moodaepotsbere: I just want to try them out since I was going to give alpha4 a whirl today (fresh install) I saw this mentioned > http://www.mvlc.org/chdd.patch
#16:46:14bshummoodaepo: The idea of using PGAgent at the time we were investigating was to see if it would be "easier" to integrate those operations with PGAdmin3 since we used that as our primary GUI for looking at database things.
#16:46:40bshummoodaepo: In actual practice, it was taking me alot longer to figure out how to setup PGAgent to call the scripts I wanted. Plus I had to write new scripts anyways.
#16:47:05bshummoodaepo: And if memory serves, it seemed that we needed to run PGAgent somewhere in our systems in order to have it do its job.
#16:47:09tsberemoodaepo: Basic indb circ will work fine without any patches. The chdd.patch file is a change to the (unreleased) hard due date functionality and I don't think will work on alpha4.
#16:48:52moodaepobshum: Yup I was going to look into it when I'd heard you wanted to check it out, if I do I'll let you know how things go.
#16:48:58bshummoodaepo: If all PGAgent seemed to be doing was defining a schedule for the DB scripts, then there still needed to be additional components to handle the actual conversion into formats we needed + email sent out. With that many scripts being called up, it seemed more effective to operate it entirely from the cron.
#16:49:17bshumI think it might be handy for scheduling maintenance tasks though.
#16:49:37moodaepotsbere++ # will do
#16:50:23moodaepobshum: Hmm in that case it might be better to go with cron like you did...and what maintenance tasks would you use PG Agent for?
#16:50:50bshumYeah, pgAgent calls SQL scripts or shell/batch scripts.
#16:51:16bshumSo it does similar things to what cron does.
#16:52:25bshumI guess if there was more complexity to the scripts, and steps for the various scripts, pgAgent could handle those. Not sure though, we have a very procedural order for things in the scripts.
#16:52:39Dyrcona thinks it unusual that his Ubuntu Lucid server says a restart is required after having done a shutdown -r now....
#16:52:50moodaepobshum: Yea I don't think I'm going to use it have everything setup that it would provide : ) > http://www.postgresonline.com/journal/archives/19-Setting-up-PgAgent-and-Doing-Scheduled-Backups.html
#16:53:00jeffDyrcona: could just be a stuck /etc/motd -- i've seen that
#16:53:22Dyrconajeff: will take a look at that when it comes up again.
#16:53:26bshummoodaepo: That's pretty much the conclusion I drew as well.
#16:53:49moodaepoMight want to look at your scripts though!
#16:53:53afterl has quit IRC
#16:57:57bshummoodaepo: They'll be ready sometime soon.
#16:58:03bshumWell more ready
#17:00:23moodaepo isn't the mantra..release early release often?
#17:00:42moodaepo: )
#17:01:07tsberemoodaepo: Not when you release patches so often the other devs can't keep up. <_<
#17:03:44mrpeters-isl has joined #evergreen
#17:04:34AaronZ has quit IRC
#17:04:36moodaepotrue enough
#17:04:53Dyrcona is shutting down the test evergreen server for tonight/tomorrow.
#17:05:34tsbereDyrcona: BTW, I don't even have a client installed on my workstation that can log into that server right now, so I probably wouldn't have noticed ;)
#17:05:59Dyrconai'm letting you know in case someone (Dave?) asks.
#17:06:40Dyrconai'm going to stop the processes and do the svn update. I'll wait to do the make until tomorrow morning.
#17:06:58DyrconaI will also update the OS packages now.
#17:07:00tsbereDon't forget to use the ils20 folder instead of the ils folder on the update. I think ils is trunk.
#17:07:11DyrconaOK. Good to know.
#17:07:41tsbere updates the db reload script whenever we change between trunk and 2.0
#17:09:00Dyrconaguess i'll update the OS on the db server, too, or is that too risky to try 20 minutes before quitting time?
#17:10:45tsbereDyrcona: aptitude safe-upgrade should be safe enough
#17:13:34Dyrconatsbere: Is there anything opensrf or evergreen-related (other than Pg) that I need to worry about on the database server?
#17:14:14DyrconaAnything that the db reload script won't take care of?
#17:14:47DyrconaHmm. Guess it depends if any new Perl modules are needed since the last time we updated, huh?
#17:22:29tsbereDyrcona: That would be about it, yea.
#17:22:58DyrconaThe OS is updated on the two servers, so I don't have to do that tomorrow. It's going to be another busy day for me.
#17:23:18yboston has quit IRC
#17:24:34tsbereI have my own work cut out for me figuring out the reason the virtual machines can't talk to the net
#17:24:57tsbereand once I do, documenting everything and then possibly bringing machine after machine online (real and virtual)
#17:26:00DyrconaYeah, and you'll have to answer my stupid questions about building evergreen clients, too. :P
#17:29:31DyrconaTTFN!
#17:29:35Dyrcona has quit IRC
#17:32:34eeeviltsbere: I'll be working on integrating and backporting you hdd patch tonight or tomorrow morning ... would you perchance like to work on an upgrade script to change the state of the db from pre to post patch?
#17:33:25eeeviltsbere: and, should I be working from http://www.mvlc.org/chdd.patch or do you have something more recent
#17:36:00eeeviltsbere: I'll check later ... commuting
#17:37:15jenny has left #evergreen
#17:39:33jamesrf has joined #evergreen
#17:45:29phasebb has joined #evergreen
#17:56:02tsbereeeevil: Changing the base DB state from pre to post is easy. Changing it and keeping old data is harder. I can see what I can come up with, though. And as for "more recent" or not, I literally came to a halt on all of my projects after wrapping up chdd.patch due to new servers giving me grief.
#17:56:04parsr has quit IRC
#18:11:48b_bonner has quit IRC
#18:22:22slipscomb has quit IRC
#18:25:41LBA has left #evergreen
#19:07:50phasebb has quit IRC
#19:08:57tsbere can't recall why his potential update function for hard due dates returned an int
#19:36:51tsbereIf I am allowed to say "nobody should be using ths, we can wipe out old hard due date data" then I can get this update script written easily. It is the "saving old data" part that is tough. :(
#19:37:26tsberes/ths/this/
#19:41:57bshumIf it hasn't been part of any releases, would anybody have any existing hard due date data that would need to be saved?
#19:42:17bshum(other than the folks developing it I guess)
#19:42:23tsberePeople on the bleeding edge and/or testing the original variant, I would assume
#19:43:56jamesrf has quit IRC
#19:50:52mrpeters-isl has quit IRC
#20:13:48asimon has quit IRC
#20:24:45eeeviltsbere: I was planning to simply drop and recreate the table that you've modified -- it's not in a release or in use by anyone, so no worries on that
#20:34:12jamesrf has joined #evergreen
#20:37:34tsbereeeevil: Oh, that makes it even easier. :D
#20:39:37tsbereLets see.....
#20:39:47tsbereOne drop table, two create tables, and two alter tables. That was easy.
#20:40:03tsbereUntested, but easy.
#20:40:51tsbereWant me to paste it?
#20:42:21eeevilsure, thanks
#20:43:04eeevilactually... would you mind emailing that and the patch to -dev with a DCO?
#20:43:33lisppastetsbere pasted "untested upgrade script" at http://paste.lisp.org/display/115729
#21:02:11tsbere keeps getting interrupted
#21:06:19tsbereeeevil: I have sent a message to the dev list now. And gotten my copy back.
#21:11:00jamesrfis there an opensrf call which will return boolean if a given org unit has holdings for a given bib?
#21:11:42jamesrfclosest i can find is open-ils.supercat.record.basic_holdings.retrieve
#21:12:43jamesrfwhat i am trying to do is modify open-ils.search.metabib.record_to_descriptors so that it will be able to limit by org unit
#21:18:12jamesrfcurrently it sometimes shows item types that might not actually exist at your org unit in the advanced holds screen
#21:19:01jamesrfit would be nice if this were scoped properly with the check org unit hiding
#21:32:40jamesrf_ has joined #evergreen
#21:37:00shadowspar has quit IRC
#21:37:01denials has quit IRC
#21:37:24jamesrf has quit IRC
#21:37:24brendan2 has quit IRC
#21:37:25gmcharlt has quit IRC
#21:37:25mck9 has quit IRC
#21:37:25tsbere has quit IRC
#21:38:53shadowsp1r has joined #evergreen
#21:39:00denials_ has joined #evergreen
#21:39:57jamesrf_ is now known as jamesrf
#21:41:40brendan2 has joined #evergreen
#21:41:40mck9 has joined #evergreen
#21:41:40gmcharlt has joined #evergreen
#21:41:40tsbere has joined #evergreen
#21:43:35bshum has quit IRC
#22:15:05tildeequals has quit IRC
#22:18:56jamesrf has quit IRC
#22:41:11mrpeters-isl has joined #evergreen
#22:49:49dbsooh, http://docs.evergreen-ils.org/ is looking nice - time to get that linked and highlighted prominently on http://evergreen-ils.org/documentation.php as a work-in-progress methinks?
#22:49:54dbsDIG++
#22:51:17gmcharltdbs: yep, now that they have the landing page, it's time
#22:51:29dbs is editing documentation.php as we speak
#22:51:56gmcharltdbs++
#22:51:57gmcharltDIG++
#23:04:41dbshttp://evergreen-ils.org/documentation.php is updated
#23:04:56dbsCSS is a bit weird but oh well, content > format
#23:07:12dbsI'm going to suggest to the DIG that they add a link to instructions for reporting doc bugs to the footer of their HTML pages - maybe they can use bugs.launchpad.net/evergreen too
#23:08:32gmcharltgood idea
#23:19:42tildeequals has joined #evergreen
#23:28:25phasebb has joined #evergreen
< Monday, October 18th, 2010Raw Log FileWednesday, October 20th, 2010 >