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

Koha project meeting on #koha, 12 September 2008 at 19:00 UTC
by Galen Charlton 05 Sep '08

05 Sep '08

Hi, The Koha developers will be holding a meeting on the #koha IRC channel on Friday, 12 September 2008 at 19:00 UTC. The agenda is currently: 1. Confirm the release manager, translation manager, and documentation manager for Koha 3.2. Each of these positions has one candidate at present: Release Manager: Galen Charlton, LibLime Translation Manager: Chris Cormack, Catalyst Documentation Manager: Nicole Engard, LibLime, 2. Decide on the release maintainer for Koha 3.0 The two candidates are currently Joshua Ferraro (LibLime) and Henri-Damien Laurent (BibLibre). 3. Discuss options for filling the position of QA manager for 3.2. 4. Discuss the features planned for Koha 3.2. All Koha users, developers, and other interested parties are welcome to attend. The meeting will be logged, and I will also send a summary to the koha and koha-devel mailing lists. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

2 2

community structure (RMaint, translation manager, QA manager...)
by Paul POULAIN 05 Sep '08

05 Sep '08

Hi, Back from my august vacation, it seems that we have reach the 3.0 official release, and that's good to see. IMO, the next step is to organize the next months team we need a 3.2 Release Manager, and we have one candidate (galen, LibLime). we need a Release Maintainer, and we have 2 candidates (hdl, BibLibre & kados/joshua, LibLime) we need a Translation Manager, and we have 1 candidate (chris C., Catalyst) we need a QA manager and we had some thoughts about that on irc, although no decision afaik. we need a Doc manager, and we have one candidate (nicole, LibLime). Previously, we always have choosen the guys (sorry Nicole, you're the 1st woman in the game on this matter ;-) ) by IRC general applause (ie: no formal vote, but an evidency that the candidate is the best we will have). We always have had only 1 candidate, except once, for 3.0 RM, were we had joshua & Pierrick. (Seems we had choosen the good guy as Pierrick/Ineo disappeared some time after ;-) ) So : - What about having an IRC meeting to nominate officially all Koha positions ? and announce them everywhere. - What about 3.0RMaint ? hdl is still candidate & will devote some time on that specifically (with BibLibre growing, things should be better for him). Looking at recent head commits, some are bugfixes that should be cherry picked to 3.0 branch. The plan, if he is accepted as RMaint, is to release a version once every 3 months (except if there is a blocking bugfix : "immediate" release in this case) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc NOUVEAU TELEPHONE : 04 91 81 35 08

7 10

Koha 3 Advanced Search
by zang＠zang.co.za 04 Sep '08

04 Sep '08

I have a very basic problem with my Koha 3 test installation. If I use the "Limit type to" selection, my search does not show anything. My Items are set as "Books, Booklets, Workbooks", but if I set the "Books, Booklets, Workbooks" checkbox, I get "No results found". If I unset the checkbox, it finds my search. Is this a known issue? Your help will be appreciated.

3 2

Re: [Koha-devel] To maintain a 'dev installation with rep 3.0.x
by Zeno Tajoli 03 Sep '08

03 Sep '08

Hi, At 14.54 03/09/2008, Galen Charlton wrote: >On Wed, Sep 3, 2008 at 3:36 AM, Zeno Tajoli <tajoli(a)cilea.it> wrote: > > get checkout my3.0.x > >You may want to do > >git checkout -b my3.0.x > >in order to create a new 3.0 working branch, unless my3.0.x exists already. in fact I have done an error on cut & paste. The instruction that I thin to use are: git fetch git branch --track kohaclone origin/3.0.x ['kohaclone' is the name of my local branch] get checkout kohaclone get pull I want only to update an existing branch. Thank you Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 1

To maintain a 'dev installation with rep 3.0.x
by Zeno Tajoli 03 Sep '08

03 Sep '08

Hi to all, I have little experience with git so I ask you a confirm of my thoughts. Date: Mon, 11 Aug 2008 16:05:53 -0500 From: "Galen Charlton" <galen.charlton(a)liblime.com> Subject: [Koha] Koha 3.0.x Git branch created >If you are running a dev-mode installation of Koha 3.0 and you *don't* >want your installation to start following the 3.1 developments, you >should fetch, create the tracking branch, and check out that branch >BEFORE rebasing and going through the database update. I have a dev-mode installation, last update 26-Jul-2008, so I don't have the exact 3.0 stable version. I want to have the last maintaining version, the branch called '3.0.x'. I think that I need to do those operation with git: git fetch git branch --track kohaclone origin/3.0.x ['kohaclone' is the name of my local branch] get checkout my3.0.x get pull With those operation I will have a dev installation with the last maintaining version ? Thank you for everything Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 1

RFC 3.2: Autogeneration of Koha UML diagrams
by Zeno Tajoli 03 Sep '08

03 Sep '08

Hi to all, from first day of October 2008 CILEA is going to support a project about Koha as student stage (followd by me). We want to improve tecnical documentation about Koha 3.0 (I hope to have a stable release for october !!). Starting from perl scripts avaible from internet we want to develop a script that read Koha API (C4 dir) and write a .xmi file with an UML rappresentation of classes, methods and usage of methods. In fact a work like this is possible only if API are written in a precise standard of coding. It thimk it s , as I know. But this is also a good check. We will report all problems we found, to be fixed in 3.2 We also write complete E-R diagrams for Koha DB and a specific document for every table But now the .xmi file in fact needs to be sligthy different for every UML tool. We can work with two Open source tool, ArgoUML and Umbrello We can usa also Rational Rose (the biggest commercial tool for UML). Which tool do you prefer ? If you think it is a useful project, I will insert it into RFCs for Koha 3.2 <http://wiki.koha.org/doku.php?id=en:development:rfcs3.2> Bye Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

4 5

RFC: Advanced patron search
by Danny Bouman 02 Sep '08

02 Sep '08

"Problem The ability is needed to search for patrons on many different fields, including email address, street address, phone number, etc. Using additional patron attributes is not a viable solution as it would require a tremendous amount of duplicate data on all fields that would need to be searchable. Possible Solution #1 Create a standard search API that functions for both circulation and patron searches and supports the ability to search on many different fields. Possible Solution #2 Create a member search API that supports the ability to search for patrons on many different fields. Technical Notes System preference should exist for what patron fields are able to be searchedWhen a Staff member clicks on the Patron menu item, they should immediately be taken to the advanced search screen, which could exist below the browse by last name. This display would be in a similar format to what Staff see when they click on the Search menu item.Patron Attribute types that are able to be searched should appear in the advanced search. http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_advancedpatro… Any thoughts, questions, or comments? -- Danny Bouman Web Programmer Howard County Central Library 10375 Little Patuxent Parkway Columbia, MD 21044 410.313.7924

3 3

Status of koha.org on Plone
by Joshua Ferraro 02 Sep '08

02 Sep '08

Hi folks, Well, September's here and I've still not been able to find the time to pull together a new koha.org site based on Plone; too many other priorities have gotten in the way. I still have it on my list and I'm optimistic that I should be able to turn something around in the next couple weeks, so please give me until Sept 15th to have something up and running with some basic content and a proposed workflow for authoriship, review, translation, etc. Sorry for the delays. Cheers, Josh -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

Python MySQLdb question
by Rick Welykochy 02 Sep '08

02 Sep '08

I know this is a bit far fetched but I am hunting for any hints anywhere. I have a script written in python that manipulates data (i.e. reads and writes tables) just fine for Koha/2.2.9 databases. This is using python + MySQLdb. But when I access Koha/3 tables, things are differnt. Reads are fine, i.e. I can select and read tables. But writes silently fail, i.e. all inserts are silently discarded. This is very weird behaviour for python, since it normally raises an exception if there are *any* problems in the db module. I am putting it down to differences between the Koha/2.2.9 tables and the Koha/3.0 tables. The only differences I can see are the charset used, i.e. Latin-1 vs utf8. Any ideas? cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor Do you realise that in forty years we'll have thousands of old ladies running around with tattoos and rap music will be the golden oldies? -- Maxine

2 2

RFC 3.2 - turn on warnings
by Galen Charlton 30 Aug '08

30 Aug '08

Hi, Perl's warnings pragma is the cheapest way to find bugs. We already use the strict pragma; now it's time to add warnings. More importantly, it's time to review the messages produced by the warnings pragma and fix the underlying issues. To reiterate, this RFC has two goals: turning on warnings, and fixing all warnings thus reported. Doing the first without the second will simply cause Apache logs to overflow. Ideally, all Perl scripts and modules should have warnings enabled by the time 3.2 is released. I propose the following steps to implement this: 1. Update the coding guidelines to require 'use strict' and 'use warnings'. 2. For any new scripts and modules, require 'use warnings'. Since Koha (per Makefile.PL) requires at least Perl 5.6.1, the 'use warnings' pragma should be used instead of -w. 3. Systematically go through and turn on warnings for each script and module. 4. Unsystematically turn on warnings. I.e., whenever you patch a particular script, consider following up with a separate patch to turn on warnings. I suggest a separate patch because turning on warnings is not enough; you should run the script through its paces and fix any problems reported by the warnings pragma. For modules in C4, note that this can be a big commitment: turning on warnings means testing every function and method. 5. Create a standing blocker bug for 3.2 for adding "use warnings". 6. "no warnings" should not be used absent a detailed comment explaining why warnings should be turned off within a block and why it is not possible to change the code to avoid the warning. It _might_ be acceptable for temporary use while turning on warnings in a big module This RFC can also be found at http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_turn_on_warni… Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

6 14