Development IRC meeting 11 April 2018

Place

The #koha IRC channel (IRC server irc.oftc.net).

If you don't have an IRC client you can join the meeting using your web browser.

Time

11 April 2018, 14:00 UTC Time and Date.com converter for various local times

Agenda

Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
Announcements
- Roles for 18.11
Update from the Release manager (18.05)
Updates from the Release Maintainers
Updates from the QA team
General development discussion (trends, ideas, ...)
- REST api:
  - Vote: /acquisitions/orders
  - Vote: /acquisitions/funds
  - Vote: /acquisitions/vendors
  - Vote: /biblios
- Authentication
  - Oauth2 client credentials flow into 18.05. What needs to be done and if there's will to do it. Bug 20402 implements a basic approach to this. It's been proposed to tie the api keys to patrons, thus reusing the current permissions system. Work on scopes could be done later, but design decisions need to be made for long term stuffs like this. Julian wrote code already for managing api keys on a per-patron basis. This dev doesn't have much impact for existing feature, but having it opens the door for new requests for endpoints for easy integration with third party systems! Making Koha more appealable yet!
  - Way to authenticate patron for REST API - what about Bug 17004
Review of coding guidelines
Set time of next meeting

Proposed topics

Where to share feedback/info/tips about upgrades?

We noticed that due to bug 17196 (Move marcxml out of the biblioitems table) the upgrade to 17.05 needs something like 1GiB per 100k bibliographic records. And it's gonna take time (will share an estimate(with hardware details) once we try on a big instance)

So where to share these info? Or where we could have found them? (as we upgrade with more delay than most of the rest of the community)

The release notes
- No comment section enabled in the blog.
- Another idea would be to link in the release notes to a page on the wiki for these kinds of feedback. And maybe relink it in the section of a change for which we know in advance it can take time, resources, etc.
The dev mailing list: too hard to find these kind of feedback about upgrades in the number of messages (requires to scan up to almost 1.5 years of emails and the feedback would be scattered)
What are the other obvious places to search/stumble upon when preparing/doing an upgrade?

Victor Grousset - tuxayo 10:46, 8 March 2018 (EST), BibLibre

=> The what's on in koha-devel emails, easy.

Apologies

Please list your name here if you would like to attend but cannot make this meeting

Minutes

Next meeting

Development_IRC_meeting_25_April_2018