- Koha-devel - lists.koha-community.org

KohaCon 13 Survey Problem
by Nicole Engard 06 Jul '12

06 Jul '12

Hello all, I wasn't clear when I sent out the survey for KohaCon and per a discussion in #koha I'm coming to you to see if you'd like me to rerun the survey so you can update your votes. Here's how it works - and how it worked in previous years: If you vote for someplace as #1 it gets 5 points, #2 it gets 4 points, and so on. In the end we tally the points to see where the conference takes place. That way if everyone picks one place as #1 but more people pick it as second and third it still might win. So basically if you won't go somewhere no matter what then don't vote for that location and it will get no points from you. This means that those of you who didn't know the rules - because I didn't make it clear at all (my fault) might not have voted the way you would have if you knew the rules. So my question to you all is ... should I close voting and put out a new call for votes explaining the procedure more clearly - or do we just carry on as we are? Nicole

11 17

Re: [Koha-devel] Bugzilla Statistics
by Marcel de Rooy 06 Jul '12

06 Jul '12

> To that end, I have been creating the statistics of signoffs > http://blog.bigballofwax.co.nz/2012/07/01/bugzilla-statistics-for-june-2012/ Interesting statistics. I was trying to get these results from Bugzilla too. So I tried this search: Changed: (is greater than or equal to) 2012-06-01 Status: (changed to) Signed off Status: (changed after) 2012-06-01 *** This after seems to be an inclusive one Status: (changed before) 2012-06-30 23:59:59 Note that I got 214 results. More than the 194 that Chris counted. It appears however that Bugzilla is not completely reliable here. By example: It includes report 7848. History shows that Status changed to Signed-off on May 31 and again on July 2. The status change in June was to Failed QA. So it should not have been included? Any idea why? Another thought: A report that was signed off twice in June, cannot be counted twice via Bugzilla search.

2 1

Koha Release Manager monthly newsletter 8 published
by Paul Poulain 04 Jul '12

04 Jul '12

Hello Koha users & developers, I just published my monthly RM newsletter at http://koha-community.org/koha-release-manager-newsletter-8-2012-06/ Enjoy -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

About IRC meeting & voting
by Paul Poulain 04 Jul '12

04 Jul '12

Hello world, Sorry for missing yesterday IRC meeting, but after 10 days away from home, my family needed me (and it was 8PM here !) During the meeting, Owen said, as a joke: oleonard> 24-hour meeting, votes ever hour, day-end averages win. but i'm not sure it should be a joke: there is always someone sleeping or (wanting to) during the IRC meeting. So shouldn't we vote not during IRC meeting, but just confirm the vote, that is made during a period before the IRC meeting, on an other tool, like wiki, gdoc, yell +1 / 0 / -1 on the mailing list, a tool like http://www.ballotbin.com/ (untested, just found it in google) or whatever you want. I think that would also help more people being involved: attending an IRC meeting is, for some, a too high barrier (in France, there's a barrier with the language, for example). More vote, more involvement,... sounds a good deal isn't it ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

8 11

[DISCUSSION] Database schema & coding guidelines
by Paul Poulain 04 Jul '12

04 Jul '12

In the wiki page http://wiki.koha-community.org/wiki/DB_schema_bugs, an insconsistency has been noticed: primary keys column name can be: id (in authorised_values table), xxxid (cityid), xxx_id (label_id), xxxId (limitId), xxxcode (branchcode), xxxnumber (borrowernumber) => choose how to name PK and update schema accordingly The bug 7065 add a foreign key to the reserves table, so I think it's time to clearly choose how we name primary keys. The possible options are below, my opinion: 1- id alone => will result in complexity & mistakes, this option must be discarded 2- xxxxid => short option, may result in hard readability. 3- xxxxId => we haven't decided if we want UC in field names. I won't discard this option, but does not favour it. 4- xxx_id => _ still undecided in field names, I'm not sure it's much better than the xxxid one 5- xxxxnumber => number is quite long, and may result in very long field names, which is not good. I does not like this option. Let's start the discussion -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

6 12

A C4::Logger module would be useful ?
by Jonathan Druart 04 Jul '12

04 Jul '12

HI all, I have developped a logging module (based on LogLite). I think it could be useful for Koha. A new system preference controls the log level (eg. level warning for production and debug for development). It can be used by a simple script or into Koha. How it works: See Bug 8190 ( http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8190) Please have a look at that, and tell me what do you think about it. Technically, is it satisfying for you? I think it could help us to increase the code quality. Any others ideas are welcome ! ++ Jonathan

8 13

[discussion] Privacy issue (bug 3280)
by Paul Poulain 03 Jul '12

03 Jul '12

Hello Koha users & developers, The bug 3280 fixes a problem in cart sending in opac : the behaviour has changed, and for security reason, it will be possible only for logged-in users. A question has also been raised : we could also add the IP address of the sender in the mail that Koha sent. Do you think : 1- we could 2- we should 3- we shouldn't (and why) I start arguing = I think we should, and in France, I think it's a legal issue, you must be able to answer any legal request from a court (9-11, thank you :\ ) It's right we have the username, but the IP address is a good complement -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 1

KohaCon 2013 Voting Open
by Nicole Engard 02 Jul '12

02 Jul '12

The voting for the KohaCon13 Conference Venue is open! http://survey.web2learning.net/limesurvey/index.php?sid=91534&lang=en Please vote for where you'd like to see KohaCon 2013. To review the full proposals please read here: http://wiki.koha-community.org/wiki/Kohacon2013 Once I know when the voting should close I'll share with you all :) But for now, get your votes in!! Thanks a bunch, Nicole C. Engard Documentation Manager

1 1

http://wiki.koha-community.org/wiki/Koha_Namespace_RFC, moving ahead
by Paul Poulain 29 Jun '12

29 Jun '12

Hello koha-devel, After our discussions during the hackfest, a wiki page has been written. Now, it's time for the first patches, to see how it could look like. I made some work on bug 8309. That's not a request for signoff, but to look at the code, comment, discuss, ... Note: if you want to play with those patches, look in admin/categories.pl and testrelations.pl. You'll have to install Moose and DBIx::Class, (available on probably all linux distros) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

4 3

Bug 6557 pushed, please check localised frameworks
by Paul Poulain 29 Jun '12

29 Jun '12

Hello devel & translate, I just pushed the patch for bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6557 . It fixes a nasty long-lasting problem, BUT will work only if your frameworks are OK. The popularity is based on biblioitems.totalissues field, that *must* be linked to 942$0 field. It's the default for MARC21 in english, I've fixed UNIMARC in french, *please* check your language/marc flavour. If the biblioitems.totalissues is not linked to 942$0, you'll get a nasty (and unclear, i've asked for a follow-up to have something more understandable): Tag "0" is not a valid tag. at /home/paul/koha.dev/koha-community//C4/Biblio.pm line 3870 *nengard* = this one will need a large/complete documentation ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0