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 1 March 2016
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
- 1 March 2016, 15 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)
- Review coding guidelines
- New coding guidelines
- Reword/update coding guidelines
- [kfischer] Merge new PERL20 and PERL20.1 into PERL15
- [khall] Update JS4 based on the availability of the format method (from Bug 15662)
- [kfischer] 'PERL7: Definitions' - point to Terminology instead and note that terminology in the code should follow the default en GUI terminology?
- [marcelr] Code changes should adhere to naming conventions published elsewhere on the wiki (Patron versus Borrower, etc.)
- Remove/obsolete/archive coding guidelines
- [kfischer] 'PERL12: VERSION [Deprecated as of start of 3.12 release cycle] Each module should have a $VERSION variable to preserve progressive levels of compatibility with dependent code.' A bit confusing - should remaining VERSION variables be removed?
Action from last meeting: Verify if perlcritic complains about missing VERSION and figure out, if we want/can reconfigure it.- [mtompset] perlcritic does not complain about missing $VERSION until -2, but since we only perlcritic to -5, there is no need to keep this.
- [kfischer] 'PERL12: VERSION [Deprecated as of start of 3.12 release cycle] Each module should have a $VERSION variable to preserve progressive levels of compatibility with dependent code.' A bit confusing - should remaining VERSION variables be removed?
- Revamp/restructure coding guidelines page
- [khall] I would like to revamp our guidelines page in the manner of https://make.wordpress.org/core/handbook/best-practices/coding-standards/ I can start a new page for this which can be voted on at a later date if everyone approves of the idea.
- [kfischer] Divide coding guidelines into separate pages, for example: frontend, backend, database, and/or by language
- Any bugs that are in discussion
- Please add links to bugs and comments here...
- Bug 11081 (Moo vs. MooseX - should this be reverted - please see Kyle's comments on bug)
- General development discussion (Trends, ideas, ...)
- [Joubu] Merge borrowers and deletedborrowers tables
- Preventing XSS attacks. (Bug 13618) doesn't work - are there other options?
- [Joubu] Get rid of item-level_itype
- [kfischer] Performance issues: Benchmark for 3.22, Bug 15242
- Updates from the QA team
- Set time of next meeting
Apologies
Minutes
- Minutes: http://meetings.koha-community.org/2016/development_irc_meeting_1_march_2016.2016-03-01-15.04.html
- Minutes (text): http://meetings.koha-community.org/2016/development_irc_meeting_1_march_2016.2016-03-01-15.04.txt
- Log: http://meetings.koha-community.org/2016/development_irc_meeting_1_march_2016.2016-03-01-15.04.log.html