Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Friday, April 1st, 2011

< Thursday, March 31st, 2011Raw Log FileSaturday, April 2nd, 2011 >
#TimeNickMessage
#00:23:45jamesrf-ak has quit IRC
#00:25:52jamesrf-ak has joined #evergreen
#00:26:38sgirard has quit IRC
#00:33:10sgirard has joined #evergreen
#01:04:33sgirard has quit IRC
#04:02:43agJohn has quit IRC
#08:22:06Dyrcona has joined #evergreen
#08:45:57KingNightWolf has joined #evergreen
#08:46:36dbs has joined #evergreen
#08:50:54collum has joined #evergreen
#08:53:15jenny has joined #evergreen
#09:15:00yboston has joined #evergreen
#09:47:25KingNightWolf_ has joined #evergreen
#09:50:17KingNightWolf has quit IRC
#09:50:17KingNightWolf_ is now known as KingNightWolf
#10:24:00sgirard has joined #evergreen
#10:46:27collum has quit IRC
#10:47:25KingNightWolf has quit IRC
#10:47:46KingNightWolf has joined #evergreen
#10:54:37adbowling-isl has joined #evergreen
#10:58:41wendy has joined #evergreen
#10:59:36StephenGWills has joined #evergreen
#11:00:27sborger has joined #evergreen
#11:09:13wendy has quit IRC
#11:09:47sborger has left #evergreen
#11:21:40bshumDmagick: Heh, nice circ policy bug ticket :)
#11:21:57bshum+1 to most of your sentiments
#11:22:27DmagickWeren't mine, I was just passing them along. I use the DB and PSQL for all that stuff. ;)
#11:22:47tsbereI responded. First part? What version of evergreen?
#11:22:50bshumSo do we, paging 15 rules when we have over 400 is just brutal.
#11:23:51dbstsbere: I sent that response too :)
#11:23:56DmagickIf you sort by org unit in the db, you have what you need in a few secs.
#11:24:03dbsalbeit via email, so it will probably get appended in a few minutes.
#11:30:34moodaepodbs++ tsbere++
#11:30:41suho has joined #evergreen
#11:31:28tsbereDmagick: I think most of my response holds in 1.6.0.x. The constraint to keep dupe rules out doesn't work due to nulls never matching nulls even in a constraint.
#11:37:46sylvarCan you test COALESCE(value1, 'f0r38jf2n;') = COALESCE(value2, 'f0r38jf2n;')?
#11:39:40tsberesylvar: I fixed the issue in trunk/2.1 already.
#11:46:33sylvarCool.
#11:50:46phasefxsilly question, but in hold_matrix_matchpoint, is the holdable column a matchpoint, or a directive of the rule (hold allowed, hold denied)?
#11:51:14bshumphasefx: I think that's a directive of the rule.
#11:51:22bshumIf I understood your question right.
#11:51:29bshumBut don't consider me authoritative on that...
#11:51:36phasefxthat seems to make sense to me
#11:52:17levacjeep has joined #evergreen
#11:53:55phasefxbshum: thanks
#11:55:07agJohn has joined #evergreen
#11:55:21levacjeepwhen creating a skin, would anyone know how to exclude certain "Copy Summary" fields on the single item page?
#11:56:03levacjeepexample: http://i.imgur.com/IQMrb.png
#12:08:06sylvarlevacjeep: rdetail.js lists all OPAC-visible statuses. If you want to keep those statuses OPAC-visible, you'd probably need to add some logic to function rdetailBuildStatusColumns() to check that the status code matches your preselected list.
#12:08:39sylvarBut you'd also have the possibility of users saying "It says there's 1 copy, but it's not showing up on the list of statuses"
#12:09:41sylvarYou might want to combine "Building use" and "At reference desk" and "Library use only" into one status.
#12:10:20mtisi_ has joined #evergreen
#12:10:24sylvarIn general, use as few statuses as you can, and use copy locations to offer information like "At reference desk". The *status* of those items is that they're checked in.
#12:11:17sylvarSo, to sum up, levacjeep, you might be able to modify an important piece of JavaScript, but you should probably refactor your statuses.
#12:11:35sylvarThat way, the list wouldn't be so long.
#12:13:37levacjeep has quit IRC
#12:14:00mtisi has quit IRC
#12:16:32dbs has quit IRC
#12:49:46levacjeep has joined #evergreen
#12:52:45suhothayan has joined #evergreen
#12:56:03suho has quit IRC
#12:56:09levacjeep has quit IRC
#13:05:38mtisi_ is now known as mtisi
#13:09:38rsoulliere has joined #evergreen
#13:10:46tater-laptop has joined #evergreen
#13:10:48tater-home has joined #evergreen
#13:14:31collum has joined #evergreen
#13:24:06eeevilphasefx: re "holdable" on the matrix, it's a directive. a hard "if using this mathpoint, DENIED!" setting. like circulate on the circ matrix
#13:24:25eeevil(btw, I'm not here)
#13:25:10eeevil(however, based on the volume of recent important updates in rel_2_0, I'd like to poll on cut-or-not)
#13:28:07phasefxeeevil: roger that
#13:28:11dbs has joined #evergreen
#13:28:25tsbereeeevil: My recent fine generator patch on launchpad may apply to 2.0 as well as trunk/2.1
#13:28:32tsbere hasn't tried it against 2.0
#13:28:54atz_ is now known as atz
#13:29:36eeeviltsbere: bug #?
#13:29:54tsbereeeevil: 747533
#13:30:12tsbereIt helps stop a potential division by 0 error
#13:30:14atheosanyone know what the functional reasoning is for last_xact_id in the gateway API for circ.money.payment ?
#13:31:31eeevilatheos: all fields of that name are used for optimistic locking ... collision detection
#13:32:50atheoseeevil thanks, I figured out the purpose of where_process pretty quickly, but last_xact_id had me stumped for a few hours.
#13:33:11berickatheos: for that method, the purpose is to prevent payments against xacts on stale data
#13:33:35bericke.g. multiple parallel payments to the same xact, one via credit card in the opac, one via staff client
#13:34:39atheosmakes good sense. I had a quick routine that verified the bill still matched before processing circ.money.payment for similar purpose
#13:34:54atheos can't wait until I can scrap this, and use the built in CC processing
#13:36:11eeeviltsbere: yes, that looks like it would be good in 1.6 as well, modified if necessary
#13:36:50LBA has joined #evergreen
#13:38:07ChanServ changes topic to "Community meeting agenda: http://ur1.ca/3q5rh | Welcome to the #Evergreen library system channel! | We are publicly logged. | Large pastes at http://paste.lisp.org/new/evergreen"
#13:39:33suhothayan is now known as suho
#13:42:19eeevildbwells: thanks for taking on change to uniquification of index normalizers!
#13:53:42jcpl-jasonb has joined #evergreen
#13:59:40afterl has joined #evergreen
#14:00:03bshumOkay, community meeting time!
#14:00:39bshumFirst, introductions; while we do that, any volunteers for leading/minutes?
#14:00:48bshum is Ben Shum, Bibliomation
#14:01:10rsoulliere is Robert Soulliere Mohawk College
#14:01:14afterl is Amy Terlaga, Bibliomation
#14:01:48sgirardis Sean Girard, lurking on behalf of Spokane Public Library
#14:01:52LBALori Ayre,Galecia Group
#14:02:30jenny is Jenny Turner, PALS
#14:02:39dbs is Dan Scott of Laurentian University / Conifer
#14:02:56phasefx is Jason Etheridge, Equinox
#14:03:24atheos is Niles Ingalls, Hussey-Mayfield Memorial Public Library / Indiana
#14:05:02afterlSmall group today
#14:05:24bshumYeah, I think kmlussier said she had a conflict and wouldn't be available.
#14:05:33dbsSounds like a good day to volunteer for leading/minute taking!
#14:05:35eeevil (Mike Rylander, ESI) lurks as well
#14:05:53jcpl-jasonband some of us just lurk, though I've just blown that...
#14:06:12afterlAnyone else want to out themselves?
#14:06:27tsbere lurks and ignores during most of the community meetings ;)
#14:06:29bshumHeh, well if someone would be willing to do notes, I can run through the agenda.
#14:06:47bshumShould be pretty quick, right? ;)
#14:07:00afterlI can take notes though technically this is a vacation day for me
#14:07:07afterlhave to do taxes today
#14:07:10afterlmight as well
#14:07:16dbsafterl++
#14:07:17LBAhere we go again with the vacation
#14:07:17dbsbshum++
#14:07:23dbsbibliomates++
#14:07:23bshumHeh okay
#14:07:31bshumgmcharlt' style
#14:07:32bshumLet's go
#14:07:37bshum3. Review action items
#14:07:49bshumI. Amy Terlaga will follow-up with Brian Feifarek and Lori Ayre via email about community servers pgrade
#14:07:53bshum*upgrade
#14:07:56afterlI did
#14:08:05tater-home has quit IRC
#14:08:06LBAand Brian did.
#14:08:07afterlLBA followed up with Brian
#14:08:09bshumCool
#14:08:12sborger has joined #evergreen
#14:08:15bshumII. Lori is collecting success stories and will work with Web team to post once she has 5 or 6.
#14:08:26LBAAmazon v-image and demo site are now current.
#14:08:49bshumbrian_f++ LBA++
#14:08:50LBAI have those with permission to post five of them. need to figure out where they go...
#14:09:21LBAi will add that to our next communications/web team agenda...I've been negligent about that.
#14:09:59bshumOkay, sounds good.
#14:10:05bshumWe'll keep our eyes open :)
#14:10:12bshumIII. Amy Terlaga will put an e-mail to the list for volunteers with the DIY interest group.
#14:10:16afterlI did
#14:10:23afterlbshum volunteered
#14:10:42afterlthat's you
#14:10:53bshumAnd moodaepo too, rsoulliere, csharp, and many others have begun brainstorming for it.
#14:11:02afterlexcellent
#14:11:24bshumSo all sys admins out there should come hang out with us during the Evergreen conference
#14:11:35bshumNext item: IV. Track down DIG volunteer names for interest group.
#14:11:39afterland sysadmin groupies
#14:11:41bshumI think that's for afterl?
#14:11:46afterlI did
#14:11:50moodaepo runs in late
#14:11:52afterlKaren Collier is coming
#14:12:05afterlShe'll be leading it
#14:12:40bshumCool.
#14:12:42bshumV. Need to send out a call for volunteers to help beef up documentation on reports
#14:13:14bshumHmm, guess that's from reports
#14:13:20bshum*reports taskforce
#14:13:24jennyI mentioned it at the Reports TF meeting on Wednesday - didn't have anyone clamoring to write anything
#14:13:45jennyI can beg on the DIG list perhaps
#14:14:09afterlMake that a follow up agenda item for next time?
#14:14:13jennyyup
#14:14:33bshumOkay, deferred for now, with an offer for a kind soul to help.
#14:14:43bshumOn to committee group reports
#14:14:48bshum4. Communications committee & Website Team report and discussion.
#14:15:13LBAWe've completed two surveys. One of the needs of the Evergreen community.
#14:15:24LBAas represented by the General Mailling List.
#14:15:31LBAWe've analyzed those responses.
#14:15:38LBAWe've surveyed the current site.
#14:15:53LBAAnd are looking for ways to make some changes that are responsive to what we've learned.
#14:16:21LBAWe are also close to having a first draft of a longer term plan for the Evergreen online ecosystem....
#14:16:34LBAAmy, anything to add?
#14:16:41afterlNo, that's good.
#14:17:21LBAFYI, all things WebTeam/Communications committee live here: http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam
#14:17:28bshumOnline ecosystem, huh? Fancy :)
#14:17:47LBA;-)
#14:17:47afterlThat's LBA-speak
#14:18:01LBAvacationer
#14:18:07bshumLBA++ :)
#14:18:16bshumNext, 5. Conference committee
#14:18:28bshumOh, unless there are questions for the web team?
#14:18:46bshum got derailed by fun vocabulary
#14:18:57LBAAnoop is here too from our team...
#14:19:14afterlConference committee update: We're up to 153 attendees as of last Monday
#14:19:26LBAwahoo!
#14:19:50moodaepo << Anoop
#14:20:02afterlYesterday was the deadline for presenters to get their presentations in for the flashdrive give-aways
#14:20:17afterlThe program will be off to the printer VERY SOON
#14:20:40afterlESI and PINES are planning a REALLY fun after hours event the first night of the conference
#14:20:54afterlI can't tell you because that would ruin the surprise
#14:20:58dbs hangs head in shame for missing deadline
#14:21:08afterl does too
#14:21:10LBA also hanging head
#14:21:16afterluh-oh
#14:21:26atheosdid Indiana get ours in? not sure if I should be hanging my head either
#14:21:32afterlso those two presentations on the flashdrive better be good ones
#14:21:35bshumSo will this flash drive be a very fancy toy to bring home?
#14:21:42afterlsure, sure
#14:21:48dbshah, 32 MB flash drive should be more than enough
#14:21:52afterlwe'll also have dine arounds and pub crawls
#14:22:07afterland a vendor reception the second night of the conference
#14:22:13sylvarbrick store and.... brick store
#14:22:26sylvarwon't have to crawl far :)
#14:22:36afterland the whole thing is going to be a grand old time and everyone should come
#14:23:02bshumCool
#14:23:04dbs might try to organize an antisocial evening hackathon, like "Genericize the TT OPAC"
#14:23:13moodaepodbs++
#14:23:21bshumdbs++
#14:23:24phasefxwith beer
#14:23:29dbsbeer++
#14:23:29moodaepoWhere do I sign up?
#14:23:35afterloh and we have people coming from
#14:23:44afterlAmsterdam and Ethiopia!
#14:24:06dbsThey put the "I" in International. Awesome
#14:24:18afterlYup, that's what I've been saying
#14:24:29LBAlast year the dutch flaked
#14:24:44LBAsome issue with volcano ash or something unlikely
#14:24:52afterlyes, not their fault
#14:25:20LBA;-)
#14:25:21bshumHeh anything else for the conference before we move on?
#14:26:11StephenGWills_ has joined #evergreen
#14:26:23afterlNope
#14:26:34bshum6. Documentation Interest Group
#14:26:43rsoulliereUpdated DIG info page: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig
#14:26:50rsoulliereMoved resources to this page instead of having an extra generic link to "resources"
#14:27:07rsoulliereWe added link + info to Brian Feifarek's test server.
#14:27:14rsoullierebrian_f++
#14:27:42rsoulliereAdded additional DIG roles: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:digparticipants
#14:27:54rsoulliereKathy Lussier volunteered for Public OPAC/staff tasks Content Coordinator
#14:28:00rsoullierekmlussier++
#14:28:13rsoulliereJenny Turner volunteered for Reports Coordinator
#14:28:25rsoulliereJenny++
#14:28:37rsoulliereJust to emphasize that these roles are for coordinating efforts (communicating) and not writing the entire parts.
#14:28:50rsoulliereWe still need section authors volunteers who can volunteer for writing and editing sections
#14:29:12rsoullieresee outlines:...
#14:29:18rsoulliere1.6 outline: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:outline
#14:29:28rsoulliere2.0 outline: http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.0:outline
#14:30:05rsoulliere volunteered for DocBook Conversion Coordinator
#14:30:18rsoulliereStill need the following roles filled...:
#14:30:22dbsrsoulliere++
#14:30:26StephenGWills has quit IRC
#14:30:26StephenGWills_ is now known as StephenGWills
#14:30:27rsoulliereAdministration/Development Content Coordinator
#14:30:34moodaeporsoulliere++
#14:30:35rsoulliereWould be great to have someone who works with a lot of developers (e.g. participates at each dev meeting), has good understanding of sound technical documentation practices and understand documentation needs in these areas.
#14:31:01rsoulliere...fill the Administration/Development Content Coordinator role
#14:31:09rsoulliereA certain Evergreen developer with a strong documentation background (who is probably already too busy) comes to mind...;-)
#14:31:43moodaeporsoulliere: Maybe you could contact people who come to mind directly and see?
#14:31:59rsoulliereOther role...
#14:32:07rsoulliereStyle Coordinator
#14:32:19rsoulliereWould be good to have someone with web/documentation style experience or ideas and has experience with DocBook style sheets. Certain people from SITKA come to mind...;-)
#14:32:52tater-laptop has quit IRC
#14:33:28rsoullieremoodaepo: yes, we might contact folks directly...
#14:33:35dbs whistles
#14:33:39rsoulliereA few chapters have been added to 2.0 version of documentation but a lot of work is still needed.
#14:33:49rsoulliereIs anyone working on "Public Access Catalog" documentation for version 2.0 or can add URL pointers to the outline to existing documentation?
#14:34:37rsoulliereThere are many differences between 1.6 and 2.0 so it would be nice to illustrate these differences in the official documentation for 2.0.
#14:35:03LBAI can't point you to documentation but we are trying to get the 2.0 patron interface up on Brian's demo server.
#14:35:49rsoulliereLBA: thanks, keep us posted on progress.
#14:35:55rsoulliereLastly, Reminder that The DIG Interest Group meeting/hackfest at the Evergreen Conference will take place at 10:00-12:00 on Wednesday, April 27.
#14:36:14afterlOh, that's good. Nice plug.
#14:36:20LBA raises hand
#14:37:00LBAAny reason the Documentation section at http://www.evergreen-ils.org/dokuwiki/doku.php should live there instead of on DIG pages where all other documentation is?
#14:38:15dbsFor the files, probably because that's where the files were uploaded in a hurry
#14:38:21rsoulliereThe wiki pages go back to a time before the official documentation pages. Many things have been migrated.
#14:38:22moodaepoLBA: I'd consider that as part of current website re-org/cleanup
#14:38:32moodaepoAlso what dbs said
#14:38:44rsoulliereIts quicker for most people to get docs in the wiki.
#14:38:57LBAGreat. Recent Acquisitions documentation (draft form) went there instead of DIG ...wondered why.
#14:39:11bshumThere's a DIG meeting on this upcoming Monday right?
#14:39:24rsoullieremost of the Acq. docs have been added to the DIG official docs as well.
#14:39:43moodaepoI'd like to put this on the next meeting agenda and maybe the dig/web folk can discuss how things should proceed from now on
#14:39:57LBAthanks
#14:40:01moodaeponext meeting == conference
#14:40:03rsoulliereI mentioned at the DIG meeting and I thought I posted on the DIG list...?
#14:40:41bshummoodaepo: Okay, followup regarding DIG/web discussion for next meeting.
#14:40:59moodaepobshum++ # wrangle on
#14:41:09bshumAlright, next on
#14:41:23bshum7. Reports Taskforce report
#14:41:33jenny We last met on Wed, March 30.  Notes from past meetings are posted here: http://open-ils.org/dokuwiki/doku.php?id=evergreen-reports:taskforce_meetings (Wednesday’s still to be posted, I think)
#14:42:01jennyWe’re hoping to recruit some additional volunteers at the conference and started generating some discussion topics for the Task Force Meeting.  A current listing can be found in our Google Group discussion, “2011 International Evergreen Conference Reports Task Force Meeting Ideas:” http://groups.google.com/group/open-ils-reports. 
#14:42:39jennyThe Task Force meets on Wed, April 27 from 10 am to noon - which is against the DIG meeting.
#14:43:18afterlThere will be treats!
#14:43:48rsoulliereI plan to "roam" on hackfest day.
#14:44:04rsoulliereI'll try to be where the treats are.;-)
#14:44:10afterlheh heh
#14:44:10jennyWe need volunteers and will stoop to bribing with food : )
#14:44:10bshumTreats are nice.
#14:44:24bshumjenny++ #for report on reports
#14:44:34bshumNext up: 8. Developer report
#14:46:15dbsI guess I can say some stuff
#14:46:22dbsGoogle Summer of Code has attracted a fair bit of attention from potential students, a number of applications have been submitted; still one week to go before application period closes
#14:46:50dbsLots of focus on bug fixes for 2.0; 2.0.5 should be out soon with even more fixes. Many thanks to those sites who are helping find and report those problems.
#14:47:21dbsLots of progress on 2.1 release; a beta should be available soon. Some great enhancements in areas like circulation rules thanks to the likes of tsbere
#14:47:22phasefxlots of goodness from MassLNC merged into rel_2_1
#14:47:35dbsAye, many thanks MassLNC
#14:47:57dbsmulti-item sets and the like, looking forward to digging into that
#14:48:20eeeviland soon, hopefully before the next tech preview, some nrcan lovin'
#14:48:36dbsIt's been heartening to see so many bug reports (and bug fixes!) coming in, along with patches for new features; our little dev/QA team is growing up (*sniff*)
#14:48:55rsoulliereDevelopers++
#14:48:57dbsContinuous integration server (http://testing.evergreen-ils.org) is at stage 1 - runs basic tests with every commit to the OpenSRF and Evergreen repositories, but needs to be given more intelligent tests to run to be truly useful
#14:49:13dbsIntelligent test-writers welcome :)
#14:49:24dbsAnything else, dev peeps?
#14:49:32eeevilwhich, btw, dbs has been adding (js testing ftw)
#14:50:21dbsAny questions for the dev team?
#14:51:00afterlWhat's the mention of the multi-item sets?
#14:51:28eeevilafterl: monograph parts
#14:51:32eeevil(aka)
#14:52:15dbsdescription at the top of http://svn.open-ils.org/trac/ILS/changeset/19884
#14:52:16eeevile-readers, dvd sets, encyclopedias, front-to-back multilanguage stuff
#14:52:31eeevilwait, ignore me
#14:52:40eeevilthat's the nrcan lovin'
#14:52:43dbsheh
#14:52:49eeevil(I blame the pain killers)
#14:52:59dbs curiously needs some pain killers
#14:53:01eeevilbut, monograph parts was correct ;)
#14:53:12afterlI'll take the description provided by dbs
#14:53:14afterlfor the notes
#14:53:22afterlthanks
#14:53:27dbs(which was provided by eeevil, so it's all good)
#14:53:34bshumOkay, next to last agenda item then? 9. Governance Committee report
#14:53:42eeevil(pre pain killers ;) )
#14:54:29afterldbs?
#14:54:41dbsafterl: oh, are we going to do this dance again? :)
#14:54:48afterlyup!
#14:54:56afterlyou're so good at this
#14:55:02dbshttp://list.georgialibraries.org/pipermail/evergreen-governance-l/2011-March/000412.html is probably a good thing to point people to in general
#14:55:04afterlyou should just own it by now
#14:56:16dbsWe still need to send our list of Governance Board people to the Software Freedom Conservancy and dot some i's / cross some t's to complete the Fiscal Sponsorship Agreement with them
#14:56:36dbsbut in theory that shouldn't take much more effort
#14:57:19dbsAnd the Governance Committee has agreed to adopt a basic Rules of Governance this year, and to work on refinining / extending those Rules to define an election process, etc, over the course of the coming year
#14:57:35eeevilpossible to have that in place by the conf? useful goal, even?
#14:57:50eeevil(the i dotting and t crossing, I mean)
#14:58:04dbseeevil: I believe so
#14:58:16afterlThat's our goal!
#14:59:03dbsPerhaps most important is the designated role of the Governance Committee: "The Board is the central administrative body of the Project. The Board
#14:59:03dbsis responsible for the overall policy and direction of the Project. The
#14:59:03dbsBoard does not generally implement practices, but instead relies on the
#14:59:03dbsrecognized community leadership within the Project"
#14:59:42dbsAnd the recognized community leadership in the Project is every group that's reporting at this meeting - the people actually making things happen. Huzzah!
#15:00:23dbs is feeling the lack of pain killers
#15:00:33afterlAnd there's a Governance Committee update the last morning of the conference so that people can ask their questions
#15:00:59LBAand celebrate!
#15:01:06bshumHeh
#15:01:13LBAour membership in SFC
#15:01:16bradlI don't know about you guys, but I'm just at this meeting for the hors d'oeuvres
#15:01:17afterlYes, LBA, and celebrate.
#15:01:34LBAwill we have food?
#15:01:46afterlWho said anything about food?
#15:01:47bshumOkay, sounds like governance session shouldn't be missed ;)
#15:02:00bradlI mean this IRC meeting.. oh... nevermind...
#15:02:01bshumLast agenda item before we stop (we're a little over an hour now)
#15:02:05LBAtreats courtest of bradl!
#15:02:12bshumScheduling the next meeting
#15:02:25LBA quick informational item....
#15:02:27eeevilmay I request bacon-wrapped-bacon for hors d'oeuvres?
#15:02:39phasefxalways
#15:02:42LBAeeevil++ bacon++
#15:02:47bshumOkay, LBA
#15:02:59LBAI'm working on developing a comprehensive list of Evergreen features.
#15:03:09LBAI will need help cleaning it up.
#15:03:42LBAEventually it will live on evergreen-ils somewhere in some easily updatable form (I imagine).
#15:04:00eeevilLBA++
#15:04:01LBAMy goal is to make RFP responses more manageable (or to kill RFPs entirely if possible).
#15:04:13dbsWhere each feature links to the pertinent documentation? Sounds good
#15:04:26LBAdbs lets not get ahead of ourselves
#15:04:54LBAanyway, step one is underway and we can see where it goes from there.
#15:05:18LBA is done now
#15:05:22dbs just doesn't want it to be an island
#15:05:40afterl[note to self - get lots of bacon for last day of conference]
#15:06:12LBAdbs, yes, it needs to have relations. will keep that in mind.
#15:06:27dbs heard a rumour the taps in the conf hotel dispense bacon
#15:06:56bshumSo, next meeting is the Evergreen conference. Next meeting after that to be discussed via list?
#15:07:05bshumSound good to everybody?
#15:07:08dbs+1
#15:07:09phasefxworld of difference between ILS A: Has Acquisitions! and ILS B: Has Acquisitions! links_to_details++
#15:07:13eeevil+1
#15:07:20afterlNo, next meeting is not the Evergreen conference
#15:07:29afterlmeaning - no official meeting
#15:07:51bshumRight, no official meeting, I just meant generically that a meeting of the community will occur at the conference.
#15:07:55bshum:)
#15:07:57afterlright
#15:08:05afterljust wanted to make that clear
#15:08:22bradlthere will be a meeting of the bacon lovers interest group, tho, apparently
#15:08:26bshumOkay, then with that, let's call this meeting to a close, unless there's any remaining business.
#15:08:41eeevilbradl: I think that's the real reason for the conf
#15:08:49afterlwe could go awhile on the bacon theme I th
#15:08:50afterlink
#15:08:51bradleby: ooo... devious.
#15:08:58bradloops I mean eeevil :)
#15:09:14afterlbut no, I'm done
#15:09:21bshumAlright, thanks everyone, meeting adjourned :)
#15:09:33eeevil"Open Source: it's about bacon, not freedom. DUH!"
#15:09:46bradleeevil: we *should* have called the software everbacon. drats.
#15:09:53jcpl-jasonbOr, the freedom to comsume bacon.
#15:10:09LBAcrispy or floppy?
#15:10:28moodaepo prefers smoked rabbit to bacon since it's easter season
#15:10:32eeevilLBA: crispy FOREVAR
#15:10:41LBAeeevil right on!
#15:10:59phasefxeeevil: baconaise?
#15:11:01bradl backs out of the floppy vs crispy flamewar before it begins
#15:11:26afterl[note to self - have some Canadian bacon on hand for our friends up north]
#15:12:11LBAafterl maybe its just plain "bacon" there.
#15:12:25dbsback bacon
#15:12:35afterloh, right - like French toast
#15:12:38dbsor peameal bacon
#15:12:54LBAour canadian bacon is your peameal or back bacon?
#15:13:05eeevilor "ham"
#15:13:07eeevil ducks
#15:13:17LBAeeeuuuuh
#15:13:33gmcharlteeevil: you mix bacon and duck? interesting choice
#15:13:42dbsLBA: 'tis the truth
#15:13:49eeevilgmcharlt: I mix bacon and everything
#15:13:59LBAdbs: what do you call our bacon...bacon?
#15:14:12dbsjust bacon
#15:14:17bradlfreedom bacon. hmm...
#15:14:22afterlso our bacon is the real bacon
#15:14:23jcpl-jasonbI'm guessing southern fried bacon
#15:14:27afterlinteresting
#15:14:28eeevilbradl++
#15:14:31LBAwe are agreed. bacon is bacon.
#15:14:40LBAand crispy is the ONLY way to go
#15:14:50dbs read "let's call this meeting to a close, unless there's any remaining baconness"
#15:15:03eeevildibs on the bacon cracklins
#15:15:27LBA is trying to shut up
#15:15:29eeevil stumbles off
#15:15:55gmcharltdbs: we don't adjourn meetings any more, we baconfy them
#15:16:18LBAgmcharlt: we were finally winding things to a close......
#15:16:34afterlto be continued .... we'll find some bacon in Georgia ... have a baconfeast ....
#15:16:53LBAlater all, signing out!
#15:17:26jcpl-jasonb has quit IRC
#15:17:48LBA has quit IRC
#15:19:10dbsyay. it turns out that the build slaves will automatically reconnect after the buildmaster has been down for a while
#15:19:19rsoulliereHave a great weekend everyone!
#15:19:25rsoulliere has quit IRC
#15:19:41dbsit's like somebody designed the buildbot to be a distributed system or something
#15:20:23gmcharltdbs: and more importantly, succeeded
#15:25:39afterl has left #evergreen
#15:36:37sborger has quit IRC
#15:38:47yboston has quit IRC
#16:01:27StephenGWills_ has joined #evergreen
#16:04:03StephenGWills has quit IRC
#16:04:03StephenGWills_ is now known as StephenGWills
#16:06:20lisppasteDyrcona pasted "config.create_circ_matrix_matchpoint" at http://paste.lisp.org/display/121084
#16:09:04chirag has joined #evergreen
#16:11:35phasefx<@bhaak> commit early, commit often <@bhaak> kids, that is only sound advice for programming, not for marriage! < kerio> there's no rollback in marriage, only blame
#16:14:12gdunbar has quit IRC
#16:30:27lisppasteDyrcona annotated #121084 "here's one that works." at http://paste.lisp.org/display/121084#1
#16:31:39collum has quit IRC
#16:43:59chiragneed to talk regarding gsoc?
#16:44:31dbschirag: sure, I have just a minute before I have to run
#16:45:02chiragsir i have made my application to whom should i send it to be reviwed
#16:45:21dbschirag: have you submitted the application to the Google Summer of Code site?
#16:45:31chiragnope not yet
#16:45:41dbsIf so, then it is automatically in the admin / potential mentor's queues for review
#16:46:30chiragi didnt get you?
#16:46:31dbshttp://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/faqs#student
#16:46:51dbs"If the organization you want to work with has a specific application template they would like you to use, it will be made available to you to fill in when submitting your proposal via the Google Summer of Code web app."
#16:47:42chiragokay i should make my application according to evergreen template an d send it to google....
#16:47:58chiragthere is no need of mentor review first...
#16:48:46chiragi have read that people send their application to their mentor first before sending to google
#16:49:21dbschirag: submit your application, we can comment on it and request clarification etc in google-melange.com
#16:49:27dbs has to go now, unfortunately
#16:49:48dbs has quit IRC
#16:49:48chiragokaY..thank you
#16:50:27chiragphasefx:can i talk to you?
#16:50:49phasefxchirag: I'm about to leave as well, but go ahead
#16:51:23chiragif i send my application to google ..shall i be able to make any changes after that'
#16:52:14phasefxchirag: I'm not sure, but I don't think it'
#16:52:58phasefxI don't think it'll matter if the website lets you or not.. you can volunteer information to mentors and we can ask questions if needed
#16:53:24phasefxchirag: try the #gsoc channel if you really need to know
#16:53:42chiragcan you review my application
#16:54:07chiragso that i can come to know of my errors
#16:55:20phasefxchirag: you can send it to me, but I can't promise I'll have to time to much more than skim it. You should not wait on me to submit your application to google
#16:55:57phasefxI haven't reviewed anyone else's application either, so you're not exactly losing out here
#16:56:23chiragcould you suggest me some dos and donts to get my application selected in my organisation
#16:56:43chiragyour organisation*
#16:57:25phasefxit's just like applying for a job. Don't pretend to be something you're not, be honest, and if you're not enthusiastic/interested in the work, consider going after something else
#16:58:34chiragshould i explain my project at a detailed level in my application...
#16:59:00chiragor just overview of everything i'm going to do?
#17:00:54phasefxmore details show that you've done more research, but I wouldn't expect you to have a detailed specification of work. Part of your time will be figuring out specifics
#17:01:22phasefxchirag: I must go now, do checkout the #gsoc channel if you need more advice in this regard
#17:01:37chiragokay thank you for your help
#17:01:40chirag:)
#17:03:17KingNightWolf has quit IRC
#17:06:44jenny has left #evergreen
#17:22:03LBA has joined #evergreen
#17:28:19Dyrcona has quit IRC
#17:30:25tpham has joined #evergreen
#17:34:03chirag has left #evergreen
#17:42:49pmpafk has joined #evergreen
#17:43:08pmpafk is now known as pmpcat
#17:53:41mtate has quit IRC
#18:11:34mtate has joined #evergreen
#18:18:00sgirard has quit IRC
#18:19:19sgirard has joined #evergreen
#18:19:55sgirard_ has joined #evergreen
#18:23:38sgirard has quit IRC
#18:23:38sgirard_ is now known as sgirard
#18:31:34sgirard has left #evergreen
#18:33:02suho has quit IRC
#18:36:47LBA has joined #evergreen
#22:02:26denials@later tell phasefx we actually do expect a reasonably detailed specification of work, at least in terms of scheduling and approach - per http://www.booki.cc/gsocstudentguide/_v/1.0/writing-a-proposal/
#22:02:26pinesol`denials: The operation succeeded.
#22:02:38dbs has joined #evergreen
#22:02:53denialssure, _now_ dbs shows up
#22:04:21ChanServ changes topic to "Welcome to the #Evergreen library system channel! | We are publicly logged. | Large pastes at http://paste.lisp.org/new/evergreen"
#22:04:34dbsMy work here is done.
#22:04:37dbs has quit IRC
#22:20:30pmpcat has quit IRC
#22:28:19StephenGWills has quit IRC
< Thursday, March 31st, 2011Raw Log FileSaturday, April 2nd, 2011 >