20:00:42 #startmeeting Genereal IRC meeting 9 March 2016 20:00:42 Meeting started Wed Mar 9 20:00:42 2016 UTC. The chair is cait. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:42 The meeting name has been set to 'genereal_irc_meeting_9_march_2016' 20:00:47 #topic Introductions 20:00:56 #info barton, BWS, Louisville KY, USA 20:00:57 #info Mark Tompsett 20:00:57 #info Joy Nelson, ByWater Solutions 20:00:59 please introduce yourself using #info 20:01:00 #info Mirko Tietgen, Berlin, Germany 20:01:04 .. and where is wahanui? 20:01:18 #info Katrin Fischer, BSZ, Germany 20:01:24 #info Brendan Gallagher, ByWater 20:01:25 today's agenda is 20:01:27 #link https://wiki.koha-community.org/wiki/General_IRC_meeting_9_March_2016 20:01:29 #info Bob Birchall, Calyx, Sydney Australia 20:01:30 #info Thomas Dukleth, Agogme, New York City 20:01:52 #info Giannis Kourmoulis, AUTh, Thessaloniki, Greece 20:02:18 ok, let's move on in a moment 20:02:19 #info Galen Charlton, ESI, USA 20:02:28 ... or two 20:02:44 ok, moving on 20:02:48 #topic Announcement 20:02:52 hm...s 20:03:01 #info Andreas Hedström Mace, Stockholm Univ 20:03:17 bag? 20:03:23 #info Chris Cormack, Catalyst 20:03:31 RM update 20:03:43 Goal one is to maintain a low PQA queue - so daily attention 20:03:56 I am learning tons! Constantly adjusting my workflow. I know there are some things I've missed so making sure that the workflow adjusts to not miss things 20:04:26 I was under the wrong assumption with packages (my mistake) and have adjusted my workflow. 20:04:26 I understand that it shouldn't be all new packages will be created and I need to do a better job of checking if they are in debian already and if not - start a discussion for alternative methods. I will be seeking help on any that come up until I feel I've mastered that part. 20:04:41 Again I am learning :) 20:05:11 * bag prepared his notes ahead of time (so it’s copy and paste) I’ll slow down to give everyone a chance to read 20:05:24 Schema updates. I know there are a few problems there - khall and I will be working on that to fix those. That has been the second weakest part of my workflow and I'm adjusting that and getting better. 20:05:45 As always - please don't hesitate to talk to me - point out anything you think I am missing. 20:05:46 Elastic search branch - is currently being rebased on master by rangi (there is a change in the Koha::ItemType that needs to be adjusted) Once that is caught up - I will add a weekly rebase to that on master until we are able to move that forward into Koha. 20:05:49 thank you rangi 20:06:01 bout halfway there 20:06:12 sweet 20:06:26 joubu also expressed desire to work on ES too, so you might want to touch base with him 20:06:48 yes his patch needs rebase (looking for number one sec) 20:07:12 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14899 20:07:12 04Bug 14899: enhancement, P5 - low, ---, jonathan.druart, Needs Signoff , Mapping configuration page for Elastic search 20:07:21 #info Elastic search branch is being rebased 20:07:51 #info Problems with Schema updates are being worked on 20:09:29 anything else? 20:09:31 That’s it from me - unless anyone has any questions 20:09:46 oh, I just finished the rebase :) 20:09:49 So your first comment was like about URL::Encode and the like? 20:10:29 ? 20:10:40 bag: Is the koha Debian repository still working for serving packages? 20:10:45 #info Elastic search rebase --- done 20:11:21 or is URL::Encode in Debian, but not currently in Koha? ... nevermnd. 20:11:21 yes URL::Encode - there is a suggestion on how to work with packages that are already in koha (I posted the comment to the bug) 20:11:50 * mtompset nods. 20:12:18 mtompset: hm tried to install it on Ubuntu - but didn't find it 20:12:30 i think there might be ways around using that specific one? 20:12:37 that’s a good example of a place that I need to communicate a bit more :) 20:12:45 added that to my workflow 20:12:45 #info Nicole Engard, ByWater 20:12:53 Which is what bag was getting at, I think. :) 20:13:02 yes URL::Encode is not in debian 20:14:06 ok cait - I think we are ready to move on 20:14:10 ok 20:14:23 #topic Update on Releases 20:15:19 bag again? ;) 20:15:30 or one of the rmaints? 20:15:38 jajm, fredericd ? 20:16:18 ok 20:16:20 movin gon then again 20:16:26 #topic GBSD 20:16:46 I was thinking... i tmight be time for another GBSD 20:17:04 If people share that opinion, the next question would be about a possible date 20:17:07 yay! 20:17:10 some people prefer a Friday 20:17:24 friday for you is saturday for me 20:17:37 in theory, gbsd starts your friday 20:17:53 yep, but i wont be updating the scoreboard etc on the saturday is all im saying 20:17:58 yeah true 20:18:05 so thatwould be an argument for maybe use another day 20:18:27 also one of the next fridays is a public holiday in lots of countries 20:19:19 maybe a thursday? 20:19:40 24th? 20:20:16 do i need to bribe the audience with cookies? :) 20:20:29 heh 20:20:34 Cookies over IRC? 20:20:40 any day with sufficient warning is ok for me 20:20:52 be nice to make it a biggish one, and do a blog post about it 20:20:53 gmcharlt: no calories:) 20:21:00 good point :) 20:21:07 24th looks good 20:21:50 so quiet... 20:22:09 i#d add a page tothe wiki and send an email about it 20:22:21 thanks 20:22:26 24th is fine 20:22:36 i hope everyone quiet doesn't mean i will be the only one present ;) 20:22:41 its the day before Easter 20:22:45 ah 20:22:51 here friday is the holiday 20:22:59 cait -- not to worry :-) 20:23:00 here too 20:23:01 BobB: so better the week after? 20:23:12 so is that good or bad? 20:23:24 i though that would be good 20:23:31 i'm not sure what affect it would have 20:23:37 less clients to urgently deal with ;) 20:23:48 but week after is ok 20:23:58 more time to promote it maybe 20:24:04 the weekafter a friday would work i think 20:24:19 april 1st? 20:24:32 might just be dangerous becauseof the jokes :) 20:24:38 didn't we just say friday is bad? 20:24:39 :) 20:24:41 I thought we said no fridays. 20:24:43 maybe i am not following 20:24:49 Thu 31 is ok 20:24:49 cait: I couldn't think of a better time... 20:24:49 aaahsorry 20:24:50 it's me 20:24:52 i liked the 24th 20:24:59 i'll do my own then 20:25:17 drojf++ # for wanting to do his own GBSD. 20:25:25 ok, quick vote? thursday 31st or thursday 24th 20:25:28 will be a challenge to get me global :D 20:25:32 and then i will moveon to the next topic, promise :) 20:25:48 drojf: Do it for 48 hours straight no sleep, then it is global. ;) 20:26:00 31 20:26:02 i am too old for that :) 20:26:05 24 20:26:06 I'm for 31. :) 20:26:14 24 20:26:23 * gmcharlt makes note to self - write script to automatically lock out a BZ account if it has been continuously used for more than 12 hours ;) 20:26:34 24 20:26:53 * gmcharlt is neutral on 24/31 20:26:59 neutral too 20:27:08 ... and then follow drojf's lead on the 31st, if that's better. 20:27:26 barton: is that a 31 or 24 for you? 20:27:34 i'm prolly neutral too 20:27:35 Ooooo... back to back GBSD's. 20:27:39 you people make it hard tocount :) 20:27:51 ok, 31 20:27:52 cait: 24 20:27:54 ok 20:28:08 #agreed next GBSD to be on March 24th 20:28:11 barton you cancelled my vote :) 20:28:17 #action cait to send an e-mail about GBSD 20:28:47 #topic Discussion on proposing a new version numbering for Koha 20:28:48 Wait... it looked like a tie. 20:28:51 that was long to type... 20:29:05 that was me that added that to the agenda 20:29:10 everyone who voted needs to signoff at least 3 patches 20:29:14 20:29:24 i think it was 3-2 20:29:25 +1 to that. :) 20:29:30 #info everyone who voted needs to signoff at least 3 patches 20:29:54 fence-sitters need to do 6 for being indecisive ;) 20:29:54 Oh you are right. 20:29:59 and everyone who voted has to signoff one crypto patch 20:30:00 heh 20:30:07 I’d like to propose that the next release of koha be - 16.05 20:30:12 * mtompset cheers, "Here! Here! gmcharlt!" 20:30:19 koha has been on 3.x for about 6 years now 20:30:26 that sounds ugly 20:30:28 or, looks 20:30:50 i like the date based idea 20:30:53 you mean as in the year/month? 20:30:53 following a yy.mm numbering going forward 20:30:54 i like that 20:30:54 and it lacks chocolate/cookie related stuff 20:31:00 there is that... 20:31:14 it has a big advantage of people seeing they are on the 12.05 release 20:31:33 yes indded 20:31:33 #info Suggestion: use a data based versioning for next release - 16.05 20:31:45 drojf: they can still have code names too ;) 20:31:54 will make it a lot easier to tell them just how old it really is :) 20:32:02 YES! 20:32:05 the numbering has caused problems for us - when we’ve been behind a release or two - and the bug says pushed to master 20:32:06 yeah, at the moment i have to go look it up ;) 20:32:26 i like the date based too, because you can immediately see how ancient your version is (well, you can't if you stay on 308 forever). i only don't like 16, i think. don't take it too seriously 20:32:27 bag: hm but why is that a problem with the numbering? 20:32:33 we'd still have master :) 20:33:03 ah yes - but I changed the message in the pushed to master - it now says the time of when it *should* be in the release 20:33:04 drojf: you have an aversion against the number 16? 20:33:23 16.05 The source awakens 20:33:24 i am 16 dysphoric, or what kids call it these days 20:33:46 17.11 looks cool on the other hand 20:34:04 So... what is expected to be 3.24.0 is going to be 16.05.0? 20:34:10 yes it does more so than 3.30 20:34:21 yes mtompset 20:34:29 And each month 16.mm? 20:34:30 no 3.33? :( 20:34:33 :P 20:34:50 What about oldstable? 16.05.{revision}? 20:34:50 * gmcharlt has no object to 16.05 (and I've double-checked that it won't cause any problems with Debian package version number comparisons) 20:34:54 *objection 20:35:04 mtompset: only every 6 months 20:35:05 will it be 16.05.1 or 16.06 then in the next month? 20:35:17 drojf: .01 i think 20:35:19 i'd prefer the first i think 20:35:22 ok so I presented the idea. I was thinking we’d get it out there and then maybe vote at the next meeting 20:35:27 16.05.01 20:35:33 rangi: the other way is probably too confusing 20:35:39 yeah 20:35:50 with several supported branches and stuff 20:35:52 #info bugfix releases would be numbered 16.05.1 ... 20:35:57 might I suggest that (at least this time around) we make the vote itself be strictly yes/no? 20:36:06 gmcharlt++ 20:36:06 +1 20:36:26 So, yy.mm(of release).{realease number}? 20:36:31 i.e., choice between 16.05.x or 3.24.x, but intentionally *not* opening floor to alternatives 20:36:37 ah 20:36:48 i guess that would make things a lot easier 20:36:56 yes 20:37:14 Yes, stop 3.x branch. Yes, yy.mm use. 20:37:24 my proposal is a little selfish, to be clear: I have a strong aversion to version numbering debates :) 20:37:26 Still need clarification of intermediate fixes. 20:37:50 gmcharlt: yes lets get it over with as long as it seems we agree 20:38:04 or we spend months inventing other schemes 20:38:28 http://knowyourmeme.com/memes/darth-vaders-noooooooooooo 20:38:51 ok vote now - or this motion passes for the next agenda “choice between 16.05.x or 3.24.x, but intentionally *not* opening floor to alternatives” 20:39:01 bag: Would there be a single for a nonstable build? 20:39:19 s/single/signifier/ 20:39:51 hm 20:40:04 17.00 / 17.06, perhaps 20:40:07 so the vote could just be as simple as "switch to 16.05 style numberin? yes/no" 20:40:12 That's the part that confused me too, thd. 20:40:35 gmcharlt: why 00 06? 20:40:37 sorry,not getting it 20:40:55 right now even stable, odd unstable. 20:40:58 16.05 == May release; 16.00 == stuff prior to May, i.e., unstable 20:41:03 i'd say thats a detail that can easily be decided on once we vote for the general change 20:41:04 cait 00 is after 11 20:41:14 ahh.. there gmcharlt said it better 20:41:20 gmcharlt: we have two 16 releases and need to prior-versions 20:41:32 ahok 20:41:33 sorry:) 20:41:45 drojf: right - 16.00 (unstable) 16.05 (stable) 16.06 (unstable again) 16.11 (stable) 20:41:48 i'd say 16.04, 16.05 and 16.10 and 16.11. or whatever else 20:41:57 #info unstable /in development could be 17.00 / 17.06 20:41:58 ok that is kind of the same in reverse 20:42:00 but more broadly, I agree with drojf that that's a detail we can punt on 20:42:09 i'd say let the RM decide 20:42:16 we can call it spaghetti if we want for unstable 20:42:19 Additionally, if an actual release date slips a little does it signify the wrong thing in versioning or would date use be fudged for an easily understood convention not strictly tied to date? 20:42:25 no one except us devs should be using it 20:42:30 so its just an internal thing 20:42:35 rangi: one would hope, anyway ;) 20:42:43 let's be hopeful :) 20:42:47 lets call it dont_use_this.1 20:42:49 lets call it dont_use_this.2 20:42:50 etc :) 20:43:02 lets not make that nice and simple vote boring and complicated 20:43:03 rangi: this_has_literal_c4_in_it.1... 20:43:04 16.spagetti? 20:43:06 ok 20:43:12 but really the external facing number is the important one 20:43:15 so we are going to have a yes/no vote next meeting? 20:43:23 ooo... 16.spaghetti. 20:43:25 yes 20:43:27 can't we have it now? 20:43:39 I like that... yy.{whatever signifier we agree on} 20:43:56 I’m fine with voting now - the only complaint is I added this to the agenda yesterday 20:44:00 yeah 20:44:07 that'smy only complaint too 20:44:11 lets vote now and give the world a chance to debate it next time. and i will accidentally miss the meeting :P 20:44:22 :) 20:44:45 its not like we have millions of people at the meetings, and it seems we basically agree atm 20:44:46 vote now, and call it a straw poll if there are serious objections aftwaards? 20:44:49 drojf: As bag rightly proposed in proposing the form of the issue that we should wait to consider further. 20:44:52 drojf: is that accidentally or 'accidentally' ? 20:44:52 ok 20:45:15 barton: either one or the other, whatever happens first :P 20:45:19 So, please restate what is to be voted on. 20:45:19 ok, can someone phrase a yes/no question for me? 20:45:40 how about this... 20:45:42 not sure why I amalways strugglingwith this 20:46:26 Shall the next major Koha release change the version scheme to yy.mm.minor, e.g., 16.05? 20:46:41 Would we be punting the fine details for further consideration of any actual implementation of the concept in any case? 20:46:43 #startvote Shall the next major Koha release change the version scheme to yy.mm.minor, e.g., 16.05? (yes,no) 20:46:43 Begin voting on: Shall the next major Koha release change the version scheme to yy.mm.minor, e.g., 16.05? Valid vote options are , yes, no, . 20:46:43 Vote using '#vote OPTION'. Only your last vote counts. 20:47:05 obviously... , should not be an option 20:47:05 #vote yes 20:47:07 #vote yes 20:47:08 #vote yes 20:47:09 #vote yes 20:47:10 yes 20:47:12 #vote yes 20:47:13 #vote yes 20:47:14 #vote yes 20:47:14 damn 20:47:17 #vote yes 20:47:17 heh 20:47:17 #vote yes 20:47:22 * mtompset laughs at drojf 20:47:32 i was too excited :D 20:47:34 Does anyone say no or abstain? 20:47:36 * talljoy hands drojf a cookie 20:47:42 awww thanks talljoy 20:47:45 nah, drojf was just agreeing with cait's statement that ... isn't a valid choice! ;) 20:48:14 #vote yes 20:48:21 gmcharlt: yeah i was reading that, wondering what it was about and tried to vote at the same time :) 20:48:22 i meant the comma :) 20:48:36 ok, closing voooote 20:48:43 #endvote 20:48:43 Voted on "Shall the next major Koha release change the version scheme to yy.mm.minor, e.g., 16.05?" Results are 20:48:43 yes (10): cait, mtompset, BobB, bag, gmcharlt, talljoy, thd, drojf, rangi, ikourmou 20:49:14 #agreed Koha's release version scheme will be changed to be date based, e.g. 16.05 20:49:20 moving on? 20:49:23 i doubt there will be 11 people here next time that hate the idea 20:49:30 moving on 20:49:31 probably unlikely 20:49:34 :) 20:49:41 #topic Hackfest in Berlin 20:49:52 YES WE WILL MOVE ON, HAVING UNLOCK THE ACHIVEMENT OF A VERSION NUMBER CONVENTION DISCUSSION THAT WAS ACTUALLY BRIEF!!!!1!!!! 20:49:53 ;) 20:49:59 im still waiting for work to OK me to go 20:50:05 (I may be a little excited about that outcome) 20:50:21 gmcharlt: I too am in shock. 20:50:22 rangi: yay :) 20:50:25 * talljoy expected the earth to shake 20:50:41 drojf? 20:50:42 not really anything new from me… 20:50:59 liw will get back to me in april about a debian packaging workshop 20:51:03 #link https://wiki.koha-community.org/wiki/Berlin_Hackfest_2016 20:51:13 I’ll be heavy asleep on the 27th of may so I won’t be able to be there - but see you in greece 20:51:15 so far very little people registered, namely cait ;) 20:51:29 #info there will be a Catmandu workshop 20:51:34 so we would have one workshop per person 20:51:36 :P 20:51:43 drojf: because youneed help advertising obviously 20:52:33 i dont know if people fixed their plans for greece already, so its hard to tell if there is more to come 20:53:14 i will appoach german libraries that may be interested at some point if there is very little response from koha devs 20:53:39 bye 20:54:01 i think ther would be some interest here 20:54:10 but it has not been advertised to the german lists so far 20:54:30 so it would be helpful to know if peopke made their plans already. rome was full within 3 or 4 weeks 20:54:33 its hard to tell 20:54:34 would so like to come, its just not possible 20:55:34 ok, moving on? 20:55:54 cait: it has not been advertised there because all german devs are already coming :P 20:56:03 ah not quite true 20:56:19 also, hackfests can help make new devs 20:56:32 #topic KohaCon 20:56:37 let's start with Greece 20:56:41 thx for the patience ikourmou 20:56:49 ok, no prob 20:56:58 let me give some numbers first 20:57:08 about 135 registrations already 20:57:22 w00t 20:57:25 awesome 20:57:27 Nice. 20:57:30 yay! 20:57:36 and more than 25 proposals for presentations 20:57:57 the call for proposals has ended on 7th of March 20:58:03 :D 20:58:09 cool 25 is a good number! 20:58:26 so now we have to form the program committee that will evaluate the proposals 20:59:06 we plan to invite some of you (eg koha elders) to form the committee... 20:59:06 nice 20:59:42 we also have opened the "call for sponsorships" 20:59:59 http://kohacon2016.lib.auth.gr/?page_id=462 21:00:13 #link http://kohacon2016.lib.auth.gr/?page_id=462 21:00:20 #info Call for sponsorships is open 21:00:22 I would say that in general everything goes as planned 21:00:28 #info 135 registrations so far 21:00:40 #info 25 proposals for presentations 21:00:59 ikourmou: the updates on the conf page are nice! 21:01:07 but I would really love to have some feedback from the people here 21:01:14 cait: thx 21:01:59 the venue we have booked has about 175 seats 21:02:18 so we are approaching a limit 21:02:26 sooner more than later 21:02:33 with 135 already… that may be full soon 21:02:39 175 is a good number 21:02:55 what was the biggest kohacon so far? reno? 21:03:00 * cait is glad she has registered already 21:03:08 drojf: that or the first one in paris 21:03:29 ikourou: Is 175 merely a seating limit or also a legal/safety limit for the venue? 21:03:39 * rangi will register .. I may have to try and seek some sponsorship to come though, but ill register 21:03:43 no, just seating 21:04:22 we could expand it by projecting the presentations in the foyer (just a thought) 21:04:30 ok so we can squeeze 200 in probably? i suppose not everyone is attending all sessions 21:04:59 Stamding room Koha :) 21:05:18 live bloggers get seats... rest standing or on the floor? ;) 21:05:47 ok, we will work sth out, if we reach the limit :-) 21:06:04 136 21:06:08 :) 21:06:28 thx @rangi 21:06:33 ikourmou: i saw you have several rooms there 21:06:45 but that would probably be way more expensive too 21:07:00 you mean the building kohacon is gonna take place? 21:07:02 and/or bookes for other stuff 21:07:04 yes 21:07:08 *booked 21:07:31 yes, they will be probalby booked by then... 21:07:55 are you planning on streaming video or audioi? 21:08:02 that was in the flyer too ;) 21:08:23 maybe we can talk more about dealing with 'more' once we reach it? 21:08:35 we still have some topics to deal with 21:08:36 +1 21:08:47 I would like to ask if there are any special considerations for the hackfest? 21:08:47 ikourmou: anything you need us to do/decide/volunteer? 21:08:53 wifi 21:09:09 checked! 21:09:09 good internet 21:09:15 :) 21:09:31 enough power outlets, tables... maybe a projector if that would not be too hard 21:09:43 do we need to define sessions or subjects or anything? 21:09:53 I encourage recording hackfest presentations for sharing with the world not attending in person. 21:10:01 not really, unless you got a lot of proposals for dev-only events 21:10:43 how do hackfest presentations work? 21:10:47 ikourmou: apart from providing the mentioned things,things usually get organized by the people attending - similar to marseille 21:10:57 ah, ok 21:11:10 i think liw would also be up for a debian packaging workshop in greece if its possible to decide in april. he just could not hand in a proposal now 21:11:19 ikourmou: its more like an unconference, the people there on any given day decide what they will work on 21:11:35 Hackfest presentations may be very informal explanations or discussions of some technical matters. 21:11:53 @rangi: that makes thing easier for us 21:11:53 ikourmou: I'll give you the answer as soon as RDA is ready 21:12:26 we plan to have streaming for the whole Kohacon 21:13:04 * pianohacker is better nate than lever 21:13:06 cool. and fair enough for people not registering in time 21:13:08 ikourmou: Will you be recording the stream for later access? 21:13:27 not sure if you are a better nate pianohacker 21:13:38 #info plan is to have straming for the whole KohaCon 21:13:58 yes, we have some considerations on video size though 21:14:06 s/later/non-realtime/ 21:14:13 you should get consent to have all talks licensed CC or similar 21:14:34 ok, if there is nothing mor urgent 21:14:35 drojf: noted 21:14:36 i'd like to move on 21:14:46 just one more thing... 21:14:58 we plan to propose the formation of Greek Koha Users Group 21:15:03 cool 21:15:07 :) 21:15:07 cool 21:15:16 that's all from me 21:15:23 ikourmou++ 21:15:24 :) 21:15:31 ok 21:15:40 for KohaCon bids we currently have one from Dublin, Ireland 21:15:50 and one from the Philippines 21:16:11 I think Dublin might be out, because of the not twice in the same continent? 21:16:16 2 europe in a row 21:16:19 not really something to discuss the next few months, is itr? 21:16:23 ah yes that 21:16:44 i did not write that on the list, because the rules are not clear 21:16:49 not sure how to handle that 21:16:59 according to the rules we should be in NZ every 5 years 21:17:02 i think it's noted somewher on the wiki at least? 21:17:06 which would be cool :P 21:17:26 Where are these rules? 21:17:29 heh, yeah 10 is more practical, id like to bid for wellington 2020 21:17:36 there is a note, but its not a rule, just vague stuff someone noted (at least that is how it sounds) 21:17:45 I sort more feel - if you want to volunteer to host - volunteer - more power to you 21:18:07 so maybe we should really set it as a rule 21:18:09 populous regions will always win it that way 21:18:18 yeah 21:18:21 lots of options here in europe 21:18:41 would be nice to bring it to Asia again 21:18:42 and we'd never end up with places like nigeria, which would be really unfortunate 21:18:44 we could probably get you kohacons in europe for the next 5 or 10 years 21:18:52 i think the beauty of kohacon is it moves around 21:18:55 everyone gets a shot 21:18:56 yes 21:19:04 so lets make it a real rule 21:19:22 +1 to making it a real rule. :) 21:19:26 no harm in having bids that dont fit, those are people that may bid again the following year 21:19:36 but i like the way it was done so far 21:19:54 dublin tried to bid last year, btw. they were a day late 21:20:14 hope they won't be disappointed 21:20:14 not sure if that was public, i think they only send it to me 21:20:30 but better to know earlier than later 21:20:43 well, it is a nice reminder of being actually active in the community you are trying to host a conference for 21:20:53 we don’t seem to get flooded with propsals 21:20:58 The potential issue may have been mentioned in the text of recent calls for proposals on the koha mailing list. 21:21:07 it took nigeria 3 years to win 21:21:37 yeah and they kept trying till they did 21:21:40 there is precedence for it taking time 21:21:42 rangi: and the help of that rule. which is why i thin we should have it/keep it/make it a real rule written down somewhere 21:22:02 paris, edinburgh, greece 21:22:06 because locations too far fro the US and EU will have no chance otherwise 21:22:06 ok, so what is the next step here? 21:22:07 reno, plano 21:22:36 are the 2 continents that have had it more than once 21:23:55 versus wellington, mumbai, cordoba, ibadan - so far 5 in EU / US and four outside 21:23:58 cait: 1) vote on it as a rule, not only a guide or whatever it was so far 2) communicate it to dublin and in calls for hosts in genberal 21:24:11 pretty good balance, so what we've done seems to work :) 21:24:13 ok, vote now or next meeting? 21:24:40 I think we could vote on the continent rule being explicit and written. 21:24:44 i'd say vote now, but i think its a bigger issue than version numbering, so maybe an announcement would be fair 21:25:01 True enough. 21:25:06 How would the rule be formed to prevent alternating between North America and Europe? 21:25:21 it hink we sould not overcomplicate 21:25:33 not the same continent twice in a row? 21:25:42 thd: its not twice within 3 years 21:25:44 thd: that would be a different rule 21:25:45 ah 21:25:49 thats always been the guideline 21:25:55 rangi++ 21:26:08 that'd mean that dublin could be 2018 earliest? 21:26:12 i never heard of that 21:26:20 is that in the wiki too? 21:26:41 who knows, we have ruled out bids using that before though 21:26:53 i haven't :) 21:26:59 rotate from E to W? :) 21:27:01 i think 21:27:26 BobB i think we do not have enough options to have a fixed rule for that? 21:27:30 drojf: It has only been a guideline to follow for avoiding dominance by population which was discussed somewhat a few years ago. 21:27:56 it came in after the thousand of votes for kohacon11 21:28:08 we'd be in india every year otherwise 21:28:13 none of whom came to the conference 21:28:25 rangi: As my call for proposals message has put it recently, we have never had to use such a rule in actual practise. 21:28:26 ok. good to know, i was not aware of that. 21:29:04 maybe we need to vote on this next time 21:29:14 hm yeah the voring rules for kohacon… i think its not on the agenda this time and i forgot what was last zime, but we need to think about that 21:29:42 so i will info it 21:29:44 cait we are an hour and a half into the meeting and only half way through the agenda 21:29:51 exactly 21:29:56 i dont think we can blame cait for that 21:29:57 :) 21:30:15 #info Vote on a for continent rotation for KohaCons next meeting 21:30:15 i blame l*bl*me 21:30:16 not blamin' of course, just sayin' :) 21:30:19 No one does, but it is rather long. 21:30:33 can we skip the next topic? 21:30:39 yes 21:30:39 what is the next topic 21:30:48 #topic International Koha Fund 21:31:06 drojf: skipped mailing list announcement rules. 21:31:16 bag? or me? 21:31:23 you start BobB_ 21:31:29 The vote counting issue is moot so far for the next KohaCon if we enforce some rule for venue diversity. 21:31:41 ok Fundraising committee is doing two things: 21:31:56 - about to start talking about how to raise to money; 21:32:02 ah no we skipped two, which both were mine 21:32:12 so the voting thing was on the list 21:32:12 - and making rules for the Grants committee, in case we get some money! 21:32:14 ^^ 21:32:26 drojf: sorry 21:32:50 So the draft rules for the Grants committee were put on the wiki last night 21:33:01 and are there to be read and commented on 21:33:07 and voted on next month 21:33:15 questions? 21:33:20 yes 21:33:35 #info draft rules for the Grants committee were put on the wiki and are there to be read and commented on 21:33:47 there is mentioning of a closed session. i wonder what things will be within such sessions 21:33:47 thx cait 21:34:13 url? 21:34:36 https://wiki.koha-community.org/wiki/Fundraising 21:34:43 scrool down 21:34:46 #link https://wiki.koha-community.org/wiki/Fundraising 21:34:50 scroll even 21:35:01 2b Meetings of the Committee will be scheduled with at least 2 weeks of prior notice. A public agenda will be published prior to the meeting that will list all of the proposals under consideration. The agenda will specify which portions of the meeting will be open and which will be held in closed session. 21:35:22 Ah, right in the minutes, sorry. 21:35:47 ^minutes^agenda^ 21:36:01 droif I am trying to remember 21:36:43 as I recall, it's a catch-all 21:36:43 BobB: not saying that can't be happening, just wondering what it is about, because it is not mentioned elsewhere 21:37:21 as in, anything that involves money raises the spectre of sensitive issues that should not be promulgated 21:37:37 yes, to give the ocmmittee the option of private discussion, which should be made known rather than done secretly, if you follow me 21:37:50 and the grants subcommittee is reserving the right to discuss any such matters in closed session -- but to say in advance that it woudl be doing so 21:37:54 gmcharlt well said 21:39:13 drojf: does this answr your question? 21:39:53 BobB: would you be ok with a vote in may? or is there a need to have the vote in April? 21:40:01 we could have the discussion on the mailing list 21:40:24 until there is money in the fund, there are no grants to make, so these rules are not urgent 21:40:36 yes 21:40:43 thanks 21:40:50 ah an update on the money in the fund… one sec 21:40:59 we are a little over $300 dollars in the fund and we’ve had 2 donations so far in 2016 21:41:12 nice start 21:41:19 and that is without any effort, so its good 21:41:38 #info $300 dollars in the fund, 2 donations so far in 2016 21:41:39 moving on 21:41:58 can we save the brainstorming for gbsd? :) 21:42:08 and get to set a date for the next meeting? 21:42:11 +1 21:42:33 #topic Set date and time for next meeting 21:43:01 wednesday, April 6th ? 21:43:30 10 UTC? 21:44:06 works for me 21:44:09 +1 21:44:39 that’s a difficult time to stay awake for 0200 for me 21:44:49 it's the normal rotation 21:44:55 yep thast fine 21:44:55 I know I know ;) 21:45:01 #agreed Next meeting will be on 6 April, 10 UTC 21:45:03 #endmeeting