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

[QA] QA process
by Katrin Fischer 03 Dec '12

03 Dec '12

Hi all, We already agreed some time ago that the patch writer and the patch sign offer should not be from the same company/library/party. I would really like to extend that rule to also apply for patch writer and QA team member. For 3.12 we got a big QA team, which is great, because with all the ongoing work we are going to need it. And it also gives us more options and flexibility when it comes to these kinds of questions. I would like to get your opinions on this, can we agree on this new rule? Katrin

6 11

Zebra Server - Cannot allocate Memory
by SANDEEP BHAVSAR 02 Dec '12

02 Dec '12

Dear All I have been observing from last one week that our Koha search stop after 24hrs and when we restart Zebra then it starts working. log show the error as : : zebra server is failing with following msg 10:40:03-29/11 [fatal] fork [Cannot allocate memory] I have searched for the solution on google but no success. -- Thanks and Regards Sandeep Bhavsar Librarian Dr.V.N.Bedekar Institute of Management Studies Thane(W) 400601 MUMBAI. INDIA @@@@@@@@@@@@@@@@@@@@@@@@@@ email : sandeep.bhavsar(a)gmail.com Mob : 9987049099 elibrary :http://www.vpmthane.org/im/elib/main.htm @@@@@@@@@@@@@@@@@@@@@@@@@@

2 2

A question/suggestion on OPAC introductory page enhancement
by Manos PETRIDIS 01 Dec '12

01 Dec '12

I wonder if a list of recent additions could be added to the library initial OPAC page. It would have to be based on the library selected I suppose, and could be divided perhaps in sub-lists, based on item type, collection, target audience, etc. Is there already such a provision in koha that I am unaware of? I did a look-up on the bug-list and found a related recent entry: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7917 that could make such an enhancement more manageable. Kind Regards, Manos Petridis

1 0

how could i change in the view of the records in OPAC
by Mohamed zalabany 01 Dec '12

01 Dec '12

i need to change the sequance of the fields of MARC record in normal view in opacand add new fields to appear in the opac in the normal viewcould you please tell me how could i do thati reached to that i need to change in /usr/share/koha/opac/htdocs/opac-tmpl/prog/en/xslt/but i don't know which file also i need to know how could i remove MARC view & ISBD view in the opac Mohamed El ZalabanyIntegrated library systems consultant Zalabany Knowledge Systems Team© For Libraries and Information systems Development and support mh_zalabany(a)hotmail.com Mobile: 0111291444

1 0

November Koha Community Newsletter has been published
by Daniel Grobani 30 Nov '12

30 Nov '12

Hi, The November 2012 edition of the Koha Community Newsletter has been posted to http://koha-community.org/koha-community-newsletter-november-2012/ . Cheers, Daniel Grobani Koha Community Newsletter Editor

1 0

3.10.0 release notes translated to French
by Paul Poulain 29 Nov '12

29 Nov '12

Hi koha-devel, Just in case a reader of this list is not reader of the French mailing list and maybe interested: the release notes document has been translated to French: http://koha-community.org/files/2012/11/Koha-3.10-nouveautés.pdf -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

1 0

Translate > Timeout
by Tomas Cohen Arazi 29 Nov '12

29 Nov '12

A few days ago I noticed access to translate.k-c.org is not possible. Timeout is the rule. Can we fix it? If there's anything I can do to help, i'll be glad to do it. Regards To+

4 3

How to change fine calculation timing: another appeal
by Vimal Kumar V. 29 Nov '12

29 Nov '12

Dear Friends, In my experience Koha installation from Ubuntu packages is very convenient and easy to keep update with forthcoming versions. Everything works fine with latest version of Koha. But one problem still haunting me, change of default time fixed to run fines.pl cron. Many users like to change the fine calculation to another convenient time (e.g. 10 AM). Dear developers, kindly guide me how to change the fine calculation time. Regards -- Vimal Kumar V. Mahatma Gandhi University Library Kottayam, Kerala- 686 560 Web: http://www.vimalkumar.org Blog: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

1 0

Commit messages
by Jared Camins-Esakov 29 Nov '12

29 Nov '12

A gentle reminder: if there is information needed for testing a patch, it should be in your commit message, not just in comments on the bug. If -- in the course of looking at a patch for pushing to Master -- I follow the test instructions in a commit message and the patch does not work, or if I can't quickly divine what the patch is about, I will ask for clarification and move on. If I don't understand, I have no reason to think that I will start to understand after spending more time on the issue, and any time I spend not understanding one patch is time during which no other patch is getting reviewed. So, what should be in a commit message to avoid a note from the RM requesting that you summarize something you already said? Every commit message should have the following: 1) A subject that includes the bug number at the very beginning of the line. Something like: "Bug XXXX: enable frobbing the whatsit" 2) A description of what problem the bug addresses, or what feature it adds. If it's a very simple patch, this might be covered by the subject line, but probably not. Often you can get this by copying the description of the bug out of Bugzilla and into your commit message. 3) A detailed test plan. When I say "detailed," I mean that it should include enough detail that it could be followed by someone familiar with Koha who does not use whatever section of the code you are editing. A test plan with forty steps may seem daunting, but it really isn't. It's considerate. Ideally, the test plan should cover how to confirm the bug *and* how to confirm that the patch fixed the problem, if the two procedures are not entirely identical (for example, if your patch involves Zebra configuration changes, note which files need to be updated; I favor a tl;dr section which includes information of this sort). 4) I'd also love to see a list or a summary of tests performed by the person who tested and/or QAed the patch. Finally, this is not grounds for an irate message from your irascible RM, but worth a reminder while we are on the subject of commit messages: ideally we are shooting for a subject which is 50 characters or fewer, and the body of commit messages should be wrapped at 72 characters. See http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html for more on this subject. In the last month I have pushed 187 patches (some merge commits, of course, but most not), and we still have a huge backlog on Bugzilla, with little prospect of the flood slowing (this is a good thing!). Let's work together so that we can get the backlog down and keep it that way. Regards, Jared P.S. Although I write this from my position as RM, it is worth noting that these recommendations will help at every stage of the process. Your patches will get signed off and QAed faster if there's a good test plan, and if there's a problem with one of your patches people are more likely to try testing the revised patch if they know that they're not going to have to flail about trying to figure out how to test it. -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

1 1

Re: [Koha-devel] When is the release of Koha version 3.12.00?
by Jared Camins-Esakov 28 Nov '12

28 Nov '12

Hello. Please make sure you guys deal with the Indexing and search tool for non > Latin characters in Koha. This need to function by default without > any complications. > I appreciate your eagerness, however, list etiquette dictates that you keep your replies on-list and sign your name. Common courtesy, of course, dictates that you not make demands of people who are *volunteering* their time for developing a piece of software you are not paying to use. Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

2 1