Evergreen ILS Website

IRC log for #evergreen, 2016-07-07

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
00:56 gsams_ joined #evergreen
01:30 Mark__T joined #evergreen
06:52 agoben joined #evergreen
07:14 rjackson_isl joined #evergreen
08:19 kmlussier joined #evergreen
08:19 dteston joined #evergreen
08:19 kmlussier good morning
08:35 mmorgan joined #evergreen
08:36 mrpeters joined #evergreen
08:46 bos20k joined #evergreen
09:00 Dyrcona joined #evergreen
09:03 rhamby good morning
09:05 * tsbere appears to have what he thinks may be a supposed court summons of some kind in his email....maybe? It happens to be in a language he doesn't actually speak, so...
09:05 Dyrcona heh.
09:06 tsbere Dyrcona: For that matter, your old email account has one too.
09:06 Dyrcona :)
09:09 Dyrcona Speaking of email: I broke authentication with dovecot yesterday by installing updates and not restarting the daemon.
09:09 jvwoolf1 joined #evergreen
09:09 tsbere Yea, that can happen
09:10 Dyrcona I didn't notice there was a dovecot update, and the child being spawned for authentication refused to authenticate anyone because its version did not match that of the parent.
09:14 jwoodard joined #evergreen
09:24 collum joined #evergreen
09:24 jvwoolf1 left #evergreen
09:24 yboston joined #evergreen
09:30 maryj joined #evergreen
10:03 mmorgan1 joined #evergreen
10:06 _bott_ joined #evergreen
10:07 jvwoolf1 joined #evergreen
10:56 dbwells Has anyone here developed a query/report for unfillable holds?  I mean holds where every copy on the record has become lost/missing/discarded/etc..
11:00 Dyrcona I think MVLC has something like that.
11:00 * Dyrcona dashes off to another meeting.
11:00 dbwells I see that jeff and tsbere talked about recently here: http://irc.evergreen-ils.org/evergreen/2016-01-13
11:01 tsbere dbwells: I have queries and reports for that
11:02 tsbere dbwells: For "fully unfillable" I generally just link to the hold copy map table and filter on said table having zero rows for the hold (assuming the hold is not frozen)
11:03 tsbere dbwells: But my more complicated report also covers "only one system can fill the hold" in case that system is not currently able to fill them (say, closed for some reason)
11:04 dbwells tsbere: I'll try the hold_copy_map route and see how that goes.  Thanks for the tip.
11:05 tsbere dbwells: If you want my more complicated query I can pull it out of the report file
11:05 dbwells tsbere: Thanks for the offer, I'll let you know if I get stuck.
11:06 * dbwells hasn't had to worry too much about holds in the past
11:11 mmorgan joined #evergreen
11:36 Christineb joined #evergreen
11:39 gsams_ joined #evergreen
11:40 bos20k joined #evergreen
11:42 bmills joined #evergreen
11:43 brahmina joined #evergreen
12:13 jihpringle joined #evergreen
12:55 jlitrell joined #evergreen
14:09 sandbergja joined #evergreen
14:26 rgagnon joined #evergreen
14:34 tspindler joined #evergreen
14:36 terran joined #evergreen
14:43 rfrasur joined #evergreen
14:43 mmorgan1 joined #evergreen
14:55 tspindler The Rules of  Governance Taskforce will be meeting in 5 minutes.  I have put up a google doc with the agenda (see https://docs.google.com/document/d/11mobHbfZMQIWI​XV70QlbM7ZEL8CKO0SbOT3eJuOfmDI/edit?usp=sharing)
14:57 terran rfrasur: did you finish your meetings?
14:57 rfrasur terran, just.  getting stuff together for this one.  my brain is fried though.
14:57 jeff tspindler: got it -- or should i say, "roger"!
14:58 terran jeff: groan
14:58 * jeff grins
14:58 terran rfrasur: me too - somehow I have at least 3 more large projects on my plate  now
14:59 rfrasur I'm just not looking anymore.  This is the one.  Hopefully there are some fresher brains than us to lead this.
15:01 terran tspindler++ for wrangling
15:03 rfrasur It's 3:03.  Ready to go?
15:03 miker +1
15:03 rfrasur I'm gonna go ahead and post the text from the git repo that miker sent through the email for the conflict of interest.
15:04 rfrasur 167 Conflicts of Interest
15:04 rfrasur 168 ~~~~~~~~~~~~~~~~~~~~~
15:04 rfrasur 169
15:04 rfrasur 170 Any Board member who has a financial, personal, or official interest in, or
15:04 rfrasur 171 conflict with any matter pending before the board, of such nature that it may
15:04 rfrasur 172 prevent that member from acting on the matter in an impartial manner, shall
15:04 rfrasur 173 voluntarily refrain from voting on said matter.
15:04 rfrasur That's what's there now.
15:04 tspindler yes I'm her
15:04 tspindler here
15:05 tspindler #startmeeting  Rules of Governance Taskforce
15:05 pinesol_green Meeting started Thu Jul  7 15:05:53 2016 US/Eastern.  The chair is tspindler. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:05 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:05 pinesol_green The meeting name has been set to 'rules_of_governance_taskforce'
15:06 tspindler Please announce your attendance with info
15:06 mmorgan joined #evergreen
15:06 tspindler #info tspindler is Tim Spindler, C/W MARS
15:06 miker #info miker is Mike Rylander
15:06 collum #info collum is Garry Collum, KCPL
15:06 terran #info Terran McCanna, PINES
15:06 rfrasur #info rfrasur is Ruth Frasur, Evergreen Indiana, Hagerstown
15:06 rgagnon #info rgagnon is Ron Gagnon, NOBLE
15:06 terran sorry...
15:07 terran #info terran is Terran McCanna, PINES
15:07 tspindler here is the agenda again if you didn't see above note
15:07 tspindler https://docs.google.com/document/d/11mobHbfZMQIW​IXV70QlbM7ZEL8CKO0SbOT3eJuOfmDI/edit?usp=sharing
15:08 tspindler #topic Conflict of Interest Policy
15:08 tspindler I thought we might begin but considering what should be considerd in a policy.  Did others read what terran and/or I posted?
15:09 miker I did
15:09 tspindler One clear area for me is financial interest
15:10 rgagnon Yes (or most of it) and I think there are some good models there.
15:10 collum Yes
15:11 tspindler would you rather looking at copying an existing example or create a new one?
15:11 rgagnon Does the Conservancy have any requirements of us?  They must have one also -- do we need to use theirs?
15:11 terran There were a few concepts that I kept running across 1) disclosure of relationships, 2) board rather than individual determines potential conflict of interest, 3) inclusion of both financial and non-financial conflicts / 'perceived' conflicts
15:11 miker tspindler: to that point, the OSGeo one looks like good models for financial conflict identification
15:12 miker s/models/model/
15:12 tspindler rgagnon: i'm not sure if there is anything in addition to what is in the bylaws which rfrasur posted above
15:13 miker my understanding is that the SFC is intentionally hands-off, as long as there is something in place
15:13 tspindler #info OSGEO Policy https://wiki.osgeo.org/wiki/​Conflict_Of_Interest_Policy
15:13 rgagnon I liked that OSGeo said, not "impartial" like we have now, but "always act in the best interest of the organization".
15:14 tspindler I like the OSGEO policy because it is fairly simple and straightforward and not overly complex
15:14 collum I just looked through the SFC agreement.  I didn't see anything.
15:15 rfrasur I agree with that - fairly simple and straightforward.  As well as the comment that "impartial" is not the best wording.
15:15 terran The SFC has one for their own staff: https://gitorious.org/conservancy/policies/c​ommits/ac5f0f5c7a7dd7ccd48fcbc6f36c83aefaa61​f5e?p=conservancy:policies.git;a=blob;f=Conf​licts/conflict-of-interest-policy.txt;h=5e7b​220ac803f3c674835a57e16b326a2e9f54ec;hb=HEAD
15:16 tspindler What does everyone think about cribbing and exisitng policy or pulling in pieces from multiple policies?
15:17 rfrasur I think I do that on a daily basis.
15:17 terran +1
15:17 tspindler The SFC policy looks pretty comprehensive
15:17 rfrasur I like the SFC policy a lot, honestly.  More than OSGEO.   It'd need tweaking, obviously.
15:18 terran Reading through the SFC one now - I like it so far
15:18 rgagnon The SFC is more complicated than I expected.
15:19 terran We could probably simplify some of it. But the types of conflicts they would face are probably very similar to ours.
15:19 miker I like the allowed-abstension to establish quarum in OSGeo, which is prohibited in the SFC one
15:19 rfrasur miker, I was just going to ask about that.
15:19 miker because our board is 1) small 2) from a small community
15:19 terran Yes, I agree
15:19 collum Me, too.
15:21 tspindler would it it make sense then for a couple people to whittle the SFC one down into something more appropriate for our board?
15:21 terran +1
15:21 rfrasur +1
15:21 miker the SFC one has a lot we don't need (PLC stuff)
15:21 rgagnon +1
15:21 collum +1
15:21 rfrasur miker, yep.  It does.  There shall be many shavings from the whittling.
15:22 miker +1 # I think I'll end up comparing the whittled version to the OSGeo one, and a couple other streamlined ones, to see if we need ALL THE WORDS ;)
15:22 tspindler I can work on this and I would suggest the goal be to retain certain components and shed others.
15:22 terran tspindler++
15:22 rfrasur tspindler++
15:23 rgagnon tspindler++
15:23 collum I have a feeling if I did the whittling, it would look a lot like the OSGeo model.
15:23 miker what they said
15:23 collum tspindler++
15:23 tspindler My intent would be to bring back a draft for review by this taskforce.  However, would someone want to work with me on this.
15:23 miker tspindler: happy to
15:24 rgagnon I'd be willing to look it over, also
15:24 tspindler #action tspindler, miker, and rgagnon will review the SFC conflict of interest policy editing it down for use by the Evergreen board
15:25 tspindler #action tspindler will present revised draft to the taskforce at the next meeting
15:25 terran One part that I think should be different is the disclosure portion - they have  their members filling out a disclosure form every 6 months, but I think it might be more useful to address disclosure at the beginning of a pertinent discussion rather than trying to track that ever-changing list
15:25 miker one point I'd like to address before we move on
15:25 miker heh ... yes, htat
15:26 miker does anyone want the EOB to maintain a standing conflict list?
15:26 tspindler #info SFC Policy at https://gitorious.org/conservancy/policies/c​ommits/ac5f0f5c7a7dd7ccd48fcbc6f36c83aefaa61​f5e?p=conservancy:policies.git;a=blob;f=Conf​licts/conflict-of-interest-policy.txt;h=5e7b​220ac803f3c674835a57e16b326a2e9f54ec;hb=HEAD
15:27 rfrasur Hmm, miker, I don't.  I agree with terran about having it at the beginning of a pertinent discussion.  I suspect having a standing conflict list would be one more thing to maintain.
15:27 tspindler I wonder if the board would signoff on agreeing to the policy at the beginning of each new year?  The C/W MARS board signs off on a conflict of interest policy at the start of the fiscal year
15:27 terran I wouldn't want to maintain it, that's for sure.
15:28 terran tspindler: I think that's a good idea.
15:28 rfrasur tspindler, that's a good idea.  If nothing else, it's either an affirmation that the existing policy is good or a reminder to do some more tweaking.
15:28 terran Another reason for disclosure at the beginning of discussions would be to have a record of it in the meeting notes.
15:28 collum terran++
15:29 tspindler our attorney suggested to be sure all members are aware of a policy
15:29 miker sure. signoff should follow the election, obv.
15:29 rgagnon We do the annual signing as well, recommended by our auditor.  It's a question on non-profit IRS Form 990 filings.
15:29 terran Perhaps sign-off at the annual meeting each year?
15:29 tspindler signoff is different than disclosures though
15:29 miker terran: if we continue with the pre-meeting elections, +1
15:29 miker from me
15:30 rgagnon Annual meeting makes sense to me.
15:30 terran tspindler: yes, was speaking of the policy sign-off
15:30 rfrasur tspindler, it is.  But I think there's the potential for conflicts to rise and fall depending on what type of discussion is being had.
15:30 tspindler ok, when we look at editing the policy we will look at one signoff a year
15:30 terran Yes - policy signoff once per year, disclosure at the start of each discussion topic
15:31 rfrasur +1
15:31 tspindler terran: got it
15:31 miker should we add a standing disclosure entry to the front of every discussion item, to remind us? once we have a policy, obv
15:31 miker as in, on the agenda
15:32 miker just a reminder for the meeting manager to say "any conflicts to disclose?"
15:32 tspindler miker: it sounds a bit overly bureaucratic but I'm open to it
15:32 collum Disclosure before a discussion or vote, or when the person feels that there is a conflict?
15:32 terran that would be a good reminder - many topics won't have anything to disclose, but it'd be a good habit to get into
15:32 rfrasur It's an important thing to the community.  I think it's a good reminder.
15:32 collum The policy right now is to refrain from voting.
15:33 tspindler ok, so do we  include the reminder language as part of the policy?
15:34 tspindler or is it going to be recommeded for the board chair?
15:34 miker tspindler: I don't think so ...
15:34 miker the latter, IMO
15:34 rfrasur I don't think so either.  Just add it to the agenda.
15:35 rfrasur Or have the board chair add it to the agenda.
15:35 tspindler #agree rfrasur
15:35 tspindler anything more than on the conflict of interest policy?
15:36 miker target date for getting a draft out to this committee? just "next meeting of this committee"?
15:36 rfrasur I think, from my standpoint, that's a really good starting point, and we'll need to wait to see the whittled and glued together draft to see if there's more work to be done on it.
15:36 terran I am happy to allow tspindler and miker to take a crack at it first
15:37 tspindler miker: i would leave it open but I think I can start looking at it in the next couple of weeks and then send a copy to you and rgagnon
15:37 miker +1
15:37 rgagnon +1
15:38 terran tspindler++ miker++ rgagnon++
15:38 tspindler ok next topic
15:38 tspindler #topic Rules of Governance
15:38 tspindler I did not have a good plan of what we wanted to do with this.  Any suggestions?
15:39 tspindler Is there anything anyone has seen in the rules that should be changed?
15:40 rfrasur Not really.  I think the biggest thing was the Conflict of Interest policy.
15:40 terran I haven't looked at it that closely yet, but there are few things that are out of date - list of board cohorts, date of next election date, date of certification
15:41 tspindler terran: would you mind going through it and identifying those areas that need updating?
15:41 tspindler at least with specifics like this?
15:41 rfrasur The only other thing would be, still, language about executive sessions, but that's something the EOB is working on.
15:41 terran tspindler: I can do that
15:42 tspindler #action terran will review rules of governance looking for things that were out of date including the list of board cohorts, date of next election, date of certification
15:42 tspindler #info official rules of governance version to use is http://git.evergreen-ils.org/?p=contrib​/governance.git;a=blob;f=governance.txt
15:43 tspindler since the EOB is looking at executive session issues we don't need to touch that
15:43 tspindler anything else?
15:44 rfrasur not from me.
15:45 terran good to me - I will read through the other sections more closely before the next meeting.
15:45 terran Sounds
15:45 collum nothing from me.
15:45 tspindler ok would you like me to send a doodle poll for the next meeting?  I would aim for about a month from now?
15:45 miker +1
15:45 rgagnon +1
15:45 rfrasur Yup, if you wouldn't mind
15:45 rfrasur +1
15:45 terran +1
15:46 collum +1
15:46 tspindler ok it looks like we can adjourn then.
15:46 terran Cheers!
15:46 tspindler #endmeeting
15:46 pinesol_green Meeting ended Thu Jul  7 15:46:47 2016 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:46 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2016/evergreen.2016-07-07-15.05.html
15:46 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2016/evergreen.2016-07-07-15.05.txt
15:46 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2016/evergreen.2016-07-07-15.05.log.html
15:46 rfrasur y'all are awesome.
15:46 miker tspindler++
15:46 tspindler first time using meetbot
15:47 collum tspindler++
15:47 rfrasur tspindler++
15:47 rgagnon tspindler++
15:47 terran tspindler++ for taming meetbot
16:13 tspindler left #evergreen
16:21 jeff git rebase reality/master
16:23 bshum fatal: Needed a single revision
16:23 bshum invalid upstream reality/master
16:29 * Dyrcona read the scroll back of the meeting.
16:34 Dyrcona bshum: git fetch reality
16:34 Dyrcona fatal: 'reality' does not appear to be a git repository
16:35 bshum Haha Dyrcona++  :)
16:38 brahmina joined #evergreen
16:38 Callender joined #evergreen
16:56 jeff huh. "adjust to zero" isn't in the web staff client that i can see.
16:57 Dyrcona Hmm. I never looked for it there.
16:58 Dyrcona Is this on your regular installation or a concerto test instance?
16:58 Dyrcona I ask because in the xul staff client whether or not the option displays is based on permissions.
16:59 * jeff nods
16:59 jeff i have the permission, i don't see the option in the web staff client, i do see the option in the xul client.
16:59 jeff i'll dig further.
17:00 Dyrcona OK.
17:00 * Dyrcona disappears in a puff of reality.
17:02 kmlussier jeff: I think you're right. I've been meaning to check into it and file a bug report, but it keeps getting buried in my to-do list.
17:02 kmlussier I say that as if I had an actual to-do list rather than a running mental tally of all the things I want to do.
17:12 mmorgan left #evergreen
17:12 jwoodard @weather
17:12 pinesol_green jwoodard: Aubrey, TX :: Clear :: 95F/35C | Heat Index: 103F/40C | Thursday: Partly cloudy and windy. Lows overnight in the upper 70s. Thursday Night: Partly cloudy. Windy this evening. Low 77F. Winds S at 20 to 30 mph.
17:14 kmlussier @weather
17:15 pinesol_green kmlussier: Seekonk, MA :: Rain :: 76F/24C | Thursday: Scattered thunderstorms. Lows overnight in the upper 60s. Thursday Night: Thunderstorms likely, especially this evening. Low 67F. Winds S at 5 to 10 mph. Chance of rain 80%.
17:15 kmlussier Ooh! Maybe I can turn off the a/c tonight.
17:21 jvwoolf1 left #evergreen
18:08 maryj joined #evergreen
22:04 gsams_ joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat