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

Write good bug report titles and commit messages
by Jonathan Druart 04 Apr '18

04 Apr '18

Hi devs, I would like to do a little reminder about the bug report titles and commit messages. For bugs: The bug report title must shortly tell what the *bug* is, whereas the commit messages must tell what the *fix* does. Sometimes they are not related at all. For instance: - bug report titles: "Feature X is not working correctly when Y is enabled", "Click on button 'Save' does not save the record", "Saving stuff on screen X does not work", "This script generates error logs", "Mystake is misspelled in this script", "Behaviour X no longer work as expected" etc. - commit messages: "Fix Feature X when Y is enabled", "Make sure behaviour is correct when button is clicked", "Remove warnings from this script", "Correct spelling of mistake in this script", "Fix regression on behaviour X" etc. For enhancements / new feature: We could have the same title and commit messages in some cases. - bug report titles: "Add new awesome feature", "Add the ability to do that", "Code is duplicated in method Koha::Stuff->method" - commit messages: "Add new awesome feature", "Add the ability to do that", "Remove code duplication in method Koha::Stuff->method" Note that "Address comment #42" is a terrible commit message. Then, I would like to standardize the commit messages a bit. We have "Bug 12345 - ", "Bug 12345: ", "Bug 12345" and "[follow-up]", "(follow-up)", "[QA Followup]", etc. I would suggest: "Bug 12345: you commit message" And reject any commit messages with only "follow-up" (or whatever how it is written), but accept "Bug 12345: (follow-up) same commit message as before" If you forgot something, even if "Bug 12345: (follow-up) This was missing" And QA follow-ups (added by QA team member): "Bug 12345: "(QA follow-up) Add/remove this stuff" I am going to suggest these change during the next dev meetings. If accepted I will change the bug report titles and commit messages before the push during few weeks, then ask authors to do it themselves (patches from new contributors will not be rejected for that reason). You should also read or re-read: https://wiki.koha-community.org/wiki/Bug_Reporting_Guidelines https://wiki.koha-community.org/wiki/Commit_messages Cheers, Jonathan

6 6

Koha 17.05.03 released
by Fridolin SOMERS 27 Nov '17

27 Nov '17

The Koha community is proud to announce the release of Koha 17.05.03. This is a security release including 3 enhancements, 13 bugfixes and 16 security fixes. The full release notes are available at https://koha-community.org/koha-17-05-03-security-release/ Regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

2 4

Multiple levels approval for suggested title and multiple level late fee slabs required in Koha
by Manju N 01 Nov '17

01 Nov '17

Dear All, Anybody has customized the Koha for multiple level approval of suggested titles from the patrons/faculty in Acquisition module? In our library, we need multiple level approvals such as from the Head of Department and Chairman, Library Committee/Dy. Director etc. We also want to use multiple levels late fee/fine slab. Currently, Koha supports only one late fee slab. We have different late fee structure/ slabs at our library. Please let us know if anybody customized the Koha for the above requirements. With Regards Manju Naika, PhD Asst.Librarian IIT Bombay

3 2

Mailinglist "Koha"
by Michael Kuhn 30 Oct '17

30 Oct '17

Hi Does anyone know hat happened to the mailinglist "Koha", it seems the list has become inactive? I haven't received any e-amils from there since October 25. Also I sent one answer but it didn't appear until now (at least I didn't receive it via the list). I didn't know where else to ask this. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

4 5

Vote request for Bug 18483 Customised help: Enhance staff client with news based, easily editable help system (Passed QA -> In Discussion)
by Marc Véron 30 Oct '17

30 Oct '17

Dear Koha community On 2017-04-22 I filed Bug 18483 "Customised help: Enhance staff client with news based, easily editable help system". https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18483#c0 The Enhancement was ready for Sign off on 2017-04-30, was signed off on 2017-05-02, and, after some discussion, passed QA on 2017-10-27, and the same day was set to "In Discussion". The aim of the bug is described in the initial comment. It fills a request we have since 2012. In short, it is about having an additional help system that allows libraries to create their own, library specific help information, taking advantage of all functionality we already have with the news system. Initial comment: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18483#c0 ---Quote--- "Koha's staff client has a file based help system with an edit function for customising. However, the edited files have to be saved and restored with each release. Otherwise they are overwritten. As an enhancement or alternative, the existing news system can be used to implement a complementing help system. Similar to the news, the text can be created for all branches or for individual branches. Help is context sensitive (based on the existing help system), and it can be created / edited directly from the help page (based on a user permission). The display can be managed with a system preference (Bug 18472: Add system preference CustomOnlineHelpStaff to hide / select custom online help system)." ---End quote --- Author's answer on a question of QA team member M. de Rooy (asked on Bug 18472, Comment 21), moved to Bug 18483: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18483#c21 ---Quote--- Need: - Having a user editable, page aware help system is a long outstanding need. First time I was asked for goes back to 2012. - We have libraries interested in Koha who ask for in their requirements. - Writing a brand new help module would take a lot of time. And who would fund it? User: - The news system works very well and libraries are used to use it. The help additons introduced in Bug 18483 enhances the news system to host custom help as well. - From a user standpoint it is easy to use, you can add whatever you want / need as help. All the benefits of the news system can be used. Custom help items can easyly be added / edited. - It can be turned on and off (combined with the existing file based help system or 'standalone'). This Bug 18472 is the basis for turning on and off and/or add additional help systems. - There is no change in behavior of news and file based help system if turned off (however this patch allows to turn off the edit function of the existing file based help system). Impact: - In Bug 18483, I paid great attention to have a minimal impact on existing code. No changes in .pm files were needed. - There is a small database change to have a field to host the page key if a news item is used as help item. Things to come: - Since the news system works for both staff client and OPAC it will be easy to implement the editable help for OPAC as well (Bug 18515) So I kindly ask for Bug 18472 and Bug 18483 to make part of Koha. ---End quote--- After the enhancement has been put to "In discussion", I kindly ask the Koha community to vote about Bug 18483 as outlined in: https://wiki.koha-community.org/wiki/Bug_and_Enhancement_Discussion Thanks and kind regards Marc Véron Koha Support Schweiz www.koha-support.ch Contributing to Koha since 2012

2 1

DBMS_auto_increment : cannot check-in items checked out before a certain upgrade
by Giuseppe Angilella 29 Oct '17

29 Oct '17

Hi, I am running Koha 17.05.05.000 on Ubuntu 14.04.1 with mysql Ver 14.14 Distrib 5.5.58. I regularly upgrade Koha via apt-get, and I've suddenly realized I cannot check-in items which had been checked-out (presumably before a certain upgrade). I can check-in items which have been checked-out with the presently installed release of Koha. Following the error message, I came across the wiki page: https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix I followed the instructions given there, and added the additional init file as described there. No error reported by /var/log/mysql/error.log upon restarting or running the mysql service. However, I cannot yet check-in back items which were checked-out in the past. (I can still do that with new check-outs.) Since it seems that the problem is solved with new check-outs, would you recommend that I manually remove old check-outs from the database, and issue them again (with a new date - doesn't matter, as long as it works)? Many thanks and best regards, Giuseppe.

1 0

Multiple level approvals for suggested titles and multiple levels late fee/fine slab
by Manju N 28 Oct '17

28 Oct '17

Dear All, Anyone has customized the Koha for multiple level approvals of suggested titles from the patrons/faculty in Acquisition module? In our library, we need multiple level approvals such as from the Head of Department and Chairman, Library Committee/etc. We also want to use multiple levels late fee/fine slab. Currently, Koha supports only one late fee slab. We would appreciate any comments or suggestions that will help us to tweak the koha. With Regards Manju Naika,PhD Asst.Librarian,IITB

1 0

Roles for 18.05
by Jonathan Druart 26 Oct '17

26 Oct '17

Hi, The roles for the next release cycle are opened https://wiki.koha-community.org/wiki/Roles_for_18.05 Please add your name if you want to join the release team. Regards, Jonathan

3 2

Koha 16.05.18 released
by Mason James 25 Oct '17

25 Oct '17

The Koha community is proud to announce the release of Koha 16.05.18 This is a maintainance release including a few security fixes. The full release notes are available at https://koha-community.org/koha-16-05-18-release Cheers, Mason _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha

3 3

Reminder - Koha Developers Meeting, 25 October 2017, 21 UTC
by Nick Clemens 24 Oct '17

24 Oct '17

Hi All, Hope to see you tomorrow, please add anything you wish to discuss to the agenda below, or add your apologies if you can't make it. See you in IRC! Point your favorite IRC client at irc.oftc.net:6667 and join #koha or connect directly to the Koha channel: http://webchat.oftc.net/?channels=koha Agenda: https://wiki.koha-community.org/wiki/Development_IRC_meeting_25_October_2017 Local date time of meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I…

1 0