19:08:11 <kidclamp> #startmeeting Development IRC meeting 16 January 2019
19:08:11 <huginn> Meeting started Wed Jan 16 19:08:11 2019 UTC.  The chair is kidclamp. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:08:11 <huginn> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:08:11 <huginn> The meeting name has been set to 'development_irc_meeting_16_january_2019'
19:08:18 <kidclamp> #chair cait
19:08:18 <huginn> Current chairs: cait kidclamp
19:08:24 <kidclamp> #topic Introductions
19:08:39 <kidclamp> #info Nick Clemens, ByWater Solutions
19:08:41 <JesseM> #info Jesse Maseto, ByWater, USA
19:08:47 <davidnind> #info David Nind, Wellington, New Zealand
19:09:01 <khall> #info Kyle M Hall, ByWater Solutions
19:09:08 <cait> #info Katrin Fischer, BSZ, Germany
19:09:41 <kidclamp> #topic Announcements
19:10:12 <cait> QA and sign off academy patches!
19:10:17 <kidclamp> Kohacon 2019 call for proposals is open
19:11:28 <kidclamp> #info Academy ish papneing, please sign off and QA patches
19:11:36 <JesseM> Rmaint 18.05.x is going great!
19:11:38 <kidclamp> #info KohaCon 2019 call for proposals open
19:12:20 <kidclamp> #link https://www.interleaf.ie/kohacon19/ KohaCon2019 website
19:12:35 <kidclamp> #topic Updates from Release Manager (19.05)
19:12:59 <kidclamp> I am working on testing Mana and providing feedback to Alex - I want to push this early so appreciate any other eyes before I do so :-)
19:13:18 <kidclamp> Will hold off on pushing while I test but wil ctach up to bugs and academy asd soon as I can
19:13:29 <kidclamp> Thanks to all for their hard work, accounts and other things moving along nicely
19:13:31 <kidclamp> koha++
19:13:37 <kidclamp> Alll for me
19:13:47 <kidclamp> #topic Updates from the Release Maintainers
19:14:41 <kamar> Hello everyone
19:15:17 <kidclamp> #info 18.11 is coming alon, see notes form Koha meeting this morning
19:15:18 <kamar> I need to know if Koha can be install on Ubuntu Live ser
19:15:27 <kidclamp> #info 18.05 is going great
19:15:29 <JesseM> Working hard to keep up with Martin. :) But things are going great with 18.05.x
19:15:41 <kidclamp> #topic Updates from the QA team
19:15:44 <cait> kamar: yes, koha is fine on ubuntu. we are currently in a meeting, can you ask later?
19:16:00 <kidclamp> cait, all yours
19:16:04 <cait> ah
19:16:06 <cait> sec
19:16:21 <josef_moravec> #info Josef Moravec
19:16:29 <josef_moravec> sorry being late
19:16:41 <cait> so, we got the bad bugs down from 20 to 16 currently, but the queue is pretty full - 100
19:16:46 <kamar> I need to know if Koha can be install on Ubuntu Live server
19:17:05 <cait> 70 2 days ago... so calling out to the QA team to help fix that :)
19:17:29 <cait> 38 of those are bugs, so it would be good to take of those for the upcoming maintenance releases
19:17:59 <kidclamp> #info the queue is growing, please help with bugs especially for maintenance releases
19:18:20 <cait> we've got quite a bit of ILL and Elastic patches waiting too - anyone willing to help there is also welcome. Second sign offs are often good too - they make us more confident
19:18:33 <kidclamp> #info ES and ILL patches need attention as well
19:18:51 <cait> hm and recently SIP activity too
19:19:03 <cait> need someone for SIP :)
19:19:23 <cait> that's it from me
19:19:25 * kidclamp *cough* ashimema *cough* khall *cough*
19:19:38 <kidclamp> #topic General development discussion (trends, ideas, ...)
19:19:46 <khall> can do kidclamp , just remind me ;)
19:20:07 <kidclamp> #link https://wiki.koha-community.org/wiki/Public_patrons_password_endpoint_RFC REST API - Public route to change patron's password
19:20:14 <kidclamp> tcohen has asked for a vote
19:20:25 <kidclamp> any questions?
19:21:18 <cait> i was thinking password_2 might be confusing
19:21:27 <cait> maybe password_repeated?
19:21:39 <cait> does it make sense anyway to ask for it twice?
19:21:45 <aleisha_> thanks davidnind for testing so many academy patches!
19:21:48 <khall> that's what I was thinking
19:21:55 <cait> we can't really tell how the GUI will implment
19:21:57 <khall> confirming the password twice is a front-end process
19:22:01 <cait> yeah
19:22:05 <kidclamp> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22061
19:22:05 <huginn> 04Bug 22061: enhancement, P5 - low, 19.05, tomascohen, Signed Off , Public route to change password
19:22:13 <cait> i am fine with the old, it might make things easier
19:22:18 <cait> leave koha to verify
19:22:51 <khall> I think it's fine to have both there as well. It could make the form data directly pass-through
19:23:07 <cait> both = p1 and p1 or old and new?
19:23:38 <khall> new twice
19:23:52 <khall> we can't require the old password because it may be for a 'forgot your password' system
19:23:59 <josef_moravec> I am for repeated new password too,, we can't relly on client implementations...
19:24:12 <cait> but they can jus copy it?
19:24:24 <khall> cait: yeah, that was my point too
19:24:29 <khall> but in the end it does no harm
19:24:38 <cait> maybe mostly a question of what is required
19:24:53 <cait> i think the old password might be a good point
19:25:04 <cait> if it's a password forget process
19:25:09 <cait> forgotten
19:25:23 <cait> this is a little trickier than I expected :)
19:25:32 <josef_moravec> and also, if we have new password twice, clients implementation could be simpler...
19:25:45 <kidclamp> I think firget would be a separate process
19:25:59 <josef_moravec> yes, i think so too
19:26:23 <josef_moravec> and Koha should care about it not, some api consumer...
19:26:35 <cait> are we ok with password_2 or should we rename?
19:26:54 * khall has no strong opinion
19:27:07 <cait> it made it sound like a separate passwrod to me
19:27:10 * josef_moravec has no strong opinion too
19:27:14 <cait> th efirst... the second
19:27:16 <kidclamp> I don't mind either way
19:27:26 <cait> that's why i thought password_repeat might be more speaking
19:27:54 <cait> but I am ok with keeping it too or let tcohen decide
19:28:05 <kidclamp> description makes it clear I think
19:28:15 <kidclamp> okay, vote and mention that as a note?
19:28:18 <davidnind> make it more meaningful, sounds like naming something document 1, document 2 <-- not that I know anything about naming these things!
19:30:27 <kidclamp> Do we agree to adopt the public api for changing the password as outlined here:https://wiki.koha-community.org/wiki/Public_patrons_password_endpoint_RFC with the note that a more detailed attribute name would be aprreciated?
19:30:33 <kidclamp> I have to run, just trying to phrase
19:30:37 <kidclamp> I support it for the the record
19:30:39 <kidclamp> bye
19:31:28 <cait> sec
19:31:30 <cait> takig over
19:31:33 <cait> but my hand fell asleep heh
19:31:47 <cait> harder to type
19:32:08 <cait> #startvote Do we agree to adopt the public api for changing the password as outlined here:https://wiki.koha-community.org/wiki/Public_patrons_password_endpoint_RFC with the note that a more detailed attribute name would be aprreciated? (yes,no,abstain)
19:32:08 <huginn> Begin voting on: Do we agree to adopt the public api for changing the password as outlined here:https://wiki.koha-community.org/wiki/Public_patrons_password_endpoint_RFC with the note that a more detailed attribute name would be aprreciated? Valid vote options are , yes, no, abstain, .
19:32:08 <huginn> Vote using '#vote OPTION'. Only your last vote counts.
19:32:10 <davidnind> too much QAing!:)
19:32:13 <cait> #vote yes
19:32:24 <cait> more lying on the couch with the laptop :)
19:32:28 <davidnind> #vote yes
19:32:41 <josef_moravec> #vote yes
19:32:52 <JesseM> #vote yes
19:33:05 <cait> ending vote... last chance
19:33:07 <cait> #endvote
19:33:07 <huginn> Voted on "Do we agree to adopt the public api for changing the password as outlined here:https://wiki.koha-community.org/wiki/Public_patrons_password_endpoint_RFC with the note that a more detailed attribute name would be aprreciated?" Results are
19:33:07 <huginn> yes (4): davidnind, cait, JesseM, josef_moravec
19:33:22 <cait> ok
19:33:30 <cait> anything more for general development?
19:33:54 <cait> moving on!
19:34:05 <cait> #topic Review of coding guidelines
19:34:09 <cait> I suspect tcohen here too
19:34:59 <josef_moravec> tcohen++
19:36:00 <cait> it seems a bit incompleate - at least swagger 4
19:36:45 <cait> hard to tell for me... but I generally trust tcohen
19:36:49 <cait> should we vote?
19:37:53 <davidnind> I'd say yes
19:38:39 <josef_moravec> the proposed rules does make sense to me, and are not too complicated ;) but it would be great to have these things explicitaly written
19:38:45 <cait> #startvote Do we agree on the new coding guidelines Swagger 3.2, 3.3 and 3.4 as outlined on the wiki? (yes,no,abstain)
19:38:45 <huginn> Begin voting on: Do we agree on the new coding guidelines Swagger 3.2, 3.3 and 3.4 as outlined on the wiki? Valid vote options are , yes, no, abstain, .
19:38:45 <huginn> Vote using '#vote OPTION'. Only your last vote counts.
19:38:54 <cait> #vote yes
19:39:02 <cait> trustng the experts (including josef_moravec)
19:39:05 <josef_moravec> #vote yes
19:39:09 <khall> #vote yes
19:39:09 <davidnind> #vote yes
19:39:18 <JesseM> #vote yes
19:39:23 <cait> nice
19:39:26 <davidnind> what cait said :)
19:39:29 <cait> ending vote... last chance
19:39:33 <cait> #endvote
19:39:33 <huginn> Voted on "Do we agree on the new coding guidelines Swagger 3.2, 3.3 and 3.4 as outlined on the wiki?" Results are
19:39:33 <huginn> yes (5): davidnind, cait, JesseM, josef_moravec, khall
19:39:42 <cait> great, now i want to see thatmoving forward :)
19:39:59 <cait> issomeone aware of when the next meeting should be?
19:40:07 <cait> #topic Set time of next meeting
19:41:06 <cait> it looks ike we had 2 in december... and 2 in november
19:41:10 <cait> so every 2 weeks i guess
19:41:23 <cait> January 30
19:41:36 <cait> 14 UTC?
19:42:02 <josef_moravec> could be
19:42:23 <cait> #info Next meeting: 30 January 2019, 14 UTC
19:42:30 <cait> #endmeeting