August 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

Dashboard browser notifications
by Tomas Cohen Arazi 27 Sep '17

27 Sep '17

Do you think we could add browser notifications superpowers to our dashboard? I can't work on it right now, but it would certaintly help me being aware of stuffs I can help with if urgent. What I like about browser notifications is that people can block them pretty easily (it is one of the two options browsers offer for them) and interested people would greatly benefit from them. -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Dedicated Zebra Server
by Mansur Ali 25 Sep '17

25 Sep '17

Hello, I am using KOHA ILS. Can i able to use dedicated Zebra Server which is installed in another server? Could you please advice if possible? Thank you, -- Mansur Ali +966568978721 | +919061635954 | mansuralih(a)gmail.com

8 12

Proposal for ES6 development on the staff client
by Jesse 13 Sep '17

13 Sep '17

As part of my work on bug 15522 <https://bugs.koha-community. org/bugzilla3/show_bug.cgi?id=15522>, I've been working with Preact (a React clone with a friendlier license). We've established that this needs ES6[1] in previous discussions on the mailing list and in IRC. From there, we found IE's many limitations meant we needed a transpiler[2] to to make use of these features. Owen and I have been thinking about the easiest way to do this, and this is the lowest-friction process we've come up with to transpile ES6: $ sudo apt-get install nodejs npm $ sudo npm install -g yarn $ yarn install $ yarn build Yarn is a somewhat faster version of npm, the de-facto JavaScript package manager. Normally, this would be a pointless addition, but the npm in the Debian repositories is 3 major versions out of date, and therefore not a great option. Many npm packages simply fail to install. This is a constant problem with the JS packages in the Debian repos; most if not all of the tools that one might want either are completely unpackaged or woefully out of date. Packaging them ourselves means working our way through a number of dependencies (see [3] for an example). Any frontend build process worth our time cannot solely use packages from the upstream repos. That aside, this build process will use Gulp, Browserify and Babel to take any files in koha-tmpl/intranet-tmpl/prog/js/src, and compile them into a matching file in koha-tmpl/intranet-tmpl/prog/js/built . This means that any new files will not have to be manually whitelisted. You can see a working example at https://github.com/pianohacker/koha, branch bz15522. I'm currently committing the built versions of the files, but this is purely for convenience of prototyping. The page in question is admin/policy.pl, and the relevant code is at .../prog/js/src/admin/policy.js . [1] ECMAScript 6, a semi-recent version of JavaScript with a large number of new features, including a nice class syntax, arrow functions, and destructuring assignment. [2] A tool that transforms ES6 syntax (and the JSX syntax extension used by (P)react) into something that can be run by older browsers, including IE. [3] https://wiki.debian.org/Javascript/Nodejs/Tasks/gulp -- Jesse Weaver

4 7

[Important] Update your MySQL|MariaDB configuration to avoid data loss
by Jonathan Druart 01 Sep '17

01 Sep '17

Hello everybody, This is an important email and you should not ignore it. If you are a librarian and have no technical skills you should forward this email to the administrator of your Koha installation. We have been dealing with circulation history loss in the last versions of Koha, and we ended up with a solution. You should read the following wiki page attentively and set up the proposed solution: https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix Cheers, Jonathan

3 5

Koha 17 on Centos 7
by Waylon Robertson 01 Sep '17

01 Sep '17

Is there instructions somewhere, that tell me how to install koha 17 on centos 7? Does anyone have any hints? Do i really have to one by one, install all those dependancies that the dependancy script says? or is there a faster way? Waylon | | Virus-free. www.avast.com |

3 2

Documentation IRC Meeting - August 31, 21 UTC
by Katrin Fischer 31 Aug '17

31 Aug '17

Hi all, we'd like to invite everyone interested in improving Koha's documentation to an IRC meeting on August 31, 21 UTC. Updating the manual is a big task and we need all the help we can get! The agenda and a link to calculate the time in your local timezone can be found on the wiki: https://wiki.koha-community.org/wiki/Documentation_IRC_meeting_31_August Please feel free to add topics and ideas to it! Hope to see you there! Katrin

1 1

QA sprint day - wish list
by Jonathan Druart 31 Aug '17

31 Aug '17

Here is my wish list for tomorrow :) Priority is bugs: blockers, criticals, majors then normals (as usual, right?) Then: Test suite improvement: Bug 18055 - Speed up '00-strict.t' test Bug 18979 - Speed up 'valid-templates.t' tests TT syntax for notices: Bug 17981 - Add the ability to preview generated notice templates (and parents!) Refactoring: Bug 18149 - Move CountUsage calls to Koha namespace Bug 18595 - Move C4::Members::Messaging to Koha namespace Bug 19059 - Move C4::Reserves::CancelReserve to the Koha::Hold->cancel (and parents!) Feedback needed on: Bug 17600 - Standardize the EXPORT Others: Bug 18298 - Enforce password complexity Bug 17380 - Resolve several problems related to Default authority framework I have created a pad with the list of the bugs in the "Signed Off" queue (generated now): https://annuel2.framapad.org/p/koha-qa-print-Sept-1-2017 It may be useful to track down who is working on what (add your name on the right for instance? Remove the line from the list if done, etc?). Feel free to suggest something else if it does not fit. Cheers, Jonathan

1 0

Where is the BIG RED WARNING button?
by Jonathan Druart 31 Aug '17

31 Aug '17

Hi devs, I started the discussion during today's dev meeting. As RM I realise that I need a big red warning button to push to trigger help when there is something urgent to do. The last problem has been the already famous checkin issues (see bug 18966 and ancestors). They were marked as "blocker" for the last 2 months and affected all the stable releases. I tried to alert you several times but I did not really receive the attention needed. There are several ways to help you to know easily what is waiting for urgent attention: - The dashboard displays a "bug tracker health status" which shows blocker, critical and major bugs (http://dashboard.koha-community.org) - This section can be easily displayed on your own bug tracker using http://dashboard.koha-community.org/bz_status - I report on the kanban the tasks waiting for help, there is also a red "important" tag to highlight some. The columns list the bugs in the different queues with the most importants on top ( https://tree.taiga.io/project/joubu-koha-rm-1711/kanban) - The "what's on in koha-devel" email list the bugs that are waiting for love I am not sure what I can do more to match your workflow, and I do not think I should propose something else. I really would like to avoid individual and repeated pings. I do not provide paid support to any customers and then, I do not understand why I care more about blocker and critical than paid support companies. If you do not think it is important, why should I? :) This discussion has to be done and answers to be given, I do not plan to push anything "big" until we have a solution. Indeed I do not want to take the risk to face another situation like that. Cheers, Jonathan

2 1

QA sprint day - Friday, September 1st
by Jonathan Druart 30 Aug '17

30 Aug '17

Hi devs, The QA team is organizing a QA sprint day on September 1st, in 2 days! If you want to fill the Signed Off queue, it's a good time :) Cheers, Jonathan

2 1