17:56:09 #startmeeting 17:56:09 Meeting started Wed Mar 2 17:56:09 2011 UTC. The chair is Brooke_. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:56:09 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:56:20 #topic Introductions 17:56:41 paul_p, BibLibre, France 17:56:45 Haere Mai, Egondea, Welcome to #koha, please introduce yourselves as we wait for others to arrive :) 17:56:52 * gmcharlt = Galen Charlton, Equinox 17:56:54 * cait = Katrin Fischer, BSZ, Germany 17:57:00 Thomas Dukleth, Agogme, New York City 17:57:07 * jcamins = Jared Camins-Esakov, ByWater Solutions 17:57:10 chatzilla tells me we are 4 mins early ;) 17:57:11 Jane Wagner, PTFS 17:57:16 * wizzyrea liz rea, NEKLS 17:57:17 * slef = MJ Ray, CEO software.coop 17:57:19 * davi davi = worker for software.coop 17:57:19 Jesse Maseto, ByWater Solutions 17:57:21 * magnuse Magnus Enger. Libriotech, Norway 17:57:30 kmkale: I think we are early too 17:57:44 Koustubha Kale Anant Corporation, VPM, Thane, granthalaya.org 17:57:46 Brendan Gallagher ByWater Solutions 17:57:47 * sekjal is Ian Walls, ByWater Solutions 17:58:26 Sandeep Bhavsar Librarian Vidya Prasarak mandal, Thane's Dr. V N Bedekar Institute of Management Studies 17:59:15 Nate Curulla: ByWater Solutions 17:59:33 Shelley Gurney, Catalyst IT 17:59:58 * hdl Henri-Damien LAURENT, biblibre 18:00:36 welcome everyone again and now it is properly time ;) 18:00:49 #topic Roadmap to 3.2 18:01:08 so, do we have an update on the 3.2 Roadmap? 18:01:21 Do we have a chris_n? 18:01:47 chris_n++ # 3.2.4 and 3.2.5 18:02:00 chris_n++ 18:02:05 chris_n++ 18:02:08 maybe enough beeps will raise him 18:02:16 chris_n++ for timely delivery :D 18:02:28 chris_n++ 18:02:52 can we speak of a security list as 3.2.5 has been released because of a security (hacker) issue ? 18:03:00 chris_n++ for timely releases, chris_n-- for not being here or putting his report on the wiki page? 18:03:04 paul go for it 18:03:05 paul_p: I've added an item to the agenda 18:03:13 after the KohaCon 11 discussion 18:03:15 gmcharlt, sorry, missed it 18:03:23 it's not on mine either 18:03:30 paul_p: no problem, I *just* added it now 18:03:36 ah, ok ;-) 18:03:39 http://wiki.koha-community.org/wiki/General_IRC_Meeting,_2_March_2011#Agenda 18:03:47 makes more sense here, methinks. 18:03:57 #link http://wiki.koha-community.org/wiki/General_IRC_Meeting,_2_March_2011 18:03:58 Brooke_: it's not specific to 3.2 18:04:05 okily dokily. 18:04:33 shall we move on to 3.0? 18:04:36 yep 18:04:43 #topic 3.0 Roadmap 18:05:04 morning 18:05:05 I actually have an update for 3.0 - with hdl's consent, I intend to cut a security release of 3.0 18:05:14 which, IIRC, would make it 3.0.7 18:05:21 yes. 18:06:24 anything else? 18:06:24 rumour has it anything else is reinventing the wheel 18:06:31 and ... I think that's about it for an update on 3.0 18:06:42 brevity is a virtue sir 18:06:51 #topic Roadmap to 3.4 18:06:58 yes. it should be noted in the relase notes that it should be the last. 18:07:09 Chris is skived off to a cool conference 18:07:16 anyone want to sub? 18:07:20 I have something to say about 3.4 & bugzilla. 18:07:32 shoot 18:07:58 allez :D 18:08:05 #info the apologies section of the wiki page says "chris cormack will try to be there but is at a conference" 18:08:20 I did a lot of wrangling recently, and have some important numbers :85 bugs are "patch pushed" waiting for "bug closed" and 152 bugs "needs signoff" 18:08:48 What can we do to lower those numbers ? 18:09:04 hehe: test and sign off ;) 18:09:10 the more there are, the hard it is to deal with them (specially the "need sign-off") 18:09:28 hdl, yes, so I change my question = how can we motivate ppl to sign-off & close ? 18:09:46 should we organise a "wrangling day" ? should we publish a weekly summary ? 18:09:51 I think hdl is right, we need more people testing and signing-off 18:09:53 a news in the newsletter ? 18:09:55 it's probably a question of time for most of us... 18:09:55 scoreboard 18:10:04 scoreboard++ 18:10:04 #idea Wrangling Day 18:10:23 a newsletter item would make nengard happy 18:10:23 what could help would be to have some dedicated server with as many vhosts as branches 18:10:26 so I'm all for it 18:10:34 hdl: is BibLibre offering to set one up? 18:10:47 we could do that.... on the new jenkins server. 18:10:56 Problem would be the databases... 18:11:10 magnuse, yes, but once we've said it's a question of time, we have 2 options: or we *decide* to do something, each of us taking, for example 20 bugs. or we do nothing, and those numbers will continue to grow and our workflow is just a theory,... 18:11:26 magnuse++ 18:11:31 any help would be appreciated in setting that up and automating that.. 18:11:32 #help bug wranglers to address backlog 18:11:35 I don't have time, but I take time ! 18:11:45 paul_p++ 18:11:58 last night I worked up to 1AM, and signed/closed something like 20 18:12:17 (i'm not asking everybody to work up to 1AM ;-) ) 18:12:27 s/asking/suggesting/ 18:12:37 (it might help, though ;-) ) 18:12:40 I appreciate your dedication, as always Paul 18:12:57 thx Brooke_, but me alone won't be enough. 18:13:01 hdl: Do you not have appropriate test databases? 18:13:15 thd: we have for unimarc 18:13:24 I realise that, and I like the 20 per person. Do we have enough volunteers that could spare the time and technical expertise to make this happen? 18:13:26 and databases are not automated. 18:13:41 Each time I put aside time, by the point I've got myself to the point of having a current master, reminded myself how to do the signing-off and found something I could test (right MARC format, reproducible problem, and so on), I'm out of time. Why does it take so long? 18:13:42 a good, but not enough news: Julian Maurice started yesterday a 6month time with us. He's a student, and will be dedicated to signin/closing/submitting BibLibre patches. 18:13:42 with respect, it is not just a numbers game 18:13:44 And some bugs are really tightened to some systempreferences 18:13:55 the quality of the signoffs and testing also matters 18:14:13 gmcharlt++ security_bugs-- 18:14:27 gmcharlt++ 18:14:41 gmcharlt++ 18:14:41 I'd imagine that they won't necessarily break down cleanly as some would work packaged together, too 18:14:55 but someplace there needs be a line drawn if we can manage 18:14:56 would be really helpful if bug reports came with testing plans. "Here is how to confirm a fix works" 18:14:59 in terms of prioritizing, I suggest that the patches awaiting signoff should come first 18:14:59 many hands make light work. 18:15:05 I could contribute 1 hour of my time to sign some bugs more 18:15:09 I think that we need to develop some automated systems for testing so that testing becomes easier. 18:15:09 gmcharlt, double right = it also means that it takes time to signoff/close (see some bugs that i've commented "can't sign-off") 18:15:12 sekjal good idea 18:15:20 thank you davi 18:15:20 once a patch has been pushed, it has presumably been tested at least once (by the person who signed off) 18:15:29 hdl++ do we need syspref summarising in "About Koha"? 18:15:33 #idea automated testing 18:15:44 so additional testing to close the bug, while still important, is hopefully less of an issue 18:15:47 #idea testing plans in conjunction with patches 18:15:52 no Brooke_ 18:15:54 np 18:16:15 slef: i think we could adding some test plans to reproduce the bug would be helpfull... 18:16:20 another idea = having more than one setup, with various configs (like marc21/unimarc , IndependantBranches ON/OFF,...) 18:16:27 But it would add some more overhead to declare bugs. 18:16:38 I did not mean that all tests should be automated but we need to have good automation for setting up tests run by humans checking behaviour. 18:17:06 hdl: I think reporting already asks for steps to reproduce the bug 18:17:20 it does 18:17:26 paul_p++ Yes, that is what I meant. 18:17:27 I am not sure we have a technical problem 18:17:38 the easy bugs are done quickly - like interface changes 18:17:40 slef: sometimes the bug comes because of one system preference. 18:17:48 cait: agreed 18:17:49 And user are not aware of that. 18:18:07 but there are some things I have no idea about - we need people with enough knowledge looking at them 18:18:13 some bugs really need attached bib and syspref .sql files 18:18:14 can we consider that someone who declares a bug should be the one who closes it when "patch pushed" ? I could send some reminders to ppl in this situation ? 18:18:20 hdl: that's what I mean. If user could get a syspref summary code from "About Koha" to paste in the report which was useful to us that may help. 18:18:24 mtj++ 18:18:32 complex circ bugs, etc 18:18:43 slef++ a report about the reporter's config 18:18:47 would help immensely 18:18:51 * Brooke_ nods. 18:18:58 * paul_p agrees too 18:19:01 paul_p: yes, general the person who first reported a bug ought to test and close it, so reminders would be appropriate 18:19:12 I think mtj_ might be right - it would be a settings file to attach to the bug. 18:19:13 #idea add a syspref summary code from About Koha" to paste in the report which was useful to us that may help. 18:19:14 #idea enhancing About Koha to report more configuration details 18:19:18 (at least for project regulars, no need to bug somebody who just dropped by to report a bug) 18:19:21 hdl++, yes, a very nice idea to work towards 18:19:23 ok, will send reminder soon unless someone objects. 18:19:42 I am hearing no objections 18:19:44 am I right? 18:20:07 #idea paul_p will send mail reminders to ppl that have a bug where they are "reporter" that is "patch pushed, pls close" 18:20:08 #action Paul to send a reminder about bug workflow details 18:20:10 an 'about this koha' page, to attach to bug reports 18:20:27 mtj_: Some bugs definitely require much more testing work but anything we can do to make any testing easier on people with limited time should help. 18:21:20 mtj_: we already have that, don't we? 18:21:37 * paul_p will deal with biblibre ppl that are no more working at BibLibre :\ 18:21:44 (nahuel mostly) 18:22:06 Sometimes the one who report a bug do not have the expertise to test-close it 18:22:21 paul_p: is he still around (in the sense of having any interest or time to work on Koha)? 18:22:25 davi: true 18:22:49 gmcharlt: he is around on koha-fr but no longer any time to work on koha 18:22:50 gmcharlt, nope. working for a university using Koha (AixMarseille), but not on Koha at all 18:23:01 davi: perhaps, but hopefully they should at least recognize when the initial problem they reported now appears to be working 18:23:14 gmcharlt++ 18:23:15 paul_p: thanks 18:23:30 gmcharlt, working in the new release, that is to say, check close after release 18:23:43 note they can not even install a dev version maybe 18:23:56 ? 18:24:23 davi: well, then they'd have to wait until the new release to test, then 18:24:40 though that leads to a variant of one of the ideas discussed 18:24:43 It is OK to ask the reported to test, but IMHO do not set as a "have to" because some ones will not be able to 18:24:48 #idea public database that always tracks master 18:25:01 * paul_p is wondering if we should not remind ppl that there are bug to test/close in a weekly/bi-monthly email on koha-devel. 18:25:25 I feel, but i may be wrong, that many ppl could find a few minuts if they knew exactly what to do. 18:25:27 davi: hence the distinction I made between project regulars and people who submit the occassional bug report 18:25:32 paul_p: I think we are always aware of it :-/ 18:25:37 ack gmcharlt 18:26:07 slef, everybody is aware ? i'm not sure. I had Frydolin boss on phone this morning, not sure he was aware. 18:26:12 it feels like this is exhausted 18:26:30 no! we must keep our energy up to close bugs! 18:26:40 heh 18:26:41 Brooke_: oh, you meant the agenda item ;) 18:26:47 and i'm sure he could tell fridolyn to take a few hours! 18:26:58 gmcharlt, no! to what ? 18:27:11 paul_p: I think that many people would indeed take the issue seriously if all that people had to do was test and not set up and configure the system to run the test. 18:27:11 paul_p: as in "no, we must not be exhausted" ;) 18:27:36 anything else relevant to 3.4? 18:28:07 movin' on 18:28:09 Schuster - Plano ISD 18:28:11 mtj_: What did you mean by "about this Koha?" 18:28:42 #topic roles for 3.6 18:28:53 soooo 18:28:58 we've a slight problem here 18:29:02 gmcharlt, lol 18:29:06 but it's not to big to surmount. 18:29:06 I don't remember who Frydolin is. 18:29:30 Most of our slate is unopposed 18:29:38 slef, Progilone, french company that won at least 2 contracts in France 18:29:50 (Lyon2 university, Bulac university) 18:29:57 so I think that we can probably manage a blanket affirmation on those. 18:30:00 * gmcharlt proposes that we proceed with votes on RM, TM, and DM for 3.6; with +1/0/-1 for the current (sole) candiates 18:30:10 also, a bunch of the usual suspects are missing 18:30:38 so the proposed Release Manager is Chris Cormack 18:30:39 gmcharlt: and RMaint? 18:30:42 all in favour 18:30:44 #link http://wiki.koha-community.org/wiki/Roles_for_3.6 18:30:44 i think Rangi was resigned to his fate before he left 18:30:48 +1 18:30:51 slef: yes, and RMaint 18:30:53 slef, http://www.progilone.com/Templates/Koha.htm 18:31:03 +1 18:31:05 +1 18:31:07 +1 18:31:07 +1 18:31:08 +1 18:31:10 +1 18:31:14 +1 18:31:15 +1 18:31:18 +1 18:31:40 +1 18:31:51 0 18:31:57 +1 18:32:12 +1 18:32:22 +1 18:32:45 * gmcharlt further moves that we vote on sekjal's bid to be QAM 18:32:47 #agreed Chris successfully suckered into another 6 months. 18:33:01 I'm gettin' there gmcharlt. 18:33:04 that's down the line. 18:33:19 I go by the list or I git too squirrelly ;P 18:33:41 Translation Manager is proposed to be Frédéric Demians 18:33:42 Brooke_: there is a motion on the table for voting on the slate of RM, TM, DM, and RMaint 18:34:16 it might save time to vote on all of the unopposed positions 18:34:23 * slef thought "tabled" meant something different to USians 18:34:34 which is what I initially said, but I thought there was disagreement on that... 18:34:57 * paul_p was not sure to have understand, but anyway will say +1 once or 4 times. 18:34:58 slef: tabled != on the table, in US parliamentary speak 18:35:18 so how about this 18:35:23 we know chris is in 18:35:28 let's bundle the other posts 18:35:33 is everyone fine with that? 18:35:45 yep 18:35:47 gmcharlt, in france, things that are on the table is usually food :D (kidding, we also use "tabled" in the "to be discussed" too) 18:35:49 yes 18:35:54 so 18:35:59 Brooke_: I see no opposition to a blanket vote in the log 18:36:20 paul_p: ("tabled" is "postponed" to US I think) 18:36:34 i would like to propose a *new* position, some person/people to be elected as admins for the Koha lists on nabble.com 18:36:42 Frédéric Demians for Translation Manager, Nicole Engard for Documentation Manager, Ian Walls for QA, Chris Nighswonger for Release Maintainer 18:36:44 paul_p, in Spain the discussion of a subject can be on the table too 18:36:54 hang on to that idea mtj 18:37:02 I'll come back to it and if I don't yell at meh 18:37:05 *nod* 18:37:18 so all in favour of the afforementioned blanket slate 18:37:24 +1 18:37:27 +1 18:37:29 +1 18:37:35 slef: 'tabled' meaning postponed is different from 'on the table' meaning the item for current discussion. 18:37:36 0 18:37:37 0 18:37:39 +1 18:37:41 +1 18:37:43 +1 18:37:43 +1 18:37:44 +1 18:37:46 +1 18:37:50 and we have things on the table in Germany too ;) 18:37:54 +1 18:37:56 thd: not in English English 18:38:13 +1 18:38:18 +1 18:38:28 +1 18:38:31 thd: we use "shelved" for postponed instead. 18:38:50 should we vote to decide if we can use the "tabled" word ? :D :D 18:39:08 slef: Do you use 'tabled' at all? 18:39:09 paul_p: yeah and we'll lose and still get confused! 18:39:16 * gmcharlt proposes that we use whatever the French term is ;) 18:39:28 thd: yes, to describe the state of the motion on the table. 18:40:03 there's a current motion, and there are actions on the table, but not usually both at once 18:40:07 anyhoo 18:40:11 think it's safe to say 18:40:17 #agreed the motion carries 18:40:37 that leaves us with Bug Wrangler 18:40:42 and a proposal for a new slot 18:40:47 slef: What is the standard manual for parliamentary procedure in the UK? 18:40:58 looking at bugwrangler position on the wiki page, I see "to do some PR about the work done", that's what I suggested a few mn ago with my weekly mail ;-) I candidate to write this PR. You'll enjoy my english ;-) 18:40:59 I propose that both applications for Bug Wrangler be accepted 18:41:05 thd: I think the Speaker makes it up as he goes along. 18:41:14 :) 18:41:17 the more bugwrangler we have the better it is. 18:41:28 pau_p++++ 18:41:29 gmcharlt++ 18:41:31 I <3 that proposal gmcharlt 18:41:50 and I feel i've been a BW recently, event without the official position... 18:42:12 * Brooke_ notes that paul is getting dangerously close to a nomination with those words... 18:42:28 just to check, everyone has noticed my drastic WONTFIX plan? 18:42:31 im keen to be a bug-wrangler 18:42:32 * paul_p knew that and accept the position if ppl want ;-) 18:42:57 so then, I'll entertain a motion to have Marcel de Rooy, MJ Ray, and Paul Poulain as Bug Wranglers. 18:43:07 I think the more bug wranglers the better 18:43:10 slef: Would explain you won't fix plan? 18:43:11 slef: noticed, though I'd prefer that those bugs be at least glanced at individually before being marked WONTFIX 18:43:14 * gmcharlt is willing to help with that 18:43:25 I will try to spend more time on it too - after march is over 18:43:32 gmcharlt: yes, I plan to check each one. 18:43:35 slef, or there is something i'm misunderstanding, or I agree with your proposition 18:43:38 too many projects at the moment :( 18:43:44 thd: so that we can concentrate on 3.6, I'd systematically check and RESOLVE WONTFIX the ~140 bugs reported not against maintained versions and I'd suggest reclassifying the 771 bugs reported against master as reported against the version which immediately follows the date they were reported 18:43:55 Brooke_: can i be a bug-wrangler too? 18:44:03 hmmm 18:44:07 this is pretty fluid 18:44:16 what do we do with this as a group? 18:44:22 is there a formal relationship between the Bug Wranglers and the QAM? 18:44:25 should we have a wrangler of the month? 18:44:29 sometimes WONTFIX can be as a wish for future version 18:44:34 or a team with an appointed chair? 18:44:44 sekjal: I thnk that would be up to the QAM and the bug wranglers to work out 18:44:57 some bugs might be reported against older versions but still be existing on master 18:44:58 slef: I had read that but do you mean not maintained is that bugs reported against 3.0 would not be fixed if no longer maintained? 18:45:04 gmcharlt: sounds good 18:45:11 should we then allow Ian to appoint as many bug wranglers as he deems fit? 18:45:12 Brooke_, team-member of the month is only used in Mc Donalds here, so it's really not something ppl are proud to be ;-) 18:45:25 * gmcharlt is in favor of having anybody who wants to wrangle bugs to get the title of Bug Wrangler, as long as they publicly commit to put in a reasonable amount of effort to it 18:45:37 thd: yes, and all the 2.x and 1.x ones. 18:46:03 slef, i fear it will be a mountain to move ! 18:46:08 gmcharlt++ , i agree 18:46:09 that's so many !!! 18:46:14 gmcharlt++ 18:46:21 so then 18:46:24 open position 18:46:25 gmcharlt++ 18:46:32 that reports to the QA manager 18:46:41 paul_p: 140ish, plus some fraction of the 700+ bugs labelled master. 18:46:47 and receives recognition at some point that they're an official bug wrangler 18:47:05 the top wrangler can get a can of raid in the post ;) 18:47:08 slef: I assume that reporters would be notified with the suggestion that they login and reopen any bug which they believe still exists. 18:47:22 thd: reopen and update the labels, yes. 18:47:35 part of the problem with the old ones it is hard to locate the originator... 18:47:35 resolved: as many wranglers as will step forward 18:47:39 slef, /me think it would be more interesting to test/close pushed patches don't you agree ? 18:47:51 thd: slef: and if a bug is marked WONTFIX, a comment could be added that the WONTFIX was done semi-automatically, and is not meant as a moral pronouncement on the validity of the bug 18:47:52 s/interesting/useful/ 18:48:13 gmcharlt++ 18:48:31 paul_p: making it easier to find relevant things in bugzilla will free everyone's time for working on current development. 18:48:42 agreed 18:48:49 slef++ 18:48:57 this is unfun grunt work, but it's been left too long 18:49:14 moving on to admins for the Koha lists on Nabble 18:49:33 OK, rereading your proposal, I misunderstood something slef ! 18:49:35 slef++ 18:49:36 Can we have a label for closed by rule but without investigation? 18:49:40 very good idea ! 18:49:44 mtj: could you clarify what you mean by Nabble admin? 18:50:08 I thought Nabble itself was just one (of several) archives of the mailng list 18:50:12 why does not everybody in the world speak french? that would make my life so easier :D 18:50:12 *list 18:50:22 yeah, i would like to ask the admins at nabble, to grant access to the Koha lists at nabble.com 18:50:39 these lists... -> http://koha.1045719.n5.nabble.com/ 18:51:00 It is, but the admin can update headers and so on. I think kados is the admin. 18:51:14 for 1 or 2 elected kc.org people 18:51:20 whoever it is did change the project link to koha-community.org 18:51:21 I got the koha nabble moved to the new site, but I find nabble very hard to use. 18:51:36 Ah, that was probably me whinging at them repeatedly :) 18:51:53 coo 18:51:57 cool, even 18:51:59 oh yeah, it says Hugo is the admin now. 18:52:04 gmcharlt: hugo, a nabble admin did that, as i asked him to , last week-ish 18:52:22 mtj__: ah, well done! I didn't think I got anywhere! 18:52:31 so currently, only hugo@nabble is an admin... 18:52:51 slef, previously, joshua upgraded all bug from N to N+1 when N was released. I think it means many bugs are now irrelevant, so setting WONTFIX is really a good idea ! 18:53:03 mtj__: are you willing to admin? 18:53:08 anyone else willing to admin? 18:53:16 i propose we elect 1/2 people here, and ask hugo et al nicely f they will grant them admin access 18:53:25 paul_p/slef: can we reopen bugs if we find they still apply to master/3.2? 18:53:26 * gmcharlt tosses name in the hat for redundancy's sake 18:53:32 i am willing to admin the nabble lists 18:53:36 cait: sure 18:53:43 slef: Can we have a label in bugzilla for closed by rule but without investigation? 18:53:49 so I'm hearing gmcharlt and mtj 18:53:51 cait, of course ! 18:53:52 anyone else? 18:53:57 Hi all - Irma from CALYX - sorry I am so late ... 18:54:27 all in favour of gmcharlt and mtj as nabble admins 18:54:31 http://nabble-support.1.n2.nabble.com/Request-to-update-Koha-ILS-mailing-lists-topic-page-with-new-website-address-td6029182.html#a6030223 18:54:54 thd: I think a message is better, but maybe a bugzilla admin can tell us if that's possible. 18:54:58 oi 18:55:00 vote. 18:55:04 +1 18:55:05 +1 18:55:11 +1 18:55:17 +1 18:55:19 thd: slef: yes, a new status could be added, but I prefer simply using a message 18:55:20 (anything so I don't have to use that site again!) 18:55:29 +1 18:55:37 +1 18:55:38 +1 18:55:42 +1 18:55:50 gmcharlt: How can the message be found systematically? 18:56:06 +1 18:56:07 thd: why would it need to? 18:56:16 thd: it will be sent to the reporter. 18:56:27 somebody who cares about a particular issue would either reopen it or file a new bug 18:56:39 +1 18:56:52 +1 18:57:15 gmcharlt: If you are looking for bugs which might be present but had been closed without investigation there should be a way to find them. 18:57:29 #action motion carries 18:57:56 thd: search bug content for a phrase or tag we put in the message. 18:58:31 moving on 18:58:39 #topic KohaCon 11 18:58:50 kmkale it's all yours :D 18:58:55 hi all 18:59:01 hi kmkale! 18:59:03 slef: The message would be fine if there is a consistent word or tag used. 18:59:08 Thanks to the commmunity form choosing India for Kohacon 11 18:59:24 I have prepared a Koha wiki page at http://wiki.koha-community.org/wiki/KohaCon2011 18:59:41