Koha Test Wiki MW Canasta on Koha Portainer

Test major Koha Wiki changes or bug fixes here without fear of breaking the production wiki.

For the current Koha Wiki, visit https://wiki.koha-community.org .

Development IRC meeting 13 December 2017

From Koha Test Wiki MW Canasta on Koha Portainer
Jump to navigation Jump to search

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

Agenda

  • Introductions (please use "#info" in front of your introduction to have it show up in the automatic minutes)
  • Announcements
  • Update from the Release manager (18.05)
  • Updates from the Release Maintainers
  • Updates from the QA team
  • General development discussion (trends, ideas, ...)
    • REST api: Proposal to vote for: allowing devs working on the REST api implementation to change attribute names so they are more meaningfull for api consumers. For example, rename 'borrowernumber' for 'patron_id'. Pros: we can provide a readable API spec, and people unfamiliar to Koha internals will have better time using the api. Cons: some people might be using the current (3) endpoints and would need to change some attribute names.
    • sql strict mode is now the default in MariaDB - https://mariadb.com/kb/en/library/sql-mode/ Do we continue closing our eyes or do we take care of the problems? Tasks: Wiki need to be updated
    • Elasticsearch status: https://wiki.koha-community.org/wiki/Elasticsearch_status#Elasticsearch_status_.28Updated_2017-12-07.29
    • Javascript in footer: many patches pushed to master now, some patches touching templates may need rebase
  • Review of coding guidelines
    • Don't use DBIX calls in updatedatabase (see Bug 19789, Bug 17292)
    • Reminder - git commit messages ('Bug 12345: ', '(follow-up)', '(QA follow-up)', see git log) + what the patch does vs what the bug is.
  • Set time of next meeting

Apologies

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

Minutes


Next meeting

Development_IRC_meeting_27_December_2017