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

KTD: Remote debugging (new way)
by Tomas Cohen Arazi 16 Jul '20

16 Jul '20

Maybe you've been following the latest German Perl Workshop 2020 news, but just in case, there's been an announcement of a full implementation of the Language Server protocol [1] for Perl [2]. As you can see in the langserver site, this is supported in most of the code editors available. I haven't managed to have the time yet to put all the things together so we can use it to develop Koha. If you have some ideas or time to discuss this, please let me know or share your ideas here so we can build an even better dev environment for Koha. Thanks! [1] https://langserver.org/ [2] https://github.com/richterger/Perl-LanguageServer/blob/master/docs/Perl-Lan… -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

String freeze for 19.11.x
by Aleisha Amohia 15 Jul '20

15 Jul '20

Hi all, String freeze will go into effect end of on Wednesday 15 July 2020 for the 19.11.x maintenance branch. 19.11.08 release scheduled for Wednesday 22 July 2020. Thanks -- *Aleisha Amohia* Koha Developer Catalyst IT - Expert Open Source Solutions

1 0

KTD: remote debugging (old way)
by Tomas Cohen Arazi 14 Jul '20

14 Jul '20

Hi all, I've tweaked koha-testing-docker so it has the same functionality we had for remote debugging in KohaDevBox. This means you can now use: * start_plack_debug * prove_debug Updated images are being pushed. I haven't had the time to update the README (PR welcome!) but the commit [1] explains how to set the URI mappings. <https://gitlab.com/koha-community/koha-testing-docker/-/commit/f01fae460127…> I use Komodo IDE for the task, currently. But this is what we've always used [2] with vdebug in Vim, etc. Looking forward for your feedback [1] https://gitlab.com/koha-community/koha-testing-docker/-/commit/f01fae460127… [2] https://wiki.koha-community.org/wiki/Debugging_in_VIM -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Merging of 'install Koha on Debian and Ubuntu' wiki pages
by Mason James 14 Jul '20

14 Jul '20

hi Folks i think it would be a good idea to merge the 2 following wiki pages... https://wiki.koha-community.org/wiki/Koha_on_Debian https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages my reasoning is that the procedure to install Koha on both Debian and Ubuntu (using .deb packages) is now identical currently each page has the same information - but presented differently, with inconsistencies what would be best is a single page that has consistent information for installing Koha on both operating systems any thoughts?

3 3

Coding Guideline proposal
by Joy Nelson 14 Jul '20

14 Jul '20

Hi all- At the last developers meeting I volunteered to draft a proposal on Inclusive Language to the Koha community coding guidelines. The proposal is below along with some reasons why we would want to do this as well as a couple of resources for those wanting to do a deeper dive into the topic. Thanks! Joy Proposed addition to the Koha community coding guidelines to cover Inclusive Language. https://wiki.koha-community.org/wiki/Coding_Guidelines#Terminology **proposed addition** TERM3: Inclusive Language Use inclusive language that promotes a community where everyone feels they are represented. Avoid terms that express or imply negative ideas that are racist, colonialist, or otherwise biased towards groups of people. Refer to the terminology list for terms to use/avoid. Example: Instead of using the term blacklist, use deny list which more accurately describes its function. **end proposed addition Explanation: At its best inclusive language promotes respectful relationships in a diverse community by allowing everyone to feel they are respected, represented, and welcome in the discussion. At a minimum inclusive language avoids offending others. In the U.S. (and possibly other countries) terms such as ‘blacklist’ reflect back the racist culture to the reader by equating the term black with 'bad' and white with ‘good’. The words we use in our communications have meaning, both explicit and implicit, and it’s important to consider how our words are being heard by others in our community. "Language is central to our experience of being human, and the languages we speak profoundly shape the way we think, the way we see the world, the way we live our lives." “How Does Our Language Shape the Way We Think”, Lera Boroditsky <https://www.edge.org/conversation/lera_boroditsky-how-does-our-language-sha…> Resources on race and language in the US and New Zealand: https://pdfs.semanticscholar.org/3868/15e565ec2d8191acb0dcb06ddb59c0780ef0.… Sites: New Series - Vol 13 No 2 2016 <http://dx.doi.org/10.11157/sites-vol13iss2id326> Accounts of Blatant Racism Against Māori in Aotearoa New Zealand by Sylvia Pack1, Keith Tuffin2 & Antonia Lyons Understanding Systemic Racism in America, Smithsonian Magazine <https://www.smithsonianmag.com/history/158-resources-understanding-systemic…> -- Joy Nelson President, Koha Division she/her ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

Call for news: July 2020 Koha Newsletter
by Koha Newsletter 13 Jul '20

13 Jul '20

I'm collecting news for the July newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Add Koha API Route to Proxy to Backend Service
by dcook＠prosentient.com.au 10 Jul '20

10 Jul '20

Hi all, I was chatting with lmstrand on IRC, and we both came up with separate features where we'd essentially want Koha to proxy our HTTP requests to the Koha API endpoint to a backend service running on the Koha server. What do people think about using the Koha HTTP API that way? Or would it just make more sense to run up Kong (or another API gateway) on the Koha server, and use it to proxy HTTP requests to backend services running on the Koha server? I think in both our cases Koha is itself only tangentially related. (lmstrand's is a SIP2 client daemon available over HTTPS, while mine is a OAI-PMH harvester daemon available over HTTPS) The advantage of using the Koha API is that it keeps everything together. The disadvantage is that we might not want to use Koha to proxy requests? The advantage of Kong is that it keeps a separation of concerns, Kong has a tonne of plugins that make working with APIs a great experience. The disadvantage is that it's yet another dependency. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 2

Looking for Sign Offs
by dcook＠prosentient.com.au 09 Jul '20

09 Jul '20

Hi all, I'm keen to get some sign offs for some small easy to test patches: * Bug 25950 - REMOTE_ADDR set to null if client_ip in X-Forwarded-For matches a koha_trusted_proxies value (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25950) * Bug 25672 - Administrators should be able to disable client-side plugin upload (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25672) Happy to trade sign offs. Actually looking for QA for the following as well, although I'm not sure what best to offer there. I wonder how much shipping is on chocolate or beer. * Bug 16357 - Plack error logs are not time stamped (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16357) Thanks! Hoping to have more plugin related patches coming in the near future, which should hopefully make managing plugins easier for vendors. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

3 2

Import biblios oaipmh endpoint RFC
by dcook＠prosentient.com.au 08 Jul '20

08 Jul '20

Hi all, At Katrin's request, I've drafted a little RFC for the API endpoint I want to make for importing OAI-PMH records into Koha as bibliographic records: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25905. I don't know if it's ready to go to a dev meeting or if people can give me feedback via email, but here you go: Referenced at: https://wiki.koha-community.org/wiki/REST_api_RFCs#Endpoints Found at: https://wiki.koha-community.org/wiki/Import_biblios_oaipmh_endpoint_RFC David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Plack down due to "GET http://swagger.io/v2/schema.json == Connect timeout"
by dcook＠prosentient.com.au 02 Jul '20

02 Jul '20

Hi all, As some people have noticed, http://swagger.io/v2/schema.json is currently unavailable, and this is causing new instances of Plack workers to crash. (New instances can be created by starting Plack or by long-running workers to reach their end of life number of requests.) The issue is detailed at length in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23653. I think the solution will be for Mason to a libjson-validator-perl package which contains a cached version of that file. Alternatively, I have copied the cached version into a patch and configured Koha to use that version instead of trying to go to http://swagger.io/v2/schema.json. I think that Mason distributing that updated package is probably the better solution, but I figure that it doesn't hurt to have options. I've tested my patch in koha-testing-docker and it worked well. Of course, while we wait for an updated package, you can also use the workaround that Mason has provided at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23653#c11. The "cache" in question isn't a real cache, so it won't get invalidated. It will persist for years, so once the workaround is done, your server should be safe. But new installs and unattended servers will need a more automated solution. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 3