| Time |
Nick |
Message |
| 00:34 |
|
timf joined #evergreen |
| 01:26 |
|
mtj_ joined #evergreen |
| 06:07 |
|
eby_ joined #evergreen |
| 06:22 |
|
artunit_ joined #evergreen |
| 06:34 |
|
b_bonner joined #evergreen |
| 06:35 |
|
mtcarlson_away joined #evergreen |
| 06:38 |
|
linuxhiker_away joined #evergreen |
| 07:11 |
|
artunit joined #evergreen |
| 07:57 |
|
akilsdonk joined #evergreen |
| 08:14 |
|
collum joined #evergreen |
| 08:31 |
|
finnx joined #evergreen |
| 08:44 |
|
Shae joined #evergreen |
| 08:52 |
|
kbeswick joined #evergreen |
| 09:02 |
|
afterl joined #evergreen |
| 09:02 |
|
ericar joined #evergreen |
| 09:03 |
|
mmorgan joined #evergreen |
| 09:18 |
|
kbutler joined #evergreen |
| 09:18 |
|
dkyle joined #evergreen |
| 09:42 |
|
rfrasur joined #evergreen |
| 09:46 |
|
RoganH joined #evergreen |
| 09:55 |
|
yboston joined #evergreen |
| 10:01 |
|
keynote2k joined #evergreen |
| 10:15 |
|
artunit joined #evergreen |
| 10:43 |
paxed |
ffs. it seems like Koha is all about going where the going is easiest. (sorry, gmcharlt) |
| 10:44 |
RoganH |
If we're going to slag on other open source projects I have few choice comments about a well known image editor. :) |
| 10:44 |
paxed |
i could bitch about that too. |
| 10:45 |
dbs |
Poor Inkscape |
| 10:45 |
* dbs |
jests |
| 10:45 |
gmcharlt |
or we could recognize that there are different, valid development philosophies in play -- and yes, a lot of warts in most any FLOSS project -- and just pick something and send patches |
| 10:45 |
gmcharlt |
or do something else |
| 10:46 |
paxed |
i'm just looking longingly back to the translation stuff in evergreen. |
| 10:47 |
dbs |
Heh, grass is always Ever-greener :) |
| 10:48 |
gmcharlt |
until one goes back to munching on the Koha egg ;) |
| 10:48 |
RoganH |
If Koha's translation system is lacking some features and you're definitely going Koha then maybe look at enhancing those aspects? |
| 10:49 |
RoganH |
Now I'm torn, I prefer Evergreen but I do like eggs.... |
| 10:49 |
paxed |
RoganH: oh, i'm trying. |
| 10:49 |
gmcharlt |
RoganH: well, clearly you need to find a nice coniferous forest have a picnic in... and bring eggs |
| 10:49 |
RoganH |
paxed: so, has the decision been made that you're going Koha? |
| 10:50 |
paxed |
RoganH: month or two ago, yes. |
| 10:50 |
RoganH |
gmcharlt: I just had a homemade chorizo and egg burrito for breakfast but it was in my office. |
| 10:50 |
paxed |
and we should be live on Koha (according to kivilahti) within next two months. color me sceptical. |
| 10:51 |
RoganH |
paxed: I'm sure you'll find pluses and minuses to Koha versus Evergreen and the other way as well. From a management stand point I think the important thing would be to take Koha's strengths and leverage them and try to minimize the impact of any shortcomings. |
| 10:51 |
RoganH |
Same advice I'd give to any software roll out mind you. /shrug |
| 10:52 |
dbs |
FWIW, it's nice to hear _something_ positive about Evergreen's i18n support. Heh. |
| 10:53 |
|
mllewellyn joined #evergreen |
| 10:53 |
paxed |
dbs: consider how much time i spent on complaining and patching it ... |
| 10:53 |
RoganH |
I think Evergreen has a lot of virtues. It's easy to forget sometimes when you spend a lot of time trying to fix or improve things. |
| 10:54 |
dbs |
paxed++ |
| 10:54 |
RoganH |
paxed++ |
| 10:54 |
gmcharlt |
RoganH: and exactly the same thing can be said of Koha, of course |
| 10:54 |
* rfrasur |
wishes paxed could come back to the EG fold. |
| 10:54 |
|
mcooper joined #evergreen |
| 10:55 |
* dbs |
greatly admires Koha's release & QA process |
| 10:55 |
RoganH |
gmcharlt: Of course. |
| 10:55 |
paxed |
rfrasur: sorry. gotta get paid. although i'm very close to leaving our koha project for good. |
| 10:56 |
|
Sato`kun joined #evergreen |
| 10:57 |
rfrasur |
oh, I know. I'm just saying. It's a sad thing when people move (unless they suck). I have a director friend who's going to a library that's not Evergreen and that bugs me, too (even though she'll be getting 125% what she's getting paid now). |
| 11:22 |
|
BigRig joined #evergreen |
| 11:25 |
csharp |
paxed++ |
| 11:36 |
|
fparks joined #evergreen |
| 12:06 |
|
j_scott joined #evergreen |
| 12:09 |
|
sseng joined #evergreen |
| 12:12 |
|
hopkinsju joined #evergreen |
| 12:16 |
gmcharlt |
if you want to brag on Evergreen (past) to Conservancy, go here - https://docs.google.com/a/esilibrary.com/document/d/1CG1QLSLpyKU4sAcPVqWZygJgPoKlN-5f_UEKD1AE0c0/edit# |
| 12:19 |
dbs |
gmcharlt: 2012 accomplishments, am I right? |
| 12:19 |
gmcharlt |
dbs: yes -- the specific data range they're interested in is in the document |
| 12:19 |
gmcharlt |
date range, even |
| 12:23 |
dbs |
when did we start codifying release schedules, EOL, release managers, etc? Those seem like significant accomplishments in terms of a maturing project |
| 12:24 |
gmcharlt |
I do think some of those events fell into that time period |
| 12:25 |
jeff |
much of that took place at or around the 2012 conference, iirc. |
| 12:32 |
remingtron |
csharp: just looking at old bug 829630. Does that still affect you? I can't reproduce in 2.5. |
| 12:32 |
pinesol_green |
Launchpad bug 829630 in Evergreen 2.4 "Holding maintenance bug when going from Item Status > View In Catalog > Holding Maintenance" (affected: 4, heat: 24) [Medium,Triaged] https://launchpad.net/bugs/829630 |
| 12:37 |
|
hopkinsju joined #evergreen |
| 12:45 |
|
sseng joined #evergreen |
| 12:46 |
|
jeff__ joined #evergreen |
| 12:47 |
|
senator joined #evergreen |
| 12:48 |
kmlussier |
Heads up. Web team meeting's going to start in about 10 minutes. |
| 12:49 |
bshum |
gmcharlt: RoganH: Just a minor question, but you guys tweaked something in the current Wordpress template right? CSS stuff or something |
| 12:49 |
bshum |
I'm making a short list of things we've tweaked (my major pain point is the heavily customized footer bits) |
| 12:49 |
gmcharlt |
bshum: IIRC, yeah -- changing the link colors, I think |
| 12:49 |
bshum |
I think we need to note those so that we don't screw up things too much between upgrades to the template. |
| 12:49 |
bshum |
I'm not 100% sure how to keep them around without trampling yet. |
| 12:50 |
bshum |
gmcharlt: That was it. |
| 12:50 |
bshum |
I had that vague memory, but couldn't drag it out |
| 12:50 |
gmcharlt |
bshum: make the WP content and theme directories Git repos? |
| 12:51 |
|
akilsdonk joined #evergreen |
| 12:52 |
dbs |
put the web site in git? |
| 12:52 |
dbs |
:) |
| 12:52 |
RoganH |
bshum: yes, link colors |
| 12:53 |
RoganH |
bshum: I didn't change the CSS directly though but included it in the Wordpress template settings that override the CSS |
| 12:54 |
RoganH |
bshum: otherwise theme updates would over write them |
| 12:54 |
bshum |
Ah, yeah, I see that. |
| 12:54 |
bshum |
RoganH++ |
| 12:55 |
|
ElliotFriend joined #evergreen |
| 12:56 |
|
CarrieC joined #evergreen |
| 12:56 |
bshum |
I guess I just need to make sure I come up with a smarter approach to the footers then. |
| 12:56 |
bshum |
Thanks guys. |
| 12:56 |
|
smyers_ joined #evergreen |
| 12:59 |
|
akilsdonk_ joined #evergreen |
| 13:00 |
kmlussier |
OK, let's get started. |
| 13:00 |
kmlussier |
#startmeeting 2014-01-16 Web Team meeting |
| 13:00 |
pinesol_green |
Meeting started Thu Jan 16 13:00:56 2014 US/Eastern. The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 13:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 13:00 |
pinesol_green |
The meeting name has been set to '2014_01_16_web_team_meeting' |
| 13:01 |
kmlussier |
#info Agenda is available at http://evergreen-ils.org/dokuwiki/doku.php?id=webteam:meetings:agenda:2014-01-16 |
| 13:01 |
kmlussier |
#topic Introductions |
| 13:01 |
kmlussier |
Please introduce yourselves with the #info command |
| 13:01 |
bshum |
#info bshum = Ben Shum, Bibliomation |
| 13:01 |
kmlussier |
#info kmlussier = Kathy Lussier, MassLNC |
| 13:01 |
RoganH |
#info RoganH = Rogan Hamby, SCLENDS |
| 13:02 |
CarrieC |
#info Carriec=Carrie Curie, PALS |
| 13:02 |
ElliotFriend |
#info ElliotFriend = Elliot Voris, St. Louis Christian College |
| 13:02 |
kbutler |
#info kbutler = Kate Butler, Rodgers Memorial Library |
| 13:03 |
kmlussier |
OK, others can introduce themselves as they wander in. |
| 13:03 |
kmlussier |
#topic Action items from the last meeting |
| 13:03 |
kmlussier |
#info graced to update the downloads page to look like her mock-ups. |
| 13:04 |
kmlussier |
According to Grace's e-mail, she was waiting to hear if there was any feedback on Alexey's e-mail. |
| 13:04 |
kmlussier |
#link http://list.evergreen-ils.org/pipermail/evergreen-web-team/2013-December/000455.html |
| 13:04 |
|
mrpeters left #evergreen |
| 13:04 |
CarrieC |
Alexey is not able to be here, either |
| 13:06 |
kmlussier |
Does anybody have any general feedback on whether graced should proceed as planned? Or should I just push for feedback on the webteam list? |
| 13:07 |
bshum |
I don't have any new ideas at the moment. |
| 13:07 |
bshum |
So I guess I'd be curious to get more feedback on the lists. |
| 13:08 |
* kmlussier |
will try to solicit feedback on the lists and come up with some of my own feedback too. |
| 13:08 |
bshum |
(I actually don't remember reading this email at all, so I have to re-read and get the attachment viewed) |
| 13:08 |
|
snowball joined #evergreen |
| 13:08 |
kmlussier |
#action kmlussier will push for feedback on the lists for new ideas on downloads page so that graced can proceed. |
| 13:09 |
kmlussier |
#info kmlussier to explore options for the “Learn More” buttons on the Evergreen home page. |
| 13:09 |
kmlussier |
I won't be able to get to this until after the conference. |
| 13:09 |
kmlussier |
If anyone else wants to look into it, I welcome the help. Otherwise, it will have to wait. |
| 13:10 |
RoganH |
I think it's fine waiting. |
| 13:10 |
kmlussier |
#action kmlussier to look into options for the "Learn More" buttons post-conference. |
| 13:11 |
ericar |
#info ericar = Erica Rohlfs, Equinox |
| 13:11 |
kmlussier |
#info gvitez to create page on logistics for setting up a mini-conference. |
| 13:11 |
kmlussier |
It sounds like gvitez will be unable to participate in web team meetings until July, but it will be a nice project waiting for her when she returns. |
| 13:11 |
kmlussier |
Best of luck to her in getting her MLIS! |
| 13:12 |
kmlussier |
#action graced and kmlussier to work on wiki page to track development projects that are part of active RFP's as well as projects seeking funding partners. |
| 13:12 |
kmlussier |
I've been waiting on working on that action item until I"m done working on some upcoming dev projects MassLNC will be funding. |
| 13:12 |
kmlussier |
Should be done by the next meeting. |
| 13:12 |
kmlussier |
#info RoganH to start listserv discussion about expanding the idea of Google document to track web site needs. |
| 13:13 |
RoganH |
Well, I sent out two pieces of communication since the last meeting. |
| 13:13 |
RoganH |
One, discussed the different forms of collaboration we could use and another this week summarizing and looking for more input. |
| 13:13 |
RoganH |
The only feedback I got gave positive input to using a help desk approach. |
| 13:14 |
RoganH |
But there doesn't seem a consensus as to what. The two products suggested are respectively project management and collaboration tools. |
| 13:14 |
RoganH |
I don't think either quite matches what we need to let people grab tasks, prioritize them, etc... without a lot of overhead. |
| 13:15 |
kmlussier |
RoganH: You thought http://osticket.com/ might work, right? |
| 13:15 |
RoganH |
I've been looking at one called OS Ticket right now. It's an open source product and seems robust. But, do we want another piece of infrastructure? |
| 13:15 |
|
montgoc1 joined #evergreen |
| 13:15 |
RoganH |
kmlussier: you typed faster than me :) |
| 13:15 |
RoganH |
Right now I'm feeling fairly warm and fuzzy towards it. |
| 13:15 |
kmlussier |
No, you typed 5 lines before I was able to type that one. :) |
| 13:15 |
bshum |
Fwiw, I'm not a huge fan of osticket. |
| 13:16 |
bshum |
And as for adding yet another piece to the infrastructure, I'm more than skeptical. |
| 13:16 |
RoganH |
bshum: I take it you've used it. What were it's drawbacks? |
| 13:16 |
ElliotFriend |
The more accounts, passwords, and infrastructure there is, the higher the bar seems to be for new participants, it seems. |
| 13:16 |
bshum |
Unless someone really champions whatever you're using and takes ownership, I don't think it's a good idea. |
| 13:16 |
kmlussier |
The alternative to adding another piece of infrastructure is to use existing infrastructure (Launchpad) to support web team needs. |
| 13:16 |
RoganH |
The barrier for entry for new people on the web team is pretty high right now since they don't know how to get tasks as well. |
| 13:16 |
kmlussier |
Do we really want to go there/ |
| 13:17 |
bshum |
RoganH: Officially, it functions, unofficially, I just never liked how the code was put together. It was a dead project for awhile, but since has revitalized somewhat. |
| 13:17 |
RoganH |
bshum: We use it York county and find it robust for our help desk needs though I admit they are pretty straight forward. |
| 13:18 |
RoganH |
I haven't had those issues but we may be doing different things in that regard. |
| 13:19 |
RoganH |
Well, our fall back if we don't do a help desk, which on list the only responses were positive to, is launchpad or Google Doc. |
| 13:19 |
bshum |
I'm not opposed to adopting that solution if that's what's desired. I'm just going to politely decline being the admin responsible for maintaining it. :) |
| 13:19 |
ElliotFriend |
I think the Google Doc that I saw a little while back did a pretty good job at letting people know what needs to be done, and letting them claim that |
| 13:19 |
ElliotFriend |
simple, straight-forward, and accessible |
| 13:20 |
kmlussier |
I woudl be happy with using the Google Doc for now. Most people have used Google docs and should be able to dive right in. |
| 13:20 |
ElliotFriend |
Although, a wiki page could do the same thing |
| 13:20 |
RoganH |
ElliotFriend: it has some distinct limitations which we ran into even for the few tasks we were using it for, that's the challenge with using collaboration tools for task management but folks can decide to live with that |
| 13:20 |
kmlussier |
RoganH: What were some of the limitations? |
| 13:20 |
kbutler |
a spreadsheet might be better than a straight up doc |
| 13:21 |
|
StephenGWills joined #evergreen |
| 13:22 |
ElliotFriend |
kbutler+ |
| 13:22 |
RoganH |
kmlussier: its hard to articulate but where people were adding on top of each other ran into some confusion especially when things were closing out as replies instead of closing task since the collaboration assumed it was resolved when it wasn't |
| 13:22 |
RoganH |
kbutler: it might |
| 13:23 |
kmlussier |
For some reason, I remembered it being in a spreadsheet. Yes, Google spreadsheet is what I meant. |
| 13:23 |
kmlussier |
kbutler++ |
| 13:24 |
|
keynote2k left #evergreen |
| 13:24 |
kmlussier |
Would somebody be willing to set up a Google spreadsheet to track tasks? |
| 13:24 |
kmlussier |
And let's see how it goes? |
| 13:25 |
|
remingtron_ joined #evergreen |
| 13:25 |
ElliotFriend |
I'm willing to volunteer |
| 13:25 |
kmlussier |
ElliotFriend++ |
| 13:25 |
kmlussier |
Is there any information you need to help you get started? |
| 13:26 |
ElliotFriend |
I'm just not sure what info would be needed for each task... |
| 13:26 |
kbutler |
ElliotFriend++ |
| 13:26 |
ElliotFriend |
date reported, task, assignee, comments, what else? |
| 13:26 |
ElliotFriend |
due date? |
| 13:26 |
kmlussier |
Status |
| 13:27 |
ElliotFriend |
Alright, I'll flesh it out and report back how things are going |
| 13:27 |
kmlussier |
#action ElliotFriend to set up Google spreadsheet to track web site tasks. |
| 13:27 |
ElliotFriend |
I'm sure as I get going, required "fields" will become more obvious |
| 13:28 |
|
jeff_ joined #evergreen |
| 13:28 |
|
jeff_ joined #evergreen |
| 13:28 |
kmlussier |
The last action item was for me to send out earlier meeting reminders. Which I did for once. |
| 13:28 |
kmlussier |
One successfully completed action item for me. |
| 13:28 |
kmlussier |
Let's move on. |
| 13:29 |
kmlussier |
#topic Evergreen library directory/map |
| 13:29 |
kmlussier |
#link http://markmail.org/message/wbnartqe63vxxpdb |
| 13:29 |
kmlussier |
So this question came up at last month's EOB meeting and then in a subsequent discussion. |
| 13:30 |
kmlussier |
We've often talked about a way to better handle the listing of Evergreen libraries. And people are interested in bringing the Evergreen map back. |
| 13:30 |
kmlussier |
Creating an Evergreen map is a lot of work, so I think it would be best if it could be generated from some kind of directory. |
| 13:30 |
kmlussier |
As I mentioned in that e-mail thread, I did find several directory plugins for Wordpress that work with Google maps. |
| 13:31 |
kmlussier |
But it's tricky, because we really need some kind of hierarchy built into the directory. |
| 13:31 |
kmlussier |
I think we would want consortia to be listed in the directory, with the individual libraries listed for each consortium. |
| 13:32 |
kmlussier |
But the consortia should also be listed alongside those single planting libraries. |
| 13:32 |
kmlussier |
Is there any interest to look into this further? |
| 13:33 |
ericar |
I've received quite a number of responses so far to that email. I think that I have added/edited all who responded. I have been trying to list out the branches, in anticipation for the structure you mention.A few people wrote me about their desire to see the EG map, but no bites on volunteering to help with it. |
| 13:33 |
kmlussier |
ericar++ |
| 13:33 |
StephenGWills |
still interested…but still busy :( I did this for EIFL a few years ago. |
| 13:33 |
|
pmurray joined #evergreen |
| 13:33 |
|
pmurray joined #evergreen |
| 13:33 |
kmlussier |
Thanks for taking on the task of updating the wiki page. It was long overdue. |
| 13:33 |
bshum |
Indeed, ericar++ |
| 13:34 |
jeff |
The subject interests me. What kind of timeline do people have in mind? |
| 13:34 |
bshum |
jeff: Sometime between now and whenever? :) |
| 13:34 |
kmlussier |
What is this thing you call a timeline? |
| 13:34 |
RoganH |
timeline-- |
| 13:35 |
kmlussier |
Seriously, though, I think just having somebody who is interested in pursuing it and also has the time to do it is a big step in the right direction. |
| 13:35 |
StephenGWills |
I was planning on being in the GIT session at the conf and hoped to learn then how to interact with our wp? |
| 13:35 |
kmlussier |
StephenGWills: I don't think you need to know GIT to interact with our wp. |
| 13:35 |
* rfrasur |
listens |
| 13:36 |
kmlussier |
jeff: Would you be willing to explore what options are availlable in WordPress and report back at the next web team meeting? |
| 13:36 |
StephenGWills |
no? i assumed we did. |
| 13:36 |
kmlussier |
As a first step. |
| 13:36 |
jeff |
It interests me enough to make time. I'll make some inquiries here to ensure that there's no conflict. |
| 13:36 |
jeff |
kmlussier: Are web team meetings usually monthly? |
| 13:37 |
kmlussier |
jeff: Yes. Execept when I fall down on the job. |
| 13:37 |
* dbs |
notes that with the auto-generated libraries page branch, we would not be far off from requiring only a URL for a live installation to get all of the addresses of every branch, as well as the current version of evergreen being run |
| 13:38 |
jeff |
dbs: That kind of thing is indeed what I had in mind. Are you interested in collaborating? :-) |
| 13:38 |
dbs |
(apologies for jumping in) |
| 13:38 |
* bshum |
rubs his hands evil-like, "yes, dbs, yes...." |
| 13:38 |
dbs |
jeff: sure. even with you! |
| 13:38 |
* RoganH |
thinks bshum needs a monocle and persian cat. |
| 13:38 |
kmlussier |
OK, I smell an action item. |
| 13:39 |
kmlussier |
#action jeff and dbs to collaborate on ways to generate an Evergreen libraries directory. |
| 13:39 |
kmlussier |
jeff++ dbs++ |
| 13:39 |
kmlussier |
You guys are awesome! |
| 13:39 |
ericar |
So, should I stop updating the roster on the wiki then? |
| 13:39 |
dbs |
Standard disclaimer applies: karma increment us _after_ we deliver something |
| 13:39 |
kmlussier |
Anything else before we move on to the next agenda item? |
| 13:40 |
dbs |
ericar: keep it going until we have something, please :) |
| 13:40 |
kmlussier |
Agreed. Especially since we didn't set a timeline. :) |
| 13:40 |
kmlussier |
#topic Evergreen conference pages |
| 13:41 |
|
ktomita joined #evergreen |
| 13:41 |
|
montgoc1 joined #evergreen |
| 13:41 |
kmlussier |
A while back when we first talked about moving the 2014 conference page to the community web site, there was a suggestion to move previous conferences to the community web site as well. |
| 13:41 |
kmlussier |
I'm not sure how to do this, but I think it's a good thing if we can do this. |
| 13:42 |
kmlussier |
Do others think it's a good thing? If so, is there anyone with the interest, time and ability to move things over. |
| 13:42 |
ElliotFriend |
Does some kind of page already exist somewhere for the previous conferences? On the wiki? |
| 13:43 |
kbutler |
I agree with moving it there. It's a shame to let that info disappear. |
| 13:43 |
CarrieC |
some are on the wiki, others a conference sites hosted by one of the hosts |
| 13:43 |
kmlussier |
ElliotFriend: They each maintained an independent site. |
| 13:43 |
kmlussier |
But there are wiki pages with links to handouts. |
| 13:43 |
CarrieC |
and some of the old sites are gone, now |
| 13:44 |
ElliotFriend |
How long have conferences been going on? |
| 13:44 |
CarrieC |
2009 |
| 13:44 |
kmlussier |
Yes, most conference hosts eventually decide to let the domain lapse. Moving the content to the community site would guarantee that the content sticks around. |
| 13:45 |
kmlussier |
At this time, the only existing sites I'm aware of are from the conferences in Decatur and Vancouver. But I think a backup was made of Indianapolis? |
| 13:46 |
kmlussier |
I can also put an e-mail out to the list for further discussion. |
| 13:46 |
ericar |
FWIW, I still think the wiki is clunky for this information. Also, Vancouver conference is not on the wiki. |
| 13:46 |
kbutler |
Would we want to do anything in particular to the info as we move it, or just basically replicate it on the community website? |
| 13:47 |
kmlussier |
I think the most important info to maintain is the handouts/presentations. If that's all we can do. |
| 13:47 |
kmlussier |
As a current organizer, it's also useful to maintain all that other information because you like to see what other conferences have done. But it's not as necessary. |
| 13:48 |
CarrieC |
this is what Yamil Suarez did for 2012 on the EG wiki: http://wiki.evergreen-ils.org/doku.php?id=conference:2012 |
| 13:48 |
ElliotFriend |
I would think replicating it as closely as we can would be a good goal, being some years removed from the actual event |
| 13:48 |
kmlussier |
#link http://wiki.evergreen-ils.org/doku.php?id=conference:2012 |
| 13:48 |
dbs |
Doesn't have to be a wiki, necessarily; could be an rsynced section of the website with static pages or WARC if you want to go crazy :) |
| 13:49 |
kmlussier |
OK, we need to wrap up soon, so I'm going to bring this discussiong to the list. |
| 13:50 |
kmlussier |
#action kmlussier to stat discussion to the list on web site from previous eg conferences. |
| 13:50 |
kmlussier |
FWW, I'm willing to serve as a web team liaison for the next planning time to make sure they have everything they need to use the community web site for the next conference. |
| 13:50 |
kmlussier |
s/time/team |
| 13:51 |
kmlussier |
#topic Web team facilitator |
| 13:51 |
kmlussier |
At the last eg conference, I volunteered to serve as the meeting facilitator to help smooth the transition after our previous fearless leader moved on. |
| 13:52 |
kmlussier |
However, I dont' think I'll be able to continue in this role. At the 2014 conference, I'm hoping we might be able to find somebody else to facilitate the meetings. |
| 13:52 |
kmlussier |
So I"m just putting the idea out there now so that people can start thinking about the possiblity of taking on this role. |
| 13:53 |
kmlussier |
Maybe we can have a small meeting at the conference and elect somebody there. :) |
| 13:54 |
kmlussier |
#help Need to find a volunteer to lead webteam meetings starting in April 2014. |
| 13:54 |
kmlussier |
Anything else before we wrap up? |
| 13:54 |
|
abneiman joined #evergreen |
| 13:54 |
kmlussier |
#endmeeting |
| 13:54 |
pinesol_green |
Meeting ended Thu Jan 16 13:54:42 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 13:54 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-01-16-13.00.html |
| 13:54 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-01-16-13.00.txt |
| 13:54 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-01-16-13.00.log.html |
| 13:54 |
jeff |
kmlussier++ |
| 13:54 |
bshum |
kmlussier++ |
| 13:54 |
ElliotFriend |
kmlussier++ |
| 13:55 |
CarrieC |
kmlussier: ++ |
| 13:55 |
kbutler |
kmlussier++ |
| 13:55 |
|
CarrieC left #evergreen |
| 13:58 |
|
EMckinney joined #evergreen |
| 13:58 |
|
jwoodard joined #evergreen |
| 13:58 |
|
EMckinney joined #evergreen |
| 13:58 |
|
jwoodard joined #evergreen |
| 14:00 |
jeff |
man, my action items : lines spoken ratio was really high in that meeting. ;-) |
| 14:00 |
bshum |
Heh |
| 14:01 |
|
benhyman joined #evergreen |
| 14:01 |
gmcharlt |
and, we're off |
| 14:01 |
gmcharlt |
#startmeeting Evergreen Oversight Board meeting, 16 January 2014 |
| 14:01 |
pinesol_green |
Meeting started Thu Jan 16 14:01:38 2014 US/Eastern. The chair is gmcharlt. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:01 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic. |
| 14:01 |
pinesol_green |
The meeting name has been set to 'evergreen_oversight_board_meeting__16_january_2014' |
| 14:01 |
gmcharlt |
#info Agenda is at http://evergreen-ils.org/dokuwiki/doku.php?id=governance:minutes:2014-1-16 |
| 14:02 |
gmcharlt |
#topic Role call of EOB members |
| 14:02 |
yboston |
#info ysboston - Yamil Suarez - Berklee College of Music (EOB) |
| 14:02 |
gmcharlt |
#info gmcharlt = Galen Charlton, ESI |
| 14:02 |
montgoc1 |
#info montgoc1 = Chauncey Montgomery, Consortium of Ohio Libraries |
| 14:02 |
benhyman |
#info benhyman= Ben Hyman, BC Libraries Co-op (Sitka) |
| 14:03 |
abneiman |
#info abneiman = Andrea Buntz Neiman, Kent County Public Library |
| 14:03 |
kmlussier |
#info kmlussier = Kathy Lussier, MassLNC |
| 14:03 |
afterl |
#info afterl = Amy Terlaga, Bibliomation (guest) |
| 14:03 |
dbwells |
#info dbwells = Dan Wells, Hekman Library (guest) |
| 14:04 |
StephenGWills |
#info StephenGWills, Maine Balsam Libraries |
| 14:04 |
EMckinney |
#Info Emckinney =Elizabeth McKinney |
| 14:05 |
gmcharlt |
OK, we have a quorum |
| 14:05 |
gmcharlt |
RoganH told me that he'll be joining presently |
| 14:06 |
gmcharlt |
#topic Financial report |
| 14:07 |
gmcharlt |
numbers to come (I'm dealing with a change of the computer I use to generate the summary), but changes have mostly been conference registrations |
| 14:07 |
gmcharlt |
#topic Evergreen 2.6 Release Manager's update |
| 14:07 |
gmcharlt |
dbwells: you have the floor |
| 14:07 |
dbwells |
#info Evergreen 2.6 is still in the early stages, but that ends soon. |
| 14:07 |
dbwells |
#info Today is the recommended last day to target bugs for inclusion in 2.6.0-alpha1. |
| 14:08 |
dbwells |
#info Next Tuesday will be the actual cutoff for committing to master for the 2.6.0-alpha1 release. |
| 14:08 |
dbwells |
#info Beta is planned for early Feb., so we should have a substantially better idea of the shape of 2.6 by the next board meeting. |
| 14:09 |
dbwells |
Any questions? |
| 14:09 |
yboston |
none from me, thanks for the update |
| 14:10 |
gmcharlt |
dbwells++ |
| 14:10 |
gmcharlt |
#topic Evergreen 2014 Conference Committee Report |
| 14:10 |
gmcharlt |
kmlussier and afterl: you have the floor |
| 14:10 |
kmlussier |
#info Registrations need to be in today to get the Early Bird discount. |
| 14:10 |
kmlussier |
afterl and I have been in the customary panic over registrations and hotel bookings that have plagued conference organizers for eternity, but the registrations are looking good. |
| 14:10 |
kmlussier |
#info We have 132 total registrations. |
| 14:11 |
kmlussier |
#info 110 are full registrations, 16 are one-day registrations and six are complimentary ones that came with sponsorships. |
| 14:11 |
pinesol_green |
[evergreen|Lebbeous Fogle-Weekley] In prereq installer, don't try to chown extracted files to original UID/GID - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d774778> |
| 14:11 |
kmlussier |
Speaking of sponsorships, do you want to talk about those now afterl? |
| 14:11 |
afterl |
Sure |
| 14:11 |
afterl |
Sponsorships are looking much better |
| 14:12 |
afterl |
We are almost to the figure that we budgeted to |
| 14:12 |
|
elmckinney joined #evergreen |
| 14:12 |
afterl |
We have three Platinum sponsorships now! |
| 14:12 |
afterl |
I am working with a few vendors now - they look promising |
| 14:12 |
afterl |
So we are in good shape with sponsorships |
| 14:12 |
kmlussier |
#link http://evergreen-ils.org/conference/eg14/eg14-sponsors/ |
| 14:13 |
afterl |
I can also talk about exhibitors |
| 14:13 |
afterl |
If now is the time |
| 14:13 |
kmlussier |
Sure |
| 14:13 |
gmcharlt |
sure |
| 14:13 |
afterl |
We have 10 confirmed exhibitors |
| 14:13 |
afterl |
The hotel can handle 12 |
| 14:13 |
afterl |
So we are almost at capacity with exhibitors |
| 14:13 |
afterl |
So we are in good shape there, too! |
| 14:14 |
gmcharlt |
afterl++ |
| 14:14 |
gmcharlt |
kmlussier++ |
| 14:14 |
kmlussier |
I think the one thing we are concerned about are hotel bookings. |
| 14:14 |
RoganH |
#info RoganH = Rogan Hamby, SCLENDS |
| 14:14 |
afterl |
Yes, that's right |
| 14:14 |
RoganH |
afterl++ |
| 14:14 |
RoganH |
kmlussier++ |
| 14:14 |
montgoc1 |
What are the bookings at this point? |
| 14:14 |
kmlussier |
We are asking people to either book hotel now, or, if they can't, to just let us know their plans so that we can figure out if we need to trim the room block. |
| 14:15 |
yboston |
afterl++ |
| 14:15 |
yboston |
kmlussier++ |
| 14:15 |
afterl |
The thought is to try to work with the hotel sooner rather than later if we need to let rooms go |
| 14:15 |
kmlussier |
As of yesterday, we had sold 165 room blocks. |
| 14:16 |
montgoc1 |
And how many are blocked? |
| 14:16 |
kmlussier |
We need 340 |
| 14:17 |
kmlussier |
The room block is higher, but we needed to commit to 80% |
| 14:17 |
montgoc1 |
Like conference registrations, is it typical to see rooms increase as you draw closer to the event? I know that our library still hasn't booked two rooms but we are still working out travel. |
| 14:17 |
|
sborger joined #evergreen |
| 14:17 |
kmlussier |
montgoc1: That's what I've head, but we really need to hear from people soon even if they don't book yet. |
| 14:17 |
kmlussier |
Sorry, heard, not head |
| 14:17 |
|
sborger joined #evergreen |
| 14:18 |
montgoc1 |
OK |
| 14:18 |
montgoc1 |
Have you had much response from the email you sent out? |
| 14:18 |
afterl |
A few |
| 14:18 |
kmlussier |
We're going to ask for an update tomorrow. I'm hoping we'll see a big jump. |
| 14:18 |
afterl |
Yes, a BIG jump! |
| 14:19 |
rfrasur |
Is there a notable disparity between the number of registrations and hotel bookings? |
| 14:19 |
elmckinney |
It is not like flights where you are committed to the expediture. Folks should book and cancel if their travel plans don't come through. |
| 14:19 |
montgoc1 |
Good point. |
| 14:19 |
afterl |
Yes, there is no risk with hotel until the very end |
| 14:19 |
kmlussier |
rfrasur: No, not a big one. There are a bunch of local registrations that we don't plan to see hotel bookings on. |
| 14:20 |
gmcharlt |
any other questions? |
| 14:20 |
montgoc1 |
At what point do we need to reduce the blocked number? |
| 14:20 |
kmlussier |
We're asking for the update tomorrow. If they still look low, I think we're going to act on it immediately. |
| 14:21 |
kmlussier |
The longer we wait, the less negotiating power we have. |
| 14:21 |
afterl |
Yes, immediately |
| 14:21 |
montgoc1 |
OK. Did that email just go to registrants or to the general listserv; I'm sorry I forget? |
| 14:21 |
afterl |
We singled people out |
| 14:21 |
elmckinney |
What is the price without our group discount. THe hotel is a bit pricey, so maybe the thought of paying the higher rate would motivate folks. |
| 14:21 |
montgoc1 |
Would sending out a general email explaining the situation help any? |
| 14:22 |
kmlussier |
It went out to people who hadn't booked hotels yet but had either registered for the conference or who we thought were likely to register. |
| 14:22 |
afterl |
But the blast also urged people to BOOK NOW! |
| 14:22 |
kmlussier |
elmckinney: I can check into that. Good idea. |
| 14:23 |
kmlussier |
In Boston terms, it's not pricey. But I don't expect people would know that. :) |
| 14:23 |
* rfrasur |
thought it was very reasonable. |
| 14:23 |
montgoc1 |
elmckinney: that is a good idea. |
| 14:23 |
benhyman |
Rack rate was $400 on hotels.com when I looked :) |
| 14:23 |
afterl |
Ouch. |
| 14:24 |
rfrasur |
It's a very nice hotel in a major city center. |
| 14:24 |
abneiman |
Wow, then we're getting a GREAT deal. Good idea to emphasize the comparison. |
| 14:24 |
benhyman |
what's the emoticon for exaggerated slightly? |
| 14:24 |
gmcharlt |
heh |
| 14:24 |
afterl |
kmlussier: let's come up with a plan of attack later today |
| 14:24 |
kmlussier |
Yup. |
| 14:24 |
gmcharlt |
however, I'm going to rein this in -- further suggestions can be made to afterl and kmlussier directly |
| 14:24 |
gmcharlt |
#topic Merchandising Committee |
| 14:25 |
kmlussier |
And it's hard to know if a lot came through since yesterday. Unlike conference registrations, I can't look the info up whenever I like. |
| 14:25 |
RoganH |
I haven't heard from the Conservancy yet. |
| 14:25 |
RoganH |
But we're ready to move ahead with motivated folks. |
| 14:25 |
* gmcharlt |
will reach out to Conservancy again |
| 14:26 |
RoganH |
Once we get clearance and are given the protocols we will setup the Zazzle store and get the base shirt designs out. |
| 14:26 |
RoganH |
I also have an idea for a 2014 conference shirt we are going to hash out and maybe put out a poll to the general list to vote on |
| 14:26 |
rfrasur |
RoganH++ |
| 14:26 |
RoganH |
If we do that I want to get it out early enough that folks could get the shirts shipped to them before the conference of course. |
| 14:27 |
RoganH |
That's all from me. |
| 14:27 |
yboston |
RoganH++ |
| 14:27 |
gmcharlt |
thanks, RoganH |
| 14:27 |
gmcharlt |
#topic Follow-up on resource allocator summit |
| 14:28 |
gmcharlt |
benhyman: you have the floor |
| 14:28 |
benhyman |
thanks - kmlussier is a miracle worker |
| 14:28 |
benhyman |
she's found us a great venue...wait for it... |
| 14:28 |
benhyman |
Google's Cambridge location |
| 14:29 |
elmckinney |
klussier ++ |
| 14:29 |
benhyman |
1 to 5 p.m. Tuesday, March 18, for 30 people "in the round" |
| 14:29 |
benhyman |
kmlussier++ |
| 14:30 |
benhyman |
Now that we have facilitator, venue and room size, we can proceed with invitations etc |
| 14:30 |
benhyman |
Plan to draft invitations later this month & run a draft invite list past the group also |
| 14:30 |
benhyman |
Questions? |
| 14:32 |
|
ktomita_ joined #evergreen |
| 14:32 |
gmcharlt |
thanks, benhyman and kmlussier |
| 14:33 |
gmcharlt |
#topic Code of conduct of Evergreen events |
| 14:33 |
gmcharlt |
#link http://list.evergreen-ils.org/pipermail/eg-oversight-board/2014-January/000650.html |
| 14:34 |
gmcharlt |
as I mentioned in the email, I am proposing that the Evergreen project adopt a code of conduct for events that occur under the project's aegis, e.g., conferences and hackaways |
| 14:34 |
|
sseng joined #evergreen |
| 14:34 |
RoganH |
I agree that a policy should be in place. It's something conferences and other events have had to become much more aware of in the last year. |
| 14:34 |
gmcharlt |
thankfully, to my knowledge there have been no incidents, but I feel that a code would strengthen our stance that the events, and by extension, participation in the project, is open to all |
| 14:35 |
ldwhalen |
gmcharlt++ |
| 14:35 |
pinesol_green |
[evergreen|Bill Erickson] make_release cleanup and options - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=7555477> |
| 14:35 |
RoganH |
gmcharlt: Are you proposing a specific policy at this time or a group to compose one? |
| 14:36 |
gmcharlt |
RoganH: I don't think we need to do one from scratch, there are plenty of examples |
| 14:36 |
|
sseng_ joined #evergreen |
| 14:36 |
gmcharlt |
one in particular that seems a good basis is this |
| 14:36 |
gmcharlt |
http://www.gophercon.com/code/conduct/2013/12/19/codeofconduct.html |
| 14:36 |
RoganH |
I've reviewed that one before. |
| 14:37 |
gmcharlt |
but this one http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy also has plenty of building blocks |
| 14:37 |
StephenGWills |
is this something SFC/Tony S. might already have that might extend out to us? I know you sent several examples but do they have a boilerplate for this already? |
| 14:37 |
RoganH |
I'd be prepared to vote on adopting that one as is if the motion is made. |
| 14:37 |
gmcharlt |
StephenGWills: no |
| 14:37 |
StephenGWills |
they would be involved in defending / prosecuting such a policy if the need arose, right? |
| 14:37 |
StephenGWills |
ok |
| 14:37 |
StephenGWills |
nm |
| 14:38 |
gmcharlt |
StephenGWills: if a matter were to come to litigation, it's unclear were it would stand, although I assume Conservancy would have some involvement |
| 14:38 |
RoganH |
The Gopher one shares a lot of DNA with the geekfeminism one. |
| 14:39 |
montgoc1 |
I like the simplicity of the Gopher policy. |
| 14:39 |
gmcharlt |
so any policy we adopt would need to be seen by them, I'm sure |
| 14:39 |
RoganH |
I think the critical parts are the condemnation of the activity and empowering the conference organizers to act when it occurs and outline the steps for resolution. |
| 14:40 |
abneiman |
Am I correct to assume that -- whichever language we adopt -- that this will be included as part of the registration? I.e. "By registering for this event, you agree to abide by this policy [link]" or something to that effect. |
| 14:40 |
gmcharlt |
one thing to note with the GoperCon policy is that we should ask permission from JSConf to adopt the wording in whole -- but I'm sure that that would be a formality |
| 14:40 |
RoganH |
I think with a few minor tweaks (maybe the staff shirt needs to be a staff lanyard) I like the gopher one. I think it's clear. |
| 14:41 |
gmcharlt |
abneiman: such verbiage would be a good idea, as well as making the policy prominent on the website |
| 14:41 |
kmlussier |
I like the GopherCon one too. |
| 14:42 |
kmlussier |
Should the policy extend beyond conferences? Like maybe to official Evergreen communication channels? |
| 14:42 |
gmcharlt |
can I get a sense from the EOB members who haven't spoken yet regarding their general support or concerns with the idea? |
| 14:43 |
yboston |
abneiman: I wonder if this comes too late for those that have already registered |
| 14:43 |
gmcharlt |
(before we get to specifics) |
| 14:43 |
kmlussier |
If it's adopted before the conference, we can send it in an e-mail blast to attendees. |
| 14:43 |
elmckinney |
I support the idea. No particular buy-in for any particular set of words...happy to support what the group likes. |
| 14:43 |
gmcharlt |
kmlussier: I would be in support of that; it's one of the things that the Code4Lib policy features |
| 14:43 |
yboston |
I would want there to be a policy for conference, and for community communications |
| 14:43 |
gmcharlt |
(that being applying the policy to the online communications channels as well as physical events) |
| 14:44 |
sborger |
I'm definitely supportive of the idea and prefer the gopher policy. I agree with Kathy it would be good to extend it to community communications. |
| 14:44 |
yboston |
no ready to vote on any just yet, would like to read more |
| 14:44 |
elmckinney |
Agree on extending this to community communications |
| 14:44 |
montgoc1 |
I am in support of it. I like the idea of a general policy that applies to all activity. It makes things simple. I am not sure how complicated that is to put together. |
| 14:44 |
yboston |
I wonder if we need to run this by the conservancy before any vote |
| 14:44 |
abneiman |
yboston: kmlussier: for this year I think the email blast would be sufficient; but going forward to I think it should be up-front, especially if violations result in a no-refund ejection (which I am OK with, for the record). |
| 14:45 |
gmcharlt |
yboston: we can do that |
| 14:45 |
yboston |
abneiman: I agree with expanding the policy to include non-refunds for ejection, we are on the same page |
| 14:46 |
gmcharlt |
also, of course, it should be open for broader discussion, although I hope that we can keep the period of time for drafting wording short |
| 14:49 |
gmcharlt |
how about this -- I would like to work out a version of the wording that combines the gophercon policy with text to extend it to the community discussion, and would like two or three volunteers to help with that |
| 14:49 |
gmcharlt |
once it's ready -- which should be a few days -- we can present the results to the community and Conservancy and hold a vote prior to the conference |
| 14:49 |
gmcharlt |
thoughts on this plan of action? |
| 14:50 |
elmckinney |
SOunds like a good way to move forward. |
| 14:50 |
RoganH |
I think that sounds good. |
| 14:50 |
benhyman |
gmcharlt +1 and I can volunteer |
| 14:50 |
sborger |
Agreed. |
| 14:50 |
RoganH |
I'm willing to volunteer as well. |
| 14:50 |
kmlussier |
+1 |
| 14:50 |
gmcharlt |
afterl and kmlussier -- can I ask one of you two to volunteer as well, since you'll be folks on the ground implementing any policy? |
| 14:51 |
kmlussier |
Sure. I'm willing. |
| 14:51 |
gmcharlt |
thanks |
| 14:52 |
gmcharlt |
#action Ben, Galen, Kathy, and Rogan will put together a draft of the code of conduct and publish it for community and Conservancy review |
| 14:53 |
gmcharlt |
#topic Planning EOB Elections |
| 14:53 |
gmcharlt |
#info Board elections and terms was decied at the April 2013 meeting - http://evergreen-ils.org/dokuwiki/doku.php?id=governance:minutes:2013-4-12 |
| 14:54 |
gmcharlt |
#info EOB terms and cohorts as decided at that meeting http://paste.lisp.org/display/140932 |
| 14:54 |
gmcharlt |
#info proposal to reduce the size of the EOB http://list.evergreen-ils.org/pipermail/eg-oversight-board/2014-January/000652.html |
| 14:55 |
elmckinney |
Ah, there it is. Never made it to the Rules of Governance document. |
| 14:56 |
gmcharlt |
right (and my bad) |
| 14:56 |
gmcharlt |
the upshot is that currently my board seat as well as that of Elizabeth, Stephen Elfstrand, and Stephen Wills are up for election |
| 14:57 |
gmcharlt |
and I've also proposed reducing the size of the EOB |
| 14:57 |
gmcharlt |
first, in general are folks in favor of that proposal? |
| 14:57 |
RoganH |
yes |
| 14:57 |
benhyman |
yes |
| 14:57 |
elmckinney |
Yes |
| 14:57 |
montgoc1 |
yes |
| 14:57 |
kmlussier |
yes |
| 14:58 |
abneiman |
yes |
| 14:58 |
elmckinney |
I would propose 9...3 year terms with 3 members rotating off every year. |
| 14:58 |
elmckinney |
I should say reducing it to 9 members.. |
| 14:59 |
abneiman |
I like the "neatness" of the 9 members / 3 year terms / 3 rotate off each year. |
| 15:00 |
abneiman |
Plus I feel 7 may be on the small side, in terms of diversity of opinion/representation etc. |
| 15:00 |
* StephenGWills |
in favor of a reduction and pockets the millions from my re-election campaign fund. 9 sounds good to me. |
| 15:01 |
kmlussier |
I don't know. I know I originally suggested 9 in the e-mail, but we're also a small community and it may be difficult to keep up with getting new, active members on a regular basis. |
| 15:01 |
* kmlussier |
is torn. |
| 15:01 |
gmcharlt |
I think 9 is a bit large, and prefer 7, although I certainly grant that 9 would keep the cohorts of equal size |
| 15:02 |
StephenGWills |
so would 6 |
| 15:02 |
montgoc1 |
I like 7 also. |
| 15:02 |
RoganH |
For nimbleness sake I like 7 though I recognize the argument for 9 and think it has merit. |
| 15:02 |
gmcharlt |
StephenGWills: but 6 would be a rather odd number for a board, so to speak ;) |
| 15:02 |
yboston |
I honestly don't see a problem with an 11 member board, but then again I don't facilitate these meetings and I have not been a member for that long (and have much to learn). I am leaning to not vote for the change, but I am glad that I am in the minority and that the majority want to make the board smaller. |
| 15:02 |
gmcharlt |
because of the potential need for a tiebreaker |
| 15:03 |
yboston |
Also, the board has been taking on some added responsibilities/ projects, and perhaps with the larger numbers more can be accomplished long term. Though I can see that when you have highly motivated and active members, a board of any size could still manage to move mountains |
| 15:04 |
kmlussier |
yboston: I was in charge of finding nominations last year, and I was worried at the last minute that we wouldn't have enough. So I am concerned with getting Board volunteers from year to year. |
| 15:04 |
montgoc1 |
Smaller groups tend to be more agile and engaged. Also, perhaps with smaller numbers the board would feel less obligated to take on so many responsibilities and those could be delegated to committees. |
| 15:04 |
kmlussier |
Though we did ultimately get a good slate, so it worked out in the end. |
| 15:04 |
yboston |
kmlussier: that really helps to know |
| 15:05 |
gmcharlt |
yboston: I think one of the balancing acts, though, is that we don't necessary /want/ the board to be directly doing everything, in favor of keeping community participation broad |
| 15:06 |
yboston |
gmcharlt: that makes sense |
| 15:06 |
RoganH |
And we see with things like the merchandising group that community members can do many things. |
| 15:06 |
RoganH |
Without being board members. |
| 15:08 |
gmcharlt |
since there's a majority in favor of reducing the size of the board, what I could do is to make two specific proposals |
| 15:08 |
gmcharlt |
one that reduces it to 9 |
| 15:08 |
gmcharlt |
and another that reduces to 7 |
| 15:08 |
gmcharlt |
both structured so that there are EOB elections in 2014 (i.e., not lopping off cohort C entirely) |
| 15:08 |
gmcharlt |
and we can discuss and vote over email |
| 15:09 |
gmcharlt |
as well as setting up for nominations prior to the conference |
| 15:09 |
gmcharlt |
does this sound sensible to folks? |
| 15:09 |
kmlussier |
How about if we rotate down to 9 this year, and see how we feel about it another year from now to rotate down to 7? |
| 15:09 |
kmlussier |
As another possible option. |
| 15:09 |
gmcharlt |
sure, I'm happy to add that to the list |
| 15:09 |
benhyman |
from 9->7 over 2 makes sense to me; possible with attrition? |
| 15:10 |
montgoc1 |
That seems reasonable. |
| 15:10 |
gmcharlt |
benhyman: yes; the main logistical issue is getting a volunteer to change cohorts and potentially shorten their term |
| 15:10 |
gmcharlt |
we'd have to work through the scenarios |
| 15:10 |
elmckinney |
I like kmlussier's idea. |
| 15:12 |
abneiman |
I also like kmlussier's idea -- gives us the chance to evaluate & adjust |
| 15:14 |
montgoc1 |
benhyman's idea also give us opportunity to adjust and may be more streamlined, if we choose to continue to reduce to 7. |
| 15:14 |
gmcharlt |
OK, then I' can draft a motion that calls for 11->9 in 2014, and 9->7 in 2015, with a built-in decision point for the board to confirm the 9->7 step prior to the 2015 elections |
| 15:14 |
montgoc1 |
If we decide to stay at 9, we could always revisit; otherwise, we would automatically move to 7. |
| 15:15 |
montgoc1 |
That sounds good to me. |
| 15:15 |
kmlussier |
+1 |
| 15:16 |
yboston |
+1 |
| 15:16 |
|
ningalls joined #evergreen |
| 15:17 |
RoganH |
+1 |
| 15:17 |
gmcharlt |
#action Galen to draft a motion for reducing the size of the EOB to from 11 to 7 over two years via attrition, with a built-in step for the EOB to confirm the reduction from 9 to 7. Vote on the motion to be held over email |
| 15:18 |
elmckinney |
Do we need to have a nominating committee for this year's election then? |
| 15:18 |
gmcharlt |
any final announcement before we end the meeting? |
| 15:19 |
gmcharlt |
elmckinney: yes, we'll need to get set up, since at least two position would be open for election this year |
| 15:20 |
|
ericar joined #evergreen |
| 15:21 |
gmcharlt |
but I anticipate that there shouldn't be any obstacle to getting that machinery running soon enough so that folks have enough time to nominate and vote |
| 15:21 |
gmcharlt |
thanks, everybody! |
| 15:21 |
gmcharlt |
#end_meeting |
| 15:21 |
gmcharlt |
#endmeeting |
| 15:21 |
pinesol_green |
Meeting ended Thu Jan 16 15:21:46 2014 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 15:21 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-01-16-14.01.html |
| 15:21 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-01-16-14.01.txt |
| 15:21 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2014/evergreen.2014-01-16-14.01.log.html |
| 15:22 |
kmlussier |
gmcharlt++ |
| 15:22 |
yboston |
gmcharlt++ |
| 15:22 |
StephenGWills |
gmcharlt++ |
| 15:22 |
montgoc1 |
gmcharlt++ |
| 15:25 |
pinesol_green |
[evergreen|Mike Rylander] Fix proximity adjustment calculator - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=a78bd1b> |
| 15:25 |
pinesol_green |
[evergreen|Mike Rylander] Upgrade script - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=657e7f3> |
| 15:25 |
pinesol_green |
[evergreen|Lebbeous Fogle-Weekley] Test for Mike's proximity adjustment fix two commits back - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9a010a1> |
| 15:43 |
eeevil |
calling 0852, because I'm dumb |
| 15:47 |
pinesol_green |
[evergreen|Mike Rylander] Renumbering the upgrade script - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9c7b271> |
| 15:47 |
pinesol_green |
[evergreen|Mike Rylander] Renumbering the test - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=aec65bd> |
| 15:49 |
pinesol_green |
[evergreen|Mike Rylander] And renaming the test - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=8c7731f> |
| 15:56 |
|
akilsdonk joined #evergreen |
| 15:57 |
|
mrpeters joined #evergreen |
| 16:15 |
|
sseng joined #evergreen |
| 16:34 |
|
misilot1 joined #evergreen |
| 16:56 |
|
afterl left #evergreen |
| 17:11 |
csharp |
8acd20b |
| 17:12 |
csharp |
8acd20b13fc6f70fa47113f77c2e0d9552518c18 |
| 17:12 |
bshum |
Heh |
| 17:12 |
csharp |
hmm - I want the snarfer to pick that up |
| 17:12 |
bshum |
If it's not in master |
| 17:12 |
bshum |
It won't |
| 17:12 |
bshum |
It's not tracking other repos |
| 17:13 |
senator |
tjat |
| 17:13 |
bshum |
Evergreen master and OpenSRF master that is. |
| 17:13 |
senator |
'scuse me. wrong window / finger spasm |
| 17:13 |
csharp |
dbwells: I'm trying to see what you changed in 8acd20b13fc6f70fa47113f77c2e0d9552518c18 (first commit listed in the changelog) but I don't see it in master or rel_2_5 |
| 17:13 |
* csharp |
must not know where to look |
| 17:14 |
csharp |
2.5.2 changelog, sorry |
| 17:14 |
dbwells |
csharp: man, you are on top of things |
| 17:14 |
bshum |
Must not have been pushed yet. |
| 17:15 |
|
stevenyvr joined #evergreen |
| 17:15 |
dbwells |
csharp: it's custom to 2.5.2 for now, and only exists in the tag branch which won't be pushed until tomorrow |
| 17:15 |
csharp |
upgrade window begins in 45 mins, so I hope so, bshum ;-) |
| 17:15 |
csharp |
okay - cool |
| 17:15 |
|
mmorgan left #evergreen |
| 17:15 |
csharp |
dbwells++ |
| 17:16 |
dbwells |
csharp: I'll push a user branch if you want to check it out. Hope you aren't counting on it for anything :o |
| 17:16 |
csharp |
nah - I've got my workarounds in place - I was just curious ;-) |
| 17:17 |
|
StephenGWills left #evergreen |
| 17:17 |
|
sseng joined #evergreen |
| 17:18 |
jeff |
dbwells: for bugfixes currently targeting 2.4 and 2.5, should they be targeted at 2.6 alpha also, or is that not necessary? |
| 17:19 |
dbwells |
csharp: Here you go: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbwells/rel_2_5_2 |
| 17:20 |
dbwells |
csharp: I really just consolidated those 4 upgrades into something more reasonable. Like the commit says, I don't know yet if it would fix what you were experiencing, but at least it is easier to see what is going on now. |
| 17:20 |
bshum |
jeff: fwiw, with bugfixes, I've tended not to target development stuff since it tended to get lost or get stuck open forever. |
| 17:20 |
bshum |
But I'll defer to dbwells' opinion. |
| 17:23 |
dbwells |
jeff: Yes, there is some cleanup which needs to happen, and I plan to do that tomorrow when 2.5.2 is official. As bshum says, if it has a pullrequest, I'll add milestone targetting for 2.6.0-alpha, but if not, I'll just add a series line for 2.5 (with 2.6 taking over the "master" line). |
| 17:24 |
dbwells |
Things without pullrequests will have milestones removed, unless there is obvious activity. |
| 17:25 |
|
misilot left #evergreen |
| 17:35 |
|
dcook joined #evergreen |
| 17:50 |
|
hopkinsju joined #evergreen |
| 17:51 |
hopkinsju |
jeff: csharp Good news... The problem I was having the other day after reorganizing the org tree and reverting it: We needed to 1) Run autogen (which we did of course) AND 2) restart opensrf |
| 17:52 |
hopkinsju |
jeff++ |
| 17:52 |
hopkinsju |
csharp++ |
| 17:52 |
hopkinsju |
Thanks very much for your advice. |
| 17:52 |
csharp |
hopkinsju: oh - great |
| 17:53 |
csharp |
glad it was a simple fix in the end |
| 17:53 |
csharp |
documentation++ |
| 17:53 |
hopkinsju |
We spent hours and hours trying to figure out where the permission depths were being cached or not being updated properly. We never looked outside the DB. |
| 18:23 |
|
mrpeters left #evergreen |
| 18:37 |
|
smyers_ joined #evergreen |
| 19:02 |
|
dbwells_ joined #evergreen |
| 19:03 |
|
fparks joined #evergreen |
| 19:07 |
|
ktomita joined #evergreen |
| 19:39 |
|
ktomita_ joined #evergreen |
| 20:47 |
pinesol_green |
[evergreen|Pasi Kallinen] Replace deprecated javascript escape() with encodeURIComponent() - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=0893dfd> |
| 21:03 |
* bshum |
remembers two PGCons back when he first looked at array_agg stuff with dbs |
| 21:05 |
|
tsbere_ joined #evergreen |
| 21:07 |
dbs |
heh |
| 21:07 |
dbs |
If we're looking for relatively easy performance wins... |
| 21:08 |
dbs |
(I think Conifer was running with array_agg/string_agg for the most part, but after the 2.4 upgrade some of those might have been reverted) |
| 21:13 |
bshum |
Ah, indeed. |
| 21:19 |
|
tsbere__ joined #evergreen |
| 22:32 |
* csharp |
would be interested in anything that helps performance |
| 23:10 |
jeff |
"i'm interested in all kinds of astronomy" |
| 23:20 |
bshum |
jeff++ |
| 23:20 |
bshum |
"Cute." |
| 23:24 |
csharp |
No more secrets. |
