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

Centralize and move to gitlab
by Jonathan Druart 08 Aug '18

08 Aug '18

Hi devs, (Spoiler: I am not talking about a move from bugzilla to gitlab for the Koha git repo) Just a quick comment: gitlab has the ability to move projects with all the issues. >From the export page of a project, they say: """ The following items will be exported: Project and wiki repositories Project uploads Project configuration including web hooks and services Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities """ So that will be easy to move (already discussed with Chris, will do in May) * koha-community-devs-users/kohadocs to koha-community/kohadocs * https://gitlab.com/koha-dashboard/koha-dashboard to koha-community/koha-dashboard And the ones from github too: * joubu/koha-misc4dev to koha-community/koha-misc4dev * Koha-Community/qa-test-tools to koha-community/qa-test-tools Then, maybe: koha-testing-docker koha-release-notes kohadevbox koha-howto The idea is to centralize our things in one place, ease the PRs and the ability to clone/fork keeping the visibility on what is the reference (account 'koha-community'). I would also like to generate a CI configuration for some of them. CI file for Koha: https://tree.taiga.io/project/joubu-koha-rm-1711/us/146 (I am going to submit that on bugzilla soon) CI file for the manual: https://gitlab.com/koha-community-devs-users/kohadocs/blob/master/.gitlab-c… Any pros/cons? Cheers, Jonathan (No troll please)

11 16

Exploration of Koha ElasticSearch implementation
by Claire Hernandez 06 Apr '18

06 Apr '18

Hi, I want to share a work with you. I knew we can now switch SearchEngine syspref to ElasticSearch in Koha community version, but I didn't know a lot more. I explored with some BibLibre guys what we can really do, if we can propose this feature to our users. It seems there is some work to do but it would be great to have a more solid version for 18.05 if we test and fix more things, a version for early adopters who want to try it in production. I began a document where I list the gap to this version, it is a work in progress. I integrated the items identified by Nick (kidclamp) in the wiki page (Elastisearch_status). Thanks. I could have put everything in bugzilla or wiki but it wasn't ideal to me at this time. Depending your feedback I can make it better. https://docs.google.com/spreadsheets/d/10VUKvIYZjlbJhE-oCLmInLe601su6vIRBRC… Notes about tabs: - Way to 18.05 : I wanted it "macro functionnal", but currently it lists features or issues that may be too small. I tried to evaluate the work in "complexity point", "1" can be one developper day or maybe more or less; - Questions : can be used as a faq, I dropped my questions, sometimes I answered myself and other time someone else answeredme; - Queries and behaviours : we did a lot of work to implement Solr in Koha (at BibLibre, it begun in 2011) and an advanced search version is always maintained. I think it can be asked, so I pasted a list of queries we work with, it is expected to be different, it is just examples; - Pros : quick list of advantages for ElasticSearch in Koha Please, feel free to read, add lines, add questions or whatever. I am often available on #koha (@clrh). Claire.

2 2

sources gitignore under versionning
by Fridolin SOMERS 05 Apr '18

05 Apr '18

Hi, Since Bug 20267 "Add basic .gitignore", there is a .gitignore in sources under GIT versionning. You may want to add more ignore globally with : https://help.github.com/articles/ignoring-files/#create-a-global-gitignore Or per repository with .git/info/exclude Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre - software and system maintainer

1 1

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

RFC for MARC holdings record support
by Ere Maijala 04 Apr '18

04 Apr '18

Hi Everyone, I've written an RFC for adding support for MARC holdings records, available here: <https://wiki.koha-community.org/wiki/MARC_Holdings_Records_RFC>. I'd be grateful for any feedback on this. I know there have been some initiatives to add (back) holdings records, but this proposal is a bit different in that it relies on the MARC format and I already have it working in a local custom branch apart from OPAC support. Regards, Ere -- Ere Maijala Kansalliskirjasto / The National Library of Finland

3 3

Koha Docs Webinar - LIVE
by Lee Jamison 31 Mar '18

31 Mar '18

Just a reminder about the Koha docs webinar is taking place now. I have set aside 17-19 UTC. Anyone who wishes to join, visit https://meet.jit.si/KohaDocsTeam -- Lee Jamison Automated Library Technician Marywood University 570-961-4586 ldjamison(a)marywood.edu

2 1

Koha Community Newsletter: March 2018
by Koha Newsletter 31 Mar '18

31 Mar '18

Fellow Koha users: The Koha Community Newsletter for March 2018 is here: https://koha-community.org/koha-community-newsletter-march-2018/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks!

1 0

new user presentation
by ck＠interleaf.ie 30 Mar '18

30 Mar '18

Hello My name is Carl, I'm a new member on this list. I have recently started working as a Developer for Interleaf - a company in Ireland providing services for libraries ( https://www.inter leaf.ie/ ). We want to give back to the Koha community, so I will be spending time on this mailing list and in Bugzilla, trying to do just that. I'm rather new to Koha, and will hang around in the background for a while to pick up on how things work around here. I've worked as a developer and with Linux & BSD systems for a few decades, and will take the time to ensure I respect your well documented guidelines. Cheers ck

5 4

Rescheduled meeting for Koha docs March meeting
by Lee Jamison 29 Mar '18

29 Mar '18

Hello all, since the meeting on the 22nd didn't come to pass (appears it was forgotten and I had an unplanned meeting at work to go to). Therefore, I'm going to reschedule it for tomorrow March 29th at 21 UTC. https://wiki.koha-community.org/wiki/Documentation_IRC_meeting_29_March_2018 Also of note in the agenda, I've scheduled the koha docs webinar I promised for March 30th. I've set aside 17-19 UTC for it to provide as much help as I can for those interested in attending. I'm figuring out the best way to do the webinar since a free zoom account only allows for one-on-one so I will provide that as soon as I figure out a solution (feel free to provide suggestions!) -- Lee Jamison Automated Library Technician Marywood University 570-961-4586 ldjamison(a)marywood.edu

2 1

User password reset question
by Graham, Stephen 27 Mar '18

27 Mar '18

Hi All - if I wanted to programmatically change a user's password what would the best way of doing this? I've just been looking at the various Perl modules for our version of Koha (16.11). modules such as C4:Members, C4:Member:Attributes etc, but cannot see any methods that can reset the password. Looking at the opac-passwd.pl CGI script which is called when changing a user password, I see that it uses a SQL update to change the password. Is this the best route to go if I wanted to change a password? Cheers, Stephen -------------------------------------- Stephen Graham Library Technology Consultant Content and Collections Team Library and Computing Services University of Hertfordshire Tel: 01707 286111 Ext: 77751 Email: s.graham4(a)herts.ac.uk

3 3