Time  Nick          Message
00:08 mtompset      @seen Joubu
00:08 huginn        mtompset: Joubu was last seen in #koha 4 hours, 5 minutes, and 38 seconds ago: <Joubu> same for batch record edit
02:59 mtompset      Have a great day (24 hour period), #koha.
05:41 calire        morning #koha
05:59 fridolin      hiiii
06:02 magnuse       \o/
06:03 calire        hi magnuse
06:03 wahanui       kamelåså
06:03 magnuse       guten morgen calire
06:03 magnuse       wie geht's?
06:04 calire        ganz gut, danke :)
06:04 calire        and you?
06:06 cait          good morning all :)
06:10 rone          hello
06:10 wahanui       salut, rone
06:14 rone          some body there?
06:32 alex_a        bonjour
06:32 wahanui       hey, alex_a
06:37 reiveune      hello
07:04 magnuse       calire: busy...
07:05 calire        :)
07:36 gaetan_B      hello
07:36 wahanui       kia ora, gaetan_B
11:39 oleonard      Hi #koha
11:40 kidclamp      hi oleonard
11:40 wahanui       hi olé onard
11:51 calire        hi oleonard
11:51 wahanui       hi dear loon
13:27 marcelr       hi #koha
13:28 tcohen        Hi
13:29 Joubu         we have a new translation server :)
13:30 Joubu         "Fix critical errors 192,205"
13:30 Joubu         outhc
13:30 josef_moravec Hi marcelr, tcohen, Joubu
13:31 marcelr       o/
13:34 tcohen        bgkriegel++
13:42 Shane-S       So my Librarian is complaining that the system is slow...so I just ran in and she said its with circulation checkin and checkout
13:43 Shane-S       anything I can check to speed that up, running Koha 7.11 w/memcache running
13:43 Shane-S       KiB Mem :  8175032 total,  3084012 free,   821440 used,  4269580 buff/cache KiB Swap:  1003516 total,  1003516 free,        0 used.  7010336 avail Mem
13:46 * andreashm   waves
13:47 Joubu         Shane-S: go to the about page and search for warnings
13:47 caroline      hey all, is it just me or is the link "Guided reports wizard" in the reports page totally useless?  It only leads to a page where there are four button/links which are also on the main reports page
13:50 kidclamp      caroline, looks to be removed in master
13:50 caroline      I still see it, but I have not updated my master in a while
13:50 caroline      I will check
13:50 caroline      tahnks! :)
13:51 Shane-S       Joubu: I have this one...on SysInfo
13:51 Shane-S       You are missing the <template_cache_dir> entry in your koha-conf.xml file. That will bring a performance boost to enable it.
13:51 Shane-S       Would that make a huge impact?
13:52 Joubu         nope
13:52 Shane-S       Perl Modules I gave 6 red boxes...not sure they should eb addresses or not.
13:52 Joubu         nothing about plack?
13:53 Shane-S       Test::DBIx::Class (0.42),HTTPD::Bench::ApacheBench (0.73), Readonly::XS (0.01), WebService::ILS (0.17)
13:53 Shane-S       all not installed
13:53 Joubu         they are not mandatory
13:54 caroline      @kidclamp, wow, it looks really different! Thanks for pointing it out!
13:54 huginn        caroline: I'll give you the answer just as soon as RDA is ready
13:54 Shane-S       I have to fix the DBMS auto increment, but that is the only warning
13:54 kidclamp      Shane-S, do you have TrackLastPatronActivity enabled?
13:54 Joubu         you can try tunning the max_requests and number of workers
13:55 oleonard      Don't mind huginn, caroline, he just doesn't like it when you put the @ on someone's name
13:55 Shane-S       kidclamp: that a system pref, I will search it if so
13:55 caroline      that's what i figured... I'm not versed in irc codes
13:55 kidclamp      yes, system pref
13:56 caroline      Before coming to inlibro last fall, I hadn't used irc since the mid 1990's when the internet was just beginning
13:56 Shane-S       kidclamp: its is set to "Don't"
13:56 Joubu         dev meeting in few minutes
13:56 Joubu         qa_team?
13:56 wahanui       somebody said qa_team was alex_a jajm marcelr khall kidclamp tcohen josef_moravec
13:56 Joubu         rmaints?
13:56 wahanui       rmaints is probably kidclamp (17.11), fridolin (17.05), rangi (16.11)
13:57 oleonard      Oh you're with Inlibro, caroline? I didn't know that.
13:57 kidclamp      not sure then shane-s
13:57 caroline      yes, I replaced francois charbonnier
13:57 caroline      he's gone on to new challenges
13:57 Shane-S       Joubu: okay I will fix my auto increment issue and then check on the request and workers
14:00 Joubu         hope you all have cofe, tea, mate or anything with stimulant
14:01 thd           Joubu: Sleep is the best stimulant ;)
14:01 Joubu         #startmeeting Development IRC meeting 11 April 2018
14:01 huginn        Meeting started Wed Apr 11 14:01:37 2018 UTC.  The chair is Joubu. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01 huginn        Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01 huginn        The meeting name has been set to 'development_irc_meeting_11_april_2018'
14:01 Joubu         #topic Introductions
14:01 wahanui       #info wahanui, a bot that has become sentient
14:02 oleonard      #info Owen Leonard, Athens County Public Libraries, USA
14:02 Joubu         #info Jonathan Druart
14:02 marcelr       #info Marcel de Rooy, Rijksmuseum, NL
14:02 thd           #info Thomas Dukleth, Agogme, New York City
14:02 andreashm     #info Andreas Hedström Mace, Stockholm University Library
14:02 jajm          #info Julian Maurice, BibLibre
14:02 josef_moravec #info Josef Moravec, Municipal Library Ústí nad Orlicí, Czech Republic
14:02 cc_           #info Colin Campbell, PTFS-Europe
14:02 Joubu         #chair kidclamp
14:02 huginn        Current chairs: Joubu kidclamp
14:02 kidclamp      #info Nick Clemens, ByWater Solutions
14:03 kidclamp      in another meeting, may be slow
14:03 Joubu         nobody else?
14:03 Joubu         #topic Announcements
14:04 Joubu         #link https://wiki.koha-community.org/wiki/Development_IRC_meeting_11_April_2018
14:04 Joubu         ^ this is the agenda
14:04 Joubu         #info wiki page for the 18.11 roles is created - https://wiki.koha-community.org/wiki/Roles_for_18.11
14:04 Joubu         anyone has something to announce?
14:05 cait          #info Katrin Fischer, BSZ, Germany
14:05 calire        #info Claire Gravely, Germany
14:05 cait          sorry to be a little late
14:05 Joubu         no worries, do you have something to announce?
14:06 cait          only the roles page
14:06 Joubu         #topic Update from the Release Manager (18.05)
14:06 cait          you already did I think
14:06 cait          reading back quickly now
14:06 Joubu         I have announced several things at the last general meeting. Everybody reads the minutes so I do not need to repeat everything
14:07 Joubu         nothing new since last week
14:07 Joubu         #topic Updates from the Release Maintainers
14:07 Joubu         rmaints?
14:07 wahanui       i guess rmaints is kidclamp (17.11), fridolin (17.05), rangi (16.11)
14:07 fridolin      yep
14:07 fridolin      I continue Rmaint 17.05 after 18.05 release
14:08 fridolin      i will go to 17.05.18 max
14:08 kidclamp      just trying to catch up and push things
14:08 Joubu         #topic Updates from the QA team
14:09 cait          hard feature freeze is planned for 20th
14:09 cait          so we are busy
14:09 cait          we'll try to take car eof as many things as possible, but at the moment the queue is still around 70
14:09 cait          please rebase/follow-up really quickly if needed
14:10 Joubu         yes, please
14:10 Joubu         I am also dealing with 40 patches to push but waiting for answers on some of the reports
14:10 wahanui       okay, Joubu.
14:10 cait          if something doesn't apply I will fail it - because there is not much time to work on follow-ups myself
14:10 cait          don't take it personal :)
14:10 cait          yes, check your outstanding bugs for comments
14:11 cait          it's disappointing to spend time on reviewing and not hear back, especially with the deadline so close
14:11 cait          but lots of progress too right now, it's just a lot of things
14:11 cait          anyone else from QA?
14:12 marcelr       you said it all
14:12 Joubu         #topic General development discussion (trends, ideas, ...)
14:12 Joubu         #topic REST api
14:13 Joubu         Does anyone disagree with one of the 4 RDF?
14:13 Joubu         RFC
14:14 Joubu         there are:
14:14 Joubu         https://wiki.koha-community.org/wiki/Acquisitions_orders_endpoint_RFC
14:14 thd           There is an open issue in the wiki descriptionl.
14:14 Joubu         https://wiki.koha-community.org/wiki/Acquisitions_funds_endpoint_RFC
14:14 cait          I've left commetns on each
14:14 Joubu         https://wiki.koha-community.org/wiki/Acquisitions_vendors_endpoint_RFC
14:14 Joubu         https://wiki.koha-community.org/wiki/Biblios_endpoint_RFC
14:14 cait          some small things about names etc, butnothing big
14:14 Joubu         so 3 about ACQ and 1 for the bibliographic record endpoint
14:14 cait          like use tax instead of gst (like the gui does already)
14:14 thd           users vs patrons for acquisition funds which obviously do not apply to patrons.
14:15 cait          but you still use a patron_id i think?
14:15 cait          if we stick with terminology
14:15 cait          i am not sure we shoud mix, if it's all the same
14:16 cait          in koha you always link to a patrons record, staff is not separate, either use one term or the other
14:16 josef_moravec we should keep it consistant I think
14:16 thd           I understand the underlying problem is the original specification for Koha.
14:16 khall         #info Kyle M Hall, ByWater Solutions
14:17 thd           Every user is a patron.
14:17 andreashm     +1 for consistency
14:17 wahanui       i think +1 for consistency is drojf's only opinion
14:17 thd           I merely identify that there are open questions in what is proposed for voting.
14:17 Joubu         from the page "Note: it would be correct to pick users over patrons in this case. This should be voted, though."
14:18 Joubu         so I guess Tomas expected the discussion here and get a decision
14:18 thd           I presume that we take the examples as they are and issues such as users vs patrons are for some future prospect of reconsideration.
14:19 bag           #info Brendan Gallagher, ByWater
14:19 Joubu         any other concerns about these RFC?
14:19 Joubu         something that could be blocker?
14:19 thd           Having noted the outstanding issues, I am ready to vote on the proposed form as they stand in the wiki today.
14:20 bag           +1 on thd comment
14:20 greenjimll    #info Jon Knight, Loughborough University
14:20 cait          start vote?
14:20 Joubu         #chair cait
14:20 huginn        Current chairs: Joubu cait kidclamp
14:21 thd           We can revisit the outstanding issues in future as the opportunity arises.
14:21 cait          all in one or separate?
14:21 bag           all in one (imo)
14:22 thd           All in one without objection.
14:22 cait          ok
14:22 cait          the hardest part is always phrasing the question
14:22 cait          #startvote To vote: RFC endpoints for orders, funds and vendors in acq, biblios. Do you agree with the RFCs and comments as they are? (yes,no,abstain)
14:22 huginn        Begin voting on: To vote: RFC endpoints for orders, funds and vendors in acq, biblios. Do you agree with the RFCs and comments as they are? Valid vote options are , yes, no, abstain, .
14:22 huginn        Vote using '#vote OPTION'. Only your last vote counts.
14:23 greenjimll    #vote yes
14:23 Joubu         #vote abstain
14:23 cait          #vote yes
14:23 thd           #vote yes
14:23 cc_           #vote abstain
14:23 bag           #vote yes
14:23 jajm          #vote abstain
14:23 oleonard      #vote abstain
14:24 cait          giving it a few more seconds
14:24 cait          #endvote
14:24 huginn        Voted on "To vote: RFC endpoints for orders, funds and vendors in acq, biblios. Do you agree with the RFCs and comments as they are?" Results are
14:24 huginn        yes (4): greenjimll, cait, bag, thd
14:24 huginn        abstain (4): Joubu, oleonard, cc_, jajm
14:24 josef_moravec #vote yes
14:24 andreashm     #vote yes
14:24 marcelr       #vote yes
14:24 Joubu         toooo late guys
14:24 marcelr       haha
14:24 khall         #vote yes
14:24 cait          people, pay attention
14:24 thd           :)\
14:25 cait          #agreed RFCs for funds, vendors, orders and biblios have been agreed upon, no blocker concerns, write the code and then we adjust.
14:25 Joubu         my concerns, not about the RFC: REST API endpoints must be written with already moved code
14:25 Joubu         and ACQ code is not moved at all (even not started)
14:25 cait          #info 4 yes, 4 lates yes and 4 abstains
14:25 josef_moravec Joubu++
14:25 cait          Joubu: i see the conflict, but we need the apis for acq
14:26 Joubu         to me it will be very difficult to write orders (order lines) end points with the code we have in C4::Acq
14:26 cait          maybe it could be a separate discussion
14:26 Joubu         which is very shitty
14:26 Joubu         (I know I wrote big part of it)
14:26 cait          how to tackel them exactly
14:27 cait          shoudl we also vote patrons vs users?
14:27 cc_           yes lots of underlying issues in acq design
14:27 bag           would be good to vote on that cait
14:27 cait          can you help me phrase the question?
14:27 marcelr       cait: what is the link for that one ?
14:27 cait          i think at the moment it's if we shoudl use it on funds
14:28 cait          comment here: https://wiki.koha-community.org/wiki/Acquisitions_funds_endpoint_RFC
14:28 cait          Note: it would be correct to pick users over patrons in this case. This should be voted, though.
14:28 cait          funds can be linked to 1-many users that can 'use ' them
14:28 marcelr       yeah fund user sounds better than fund patron
14:28 cait          you still will link it to a patron record
14:28 cait          i thnk mixing might get difficult, but ready to abstain
14:29 bag           so cait you think having users in acqs and then having patrons on other areas of Koha - is too confusing?
14:29 cait          #startvote Should we use users instead of patron in the case of the funds RFC (users /patrons able to use a specific fund for odering)? (yes,no,abstain)
14:29 huginn        Begin voting on: Should we use users instead of patron in the case of the funds RFC (users /patrons able to use a specific fund for odering)? Valid vote options are , yes, no, abstain, .
14:29 huginn        Vote using '#vote OPTION'. Only your last vote counts.
14:29 greenjimll    #vote yes
14:29 cc_           #vote yes
14:29 Joubu         there is also the owner, so "users" and "owner" make perfect sense
14:29 cait          bag: it will still be patron_id I think
14:30 Joubu         #vote yes
14:30 marcelr       #vote yes
14:30 bag           right <thinking>
14:30 thd           #vote yes
14:30 oleonard      #vote yes
14:30 josef_moravec #vote abstain
14:30 bag           #vote yes
14:30 cait          #vote yes (turned by the argument of owners)
14:30 huginn        cait: yes (turned by the argument of owners) is not a valid option. Valid options are , yes, no, abstain, .
14:30 andreashm     #vote abstain
14:30 kidclamp      #vote yes
14:30 jajm          #vote yes
14:30 cait          #vote yes
14:30 * ashimema    catches up
14:30 cait          few more seconds
14:30 cait          people concentrate!
14:30 ashimema      #vote yes
14:31 marcelr       :)
14:31 cait          #endvote
14:31 huginn        Voted on "Should we use users instead of patron in the case of the funds RFC (users /patrons able to use a specific fund for odering)?" Results are
14:31 huginn        yes (11): Joubu, greenjimll, cc_, cait, kidclamp, oleonard, ashimema, jajm, marcelr, bag, thd
14:31 huginn        abstain (2): andreashm, josef_moravec
14:31 cait          #agreed We will users in the case of the funds RFC (11 yes, 2 abstain)
14:31 cait          done
14:31 cait          can someoen help with oauth?
14:31 Joubu         moving ong?
14:31 Joubu         #topic REST API Authentication
14:31 Joubu         jajm: ?
14:32 * ashimema    thinks we should say 'users everywhere in the api' as apposed to 'in this case'
14:32 cait          ashimema: that woudl mean changing already voted on rfcs which I'd wanted to avoid in this case
14:32 jajm          i think we need to discuss what to do with oauth2, scopes, and patron's permissions
14:32 cait          ashimema: something we can discuss later again
14:32 ashimema      is the api versioned yet
14:33 cait          jajm: how does the proposal work? i create an api-key for an existing patron, the permission the patron has will be used?
14:33 * ashimema    will refrain from asking questions now and have a catch up session with cait/tomas or someone later
14:33 cait          because that would sound ok for e right nwo
14:33 Joubu         As RM I'd like to know if we can expect to see this REST API auth work into 18.05 or if it is too late
14:33 greenjimll    With OAuth2, are we talking client-confidential flows? Using JWT tokens?
14:33 jajm          the code in bug 20402 only allow to define "API clients" in koha-conf.xml, not linked to any koha patron
14:33 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20402 enhancement, P5 - low, ---, julian.maurice, Failed QA , Implement OAuth2 authentication for REST API
14:34 jajm          greenjimll, client crendentials yes, no jwt tokens
14:34 cait          jajm: but how do you figure what they are allowed todo?
14:34 * ashimema    will read that code before commenting
14:35 cait          maybe that's the best approach to comment on the bug itself?
14:35 jajm          cait, as an example the code allow to define scopes for each API client (ex. "patrons.read"), the scopes needed to access a specific resource is defined in the swagger schema
14:35 greenjimll    jajm: The reason for not having JWT tokens? They're in common use (eg Google REST APIs)
14:36 jajm          greenjimll, i just wanted a minimal working implementation
14:36 cait          i think one of the basic questions is if we can finish something or 18.05
14:36 cait          my impression was that we haven't defined scopes yet, is that right?
14:36 jajm          cait, you're right
14:36 greenjimll    Isn't 18.05 freeze in 9 days? That's tight!
14:36 cait          yep
14:36 marcelr       too late..
14:36 cait          so is there something reasonable that we can do for 18.05
14:37 cait          i think people voiced a need for this in order to continue with implementing links with Coral
14:37 cait          which would be a good argument for me to provide something earlier than later, but not sure how doable it is
14:37 matts         links with anything outside of Koha itself, in fact
14:37 andreashm     Something that works better than cookies is needed. But other than that, I have no opinion on how it is built
14:38 jajm          i think the only thing we can do before feature freeze is to remove the "scopes" stuff, and tie an API client with an existing Koha patron, so that we can use the permissions the patron
14:38 andreashm     starting simple seems viable to me. doing something for 18.05 seems tight though.
14:38 josef_moravec If it is doable for 18.05 I am for it
14:38 andreashm     +1
14:38 matts         +1
14:38 thd           Do we allow backporting after release?
14:38 cait          +1 i think we need to offer something now
14:39 Joubu         who's working on bug 20402?
14:39 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20402 enhancement, P5 - low, ---, julian.maurice, Failed QA , Implement OAuth2 authentication for REST API
14:39 cait          jajm: do you have time to work on it?
14:39 cait          i think maybe also tomas, for qa we#d have to check then
14:40 jajm          Joubu, I will, if everyone agree
14:40 cait          josef_moravec: maybe you for qa? feasable?
14:42 * oleonard    watches everyone disappear
14:44 bag           hiya oleonard
14:45 * oleonard    wonders if half of the meeting is now taking place in an alternate dimension
14:46 thd           Was there another earthquake wherever OFTC houses its servers?
14:47 cait          i think the question was about how not to force everyone to discover the smae things :)
14:47 cait          like put a warning somewher that a specific database update needs a lot of time
14:47 cait          so you can plan ahead and are not surprised by it
14:47 Joubu         it's 2 meetings in a row with IRC explosion...
14:47 ashimema      release notes?
14:47 wahanui       release notes are in misc/release_notes
14:47 cait          they are already created when those things appear in part
14:47 cait          i think tht was tuxayo's point at least
14:47 oleonard      We meeting HARD, get used to it oftc
14:47 greenjimll    Is this warnings that we know about before release, or that become apparent afterwards?
14:48 cait          i think appratent afterwards was the issue
14:48 cait          but we shoul try to put all the important things int he release notes
14:48 Joubu         (resending some messages for the minutes)
14:48 Joubu         #action ashimema will read code of bug 20402 and give feedback on the bug report
14:48 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20402 enhancement, P5 - low, ---, julian.maurice, Failed QA , Implement OAuth2 authentication for REST API
14:48 Joubu         #action jajm will work on linking to existing patrons, tcohen and josef_moravec will test/qa
14:49 Joubu         #info jajm will take a look at the existing Mojolicious plugin (instead of using Net::OAuth2::.. directly)
14:49 cait          we got another dev meeting before release
14:49 cait          postpone this?
14:49 Joubu         About the updates - just assume than updates can be problematic, and test them on a test/pre-prod server
14:50 ashimema      +1
14:50 Joubu         but yes, we could highlight them in the release notes as well
14:50 cait          I think collect on a wiki page if it happens
14:50 marcelr       wiki page per release
14:50 ashimema      If a db update is likely to take hours then that's certainly something we can predict and put in the release notes I would say
14:50 cait          that problems/notes make sense after release
14:50 cait          yep
14:51 cait          set time and date of next meeting?
14:51 Joubu         it's very easy to know if it will be problmatic, just by reading the SQL queries in updatedb.pl
14:51 cait          #info try to already note long running db updates in the release notes properly
14:51 * ashimema    actually reads the wiki page of release note/upgrade path notes for Mojolicious versions.. something similar would certainly be helpful.
14:51 greenjimll    I was thinking more that if we knew something might take a long time up front, a warning could be included as part of the update process?
14:51 Joubu         if there is items/biblioitems, etc. it will certainly take ages
14:51 cait          Joubu: not everyone will understand them the way we do
14:51 cait          think a sysadmin that ususally not works on Koha or with sQL
14:51 cait          i know what tuxayo means
14:52 ashimema      a warning inlines in the updates won't help I think..
14:52 Joubu         I am just worried about the decisions/discussions we have in the meetings ;)
14:52 ashimema      - Hey, this thing we're about to do is going to take a while.. but we're not going to give you an option to postpone it
14:52 ashimema      not helpfull really is it ;)
14:53 Joubu         they are usually lost in blockholes
14:53 greenjimll    More helpful than silence.
14:53 Joubu         blackholes
14:53 ashimema      mm
14:53 cait          let's move on?
14:53 Joubu         1sec
14:53 Joubu         we talked about moving the print line of the updateDB *before* the execution
14:54 Joubu         that could give information on what is going on
14:54 ashimema      that would be nice
14:54 Joubu         (no idea if someone opened a bug report)
14:54 marcelr       or just occassionally print a extra line
14:54 Joubu         #topic  Set time of next meeting
14:55 Joubu         April 25th?
14:55 Joubu         Next meeting: 25 April 2018, 20 UTC?
14:55 cait          will be travelling
14:55 greenjimll    +1
14:55 calire        me too
14:55 Joubu         Next meeting: 25 April 2018, 21 UTC?
14:56 greenjimll    yes
14:56 Joubu         #info Next meeting: 25 April 2018, 21 UTC
14:56 Joubu          3
14:56 thd           Yes
14:56 Joubu          2
14:56 Joubu          1
14:56 Joubu         #endmeeting
14:56 huginn        Meeting ended Wed Apr 11 14:56:27 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
14:56 huginn        Minutes:        http://meetings.koha-community.org/2018/development_irc_meeting_11_april_2018.2018-04-11-14.01.html
14:56 huginn        Minutes (text): http://meetings.koha-community.org/2018/development_irc_meeting_11_april_2018.2018-04-11-14.01.txt
14:56 huginn        Log:            http://meetings.koha-community.org/2018/development_irc_meeting_11_april_2018.2018-04-11-14.01.log.html
15:00 reiveune      bye
15:01 oleonard      Joubu++
15:01 oleonard      Thanks for chairing
15:05 Joubu         @later tell marcelr Koha::Cache::Memory::Lite is not buggy, it's flushed correctly
15:05 huginn        Joubu: The operation succeeded.
15:17 oleonard      Thanks for the signoff on Bug 18791 calire!
15:17 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18791 enhancement, P5 - low, ---, kyle, Signed Off , Add the ability for librarians to easily copy, download or print DataTables based tables in Koha
15:20 calire        you're welcome
15:22 tuxayo        cait++
15:23 tuxayo        Thanks for developing on the issue that I wrote about for the meeting. Too bad I missed the date.
15:27 Joubu         tuxayo: how did you miss it?
15:27 Joubu         seen the Koha calendar?
15:27 wahanui       I haven't seen 'the', Joubu
15:28 * ashimema    is getting angry whilst reading ::Objects code
15:33 tuxayo        lol wahanui
15:33 tuxayo        Joubu: I wrote about this the 8 march when the meeting was planned for the 15 march. I didn't keep track of when it was rescheduled.
15:36 Joubu         ashimema: hum? Can you be more explicit?
15:38 Shane-S       So...I can't duplicate this off-site, but a user called me saying doing check-in / checkout they keep getting the "add Message" pop coming up and that checking the immediately show checkouts box isn't enabled across patrons
15:38 Shane-S       Is there anything aside from a browser cache issue that would cause that?
15:46 Shane-S       on another matter...I did the auto increment files, and tailed the logs...got no errors, but the SysInfo page still says I have auto-increment issues...do I have to re-boot the whole server?
15:46 Shane-S       I followed https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix
15:48 Shane-S       I should not my my.cnf did not have a [mysqld] directive, I added that and 2 init-file= lines as I have 2 instances
15:58 Joubu         Shane-S: re-read the page, you need to fix the "corrupted data" first
16:01 Shane-S       ...uhh...as in just purge the records or what?
16:08 Joubu         Shane-S: what tells the about page?
16:08 Shane-S       I got it...I saw the bug 19016 reference and didnt read next line
16:08 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19016 major, P5 - low, ---, jonathan.druart, In Discussion , Add a script to fix corrupted data
16:08 Shane-S       one possible fix is to delete the entries in the deleted* and old* tables matching the IDs listed on the about page.
16:09 Shane-S       Sorry to be a PITA with missing that line
16:11 tcohen        hi
16:11 wahanui       hi, tcohen
16:13 Joubu         Shane-S: you are going to lose data but yes it's the easiest fix. It depends on the number of corrupted rows you have
16:13 Shane-S       1 for 1 instance, and 4 in another instance
16:16 Joubu         from old_issues? or something else?
16:17 Shane-S       deleteditems (1 koha & 2 woodburhts) and old_reserves (2 woodburyhts) those are instance names
16:18 Shane-S       i deleted all the record in the the deleted and old tables
16:18 Shane-S       well the reported issues record
16:18 Shane-S       not *all* that was poor word choice
16:19 Shane-S       okay warning page just have the <template_cache_dir> warning and that is it
16:22 Shane-S       Anyone recommend a good image paste bin...FFx is rendering the OPAC odd at the top...is a blue bar over the header image and menu bar
16:27 Joubu         Shane-S: https://lut.im/
16:28 Shane-S       actually nm...just one instance, I have to check my custom CSS
16:28 Shane-S       ty though
16:29 tcohen        Joubu: are the release notes rebuilt regularly for us to take a look?
16:31 Joubu         yes
16:32 Joubu         I regenerate them just after pushing stuffs
16:34 pastebot      "tcohen" at 200.16.23.4 pasted "Joubu: the orders endpoint controller" (336 lines) at http://paste.koha-community.org/208
16:35 tcohen        Joubu: that's only to show that current Koha::Acquisition::Order(s) code is perfectly suitable for implementing the orders endpoint as-is
16:35 tcohen        the only problem I'm facing is that other Koha::Object-based classes behave differently regarding DBIC exceptions, and I think we should make it behave as the others
16:35 tcohen        for consistency
16:37 * tcohen      adds that this controller is not ready because there's the idea to make it automatically create baskest if no basket_id is passed (Coral use cases)
16:41 tcohen        release notes?
16:41 wahanui       release notes are in misc/release_notes
16:48 Joubu         https://gitlab.com/koha-community/koha-release-notes/blob/master/release_notes_17_12_00.md
16:49 Joubu         hum, buggy
16:55 Shane-S       grr..I can't find the right CSS element to change the header background from black to a gradient...
16:56 Shane-S       tried .navbar div.navbar #header-region all get over-ridden
17:07 Shane-S       Anyone know what OPAC CSS class is giving the Koha nav bar (top bar) the black color
17:07 Shane-S       I can't find it with Chrome Inspector
17:08 Shane-S       only black I am finding is for color: #33333; in the Body{} and that should be for font colors
17:12 Joubu         black? it's all blue
17:16 Joubu         khall: ping on bug 12123, can you share an example that breaks the display/js please?
17:16 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12123 normal, P5 - low, ---, kyle, Passed QA , HTML notices can break the notice viewer
17:22 Joubu         @later tell kidclamp did not you write a patch to remove the ability to delete "core" notice templates?
17:22 huginn        Joubu: The operation succeeded.
17:24 oleonard      Shane-S: .navbar-inverse .navbar-inner { background: linear-gradient(to bottom,#194e87 0,#0f3666 100%); }
17:32 Joubu         kidclamp: bug 20562 is major, right? regression?
17:32 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20562 normal, P5 - low, ---, kyle, NEW , issue_id is not stored in accountlines for rental fees
17:33 khall         Joubu: kidclamp working on a patch right now
17:33 Joubu         ok
17:34 Shane-S       Joubu: http://library.npelem.com/ I see black on MacBookPro
17:35 Shane-S       oleonard: TY! http://whes.npelem.com/ works
17:36 Joubu         heh... opac... sorry
17:37 Shane-S       np, figured that was what you meant with all blue...but I also pulled my data from a 3.20 install...so wasn't sure of a color preference carried over
17:38 * tcohen      uploaded an image: image.png (245KB) <https://matrix.org/_matrix/media/v1/download/matrix.org/iBurjsraiATnGHqdrCHrcqml>
17:39 Shane-S       There anyway to send donations like coffee/beer money to the project?
17:40 Shane-S       Only because I feel bad as I don't contribute and I have used Koha now for 4 years in my building
17:40 tcohen        Shane-S: kohacon18?
17:41 Joubu         Shane-S: test patches!!
17:41 Joubu         join the documentation team
17:42 oleonard      Mail cookies to developers!
17:42 Joubu         Shane-S: https://wiki.koha-community.org/wiki/Getting_involved
17:42 khall         Joubu: kidclamp patch for 20562 is up
17:43 Shane-S       bug 7646 I have tried :)
17:43 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7646 enhancement, P5 - low, ---, ssammons, Failed QA , Printing w/o the SQL Code showing
17:44 Shane-S       Just never have time to code much I have 300 kids breaking chromebooks all day :)
17:44 Shane-S       I had to use Easter Break to migrate the server, where will KohaCon 2018 be?
17:45 Shane-S       Any chance North Carolina (I want to take a trip down there anyway)
17:45 oleonard      Portland, Oregon
17:45 oleonard      So, maybe it's on the way?
17:46 tcohen        Shane-S: http://kohacon2018.bywatersolutions.com/
17:46 Shane-S       Not...quite...Im in New Jersey....but maybe
17:46 tcohen        we pick a different continent each year
17:47 tcohen        Shane-S: you still owe those cookies, you better think seriously about it
17:47 tcohen        he
17:49 Shane-S       well I have to give some to damn near the whole channel...plane ticket and pizzas might be cheaper in Portland
17:49 Shane-S       who am I kidding, I have a 2yr old and a newborn, my wife isn't letting me go anywhere unless she is set free too :)
17:55 Joubu         #action Shane-S send cookies to the whole channel
18:45 Joubu         josef_moravec: "with ISE"?
18:46 josef_moravec Joubu: yes, i was looking into developer tools/network panel, ajax calling of /svc/letters/preview returns 500 Internal server error
18:50 Joubu         josef_moravec: got it, thanks!
18:50 josef_moravec Joubu: great
18:53 roch          Is the qa-tools supposed to tell me if my commit messsages are invalid ? I ran the tools on my commits for this issues https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12747 but it showed no errors
18:53 huginn        Bug 12747: enhancement, P5 - low, ---, david.bourgault, Failed QA , Add extra column in Z3950 search result
18:53 oleonard      Bug 12747 - Add extra column in Z3950 search ...should be: Bug 12747: Add extra column in Z3950 search
18:53 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12747 enhancement, P5 - low, ---, david.bourgault, Failed QA , Add extra column in Z3950 search result
18:54 oleonard      colon instead of hyphen
18:55 roch          woops! I missed that. Thanks :)
18:56 Joubu         josef_moravec: follow-up submitted. But... if you are going to PQA it, you should ask oleonard to rebase bug 18007
18:56 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18007 enhancement, P5 - low, ---, oleonard, Signed Off , Interface updates to notices and notice previews
18:56 oleonard      Easy to miss
18:57 Joubu         roch: did you update the qa-tools repo?
18:57 oleonard      Bye all
19:02 Joubu         khall: I do not understand your answer on bug 20562, but just realised I made a typo, it was "or", not "of"
19:02 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20562 normal, P5 - low, ---, kyle, Needs Signoff , issue_id is not stored in accountlines for rental fees
19:03 Joubu         I wanted to know if it was a regression (in that case we should find the cause) or if the problem exists since issue_id has been added to this table (long time ago iirc)
19:03 khall         Joubu: it's a bug, but not a regression
19:03 Joubu         since 3.22 then, that's bad
19:03 khall         you are exactly right, it we never implemented when issue_id was added to accountlines
19:06 roch          Joubu using qa-tools from github, I tried to update but nothing new. last commit was on 2014-08-18 13:07 , is there a more recent version somewhere?
19:07 Joubu         outch, yes, a lot
19:07 Joubu         a lot of commits
19:07 Joubu         https://gitlab.com/koha-community/qa-test-tools
19:07 Joubu         qa-test-tools is https://gitlab.com/koha-community/qa-test-tools
19:07 Joubu         qa-tools is https://gitlab.com/koha-community/qa-test-tools
19:07 Joubu         qa-tools?
19:08 Joubu         wahanui: qa-tools?
19:08 Joubu         wahanui: hi stupid bot!
19:08 wahanui       well, qa-tools is https://gitlab.com/koha-community/qa-test-tools
19:08 wahanui       qa-tools is https://gitlab.com/koha-community/qa-test-tools
19:08 wahanui       Joubu: i'm not following you...
19:09 Joubu         yes, too slow
19:10 Joubu         not stupid, just slow. Sorry wahanui
19:10 roch          OK thanks! We were up to date with the version on github - from 2014!!
19:12 Joubu         it has been announced on the list I think
19:51 bag           @seen cait
19:51 huginn        bag: cait was last seen in #koha 4 hours, 56 minutes, and 10 seconds ago: <cait> will be travelling
19:51 bag           ahh
19:54 huginn        News from kohagit: Bug 19289: DBRev 17.12.00.027 <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=55abcbee5323b16071392cdc3f0dc38b0f1c3cfe>
19:54 huginn        News from kohagit: Bug 18674: (QA follow-up) Add date and time <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=9a3d12e35e20766a2175c68f870a48058a25d6ec>
19:55 huginn        News from kohagit: Bug 19904: (follow-up) Add Nick Clemens as RM assistant <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=b9b824559d336150afb27836c2c8e36ca3ad4900>
19:55 huginn        News from kohagit: Bug 20552: Fix HTML tag for search facets <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=dd0469132cf5aee7fded7e69949b4e6e2e54694b>
19:55 huginn        News from kohagit: Bug 19289: (follow-up) Add existing fields to the ACQ framework <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=ad2b04001fe3100a5caeafbbdd5ea56a6ff65e1a>
19:55 huginn        News from kohagit: Bug 19904: Release team for 18.05 <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=5e41df9101667304a09da007e7ef1104c4fdfeb6>
19:55 huginn        News from kohagit: Bug 20540: (follow-up) Remove debug line <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=ccc71f6cf13334d554cad74ae85df2e8be3e3649>
19:55 huginn        News from kohagit: Bug 20540: Fix TransformHtmlToXml if last tag is empty <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=cc8f3dc1cc046ecd7d53349091fbba864dfb91c9>
19:55 huginn        News from kohagit: Bug 19289: Extend size of inputs to 50 <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=198096ffab71ced1aa6ce453ee5c08fc43d0b5d3>
19:55 huginn        News from kohagit: Bug 20536: (ILL) authnotrequired should be explicitly unset on opac <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=84d6c23eddf8744a61e06432b0f443753138d7f2>
19:55 huginn        News from kohagit: Bug 20518: Don't show "Messages" header and link on patron details if there are no... <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=f3b8f17395f05548c87129d286a3f49d0b171e0b>
19:55 huginn        News from kohagit: Bug 19289: Use copyrightdate instead of publicationyear for MARC21 <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=30faa632e95362e0f80cf42f9fa37e96047e4a74>
19:55 huginn        News from kohagit: Bug 20104: Update minimum version of Perl to 5.20 <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=4218875ec039dc375124f969caea1624399c21a4>
19:55 huginn        News from kohagit: Bug 19289: Use jQuery validate plugin <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=946d5bcdd2ccaefaba2596b8be1278781d1cc482>
19:55 huginn        News from kohagit: Bug 9634: Allow for combining same paraneters in SQL reports <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=8acf5912b3fd213b8bcb3e7ee9b47f7cb086002b>
19:55 huginn        News from kohagit: Bug 19538: Move EnableAdvancedCatalogingEdtor from 'Labs' to 'Cataloging' <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=999f2ed7e9e56dda254308f9bbbc85dcc66a160c>
19:55 huginn        News from kohagit: Bug 18625: (QA follow-up) Unit tests <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=5e9c703d2bef25f7ada760952d3e070203376a05>
19:55 huginn        News from kohagit: Bug 19289: Add existing fields to the ACQ framework <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=d632da51c80f9c4215c6952793353803038d98d3>
19:55 huginn        News from kohagit: Bug 19289: Use the ACQ framework to display bibliographic details <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=84ce1fb5921cdddf2368f0c330dede0f602742d0>
19:55 huginn        News from kohagit: Bug 18625: (QA follow-up) Simplify update_lastseen <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=d8b6fde9b7f59ba32f4726f55acb6f803c7816d6>
19:55 huginn        News from kohagit: Bug 18625: Update lastseen in patron info request <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=654d8c0cfd6cd2643e2deed7bb18618ea740cace>
20:25 cait          helo
20:25 cait          hello even
20:25 cait          did i miss it?
20:30 jenkins       Project Koha_Master_D8 build #429: UNSTABLE in 32 min: https://jenkins.koha-community.org/job/Koha_Master_D8/429/
20:30 jenkins       * kyle: Bug 20123: Allow multiple instances of Koha to have different timezones
20:30 jenkins       * kyle: Bug 20123: (QA follow-up) If tz is 'local', no need to tell database to
20:30 jenkins       * kyle: Bug 20123: Add commented out example to koha-conf.xml
20:30 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20123 enhancement, P5 - low, ---, kyle, Pushed to Master , Allow multiple instances of Koha to have different timezones on the same server
20:30 jenkins       * Tomás Cohen Arazi: Bug 20123: Make the timezone entry empty and uncommented by default
20:30 jenkins       * mtompset: Bug 18674: Added timezone information to about page
20:30 jenkins       * mtompset: Bug 18674: Allow TZ SetEnv for plack
20:30 jenkins       * Tomás Cohen Arazi: Bug 18674: Style changes to match other entries
20:30 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18674 enhancement, P5 - low, ---, mtompset, Pushed to Master , Show timezone for Perl and MySQL on the About Koha page
20:30 jenkins       * Tomás Cohen Arazi: Bug 18674: TZ error handling
20:30 jenkins       * Tomás Cohen Arazi: Bug 18674: (QA follow-up) Add date and time
20:30 jenkins       * Nick Clemens: Bug 9634: Allow for combining same paraneters in SQL reports
20:30 jenkins       * oleonard: Bug 20518: Don't show "Messages" header and link on patron details if
20:30 jenkins       * Nick Clemens: Bug 19538: Move EnableAdvancedCatalogingEdtor from 'Labs' to
20:30 jenkins       * claire.gravely: Bug 20552: Fix HTML tag for search facets
20:30 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9634 enhancement, P5 - low, ---, nick, Pushed to Master , Allow for parameters re-use on SQL reports
20:30 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20518 enhancement, P5 - low, ---, oleonard, Pushed to Master , Don't show "Messages" header and link on patron details if there are no messages
20:30 jenkins       * martin.renvoize: Bug 20536: (ILL) authnotrequired should be explicitly unset on opac
20:30 jenkins       * mtompset: Bug 20104: Update minimum version of Perl to 5.20
20:30 jenkins       * Nick Clemens: Bug 18625: (QA follow-up) Unit tests
20:30 jenkins       * colin.campbell: Bug 18625: Update lastseen in patron info request
20:31 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19538 enhancement, P5 - low, ---, nick, Pushed to Master , Advanced editor - Rancor - Move syspref from labs to cataloging and remove experimental note
20:31 jenkins       * m.de.rooy: Bug 18625: (QA follow-up) Simplify update_lastseen
20:31 jenkins       * Jonathan Druart: Bug 20540: Fix TransformHtmlToXml if last tag is empty
20:31 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20552 minor, P5 - low, ---, claire_gravely, Pushed to Master , Fix HTML tag for search facets
20:31 jenkins       * katrin.fischer: Bug 20540: (follow-up) Remove debug line
20:31 jenkins       * Jonathan Druart: Bug 19289: Add existing fields to the ACQ framework
20:31 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20536 trivial, P5 - low, ---, martin.renvoize, Pushed to Master , ILL: authnotrequired not explicitly unset
20:31 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20104 trivial, P5 - low, ---, mtompset, Pushed to Master , Update minimum version of Perl to 5.20
20:31 jenkins       * Jonathan Druart: Bug 19289: Use the ACQ framework to display bibliographic details
20:31 jenkins       * Jonathan Druart: Bug 19289: Use jQuery validate plugin
20:31 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18625 enhancement, P5 - low, ---, colin.campbell, Pushed to Master , Update borrower last seen from SIP
20:31 jenkins       * Jonathan Druart: Bug 19289: Use copyrightdate instead of publicationyear for MARC21
20:31 jenkins       * Jonathan Druart: Bug 19289: Extend size of inputs to 50
20:31 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20540 enhancement, P5 - low, ---, jonathan.druart, Pushed to Master , TransformHtmlToXml can duplicate </datafield>
20:31 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19289 new feature, P5 - low, ---, jonathan.druart, Pushed to Master , Allow configuration of the fields on the 'Catalog details' form in the acquisition baskets
20:31 jenkins       * Jonathan Druart: Bug 19289: (follow-up) Add existing fields to the ACQ framework
20:31 jenkins       * Jonathan Druart: Bug 19289: DBRev 17.12.00.027
20:31 jenkins       * m.de.rooy: Bug 19904: Release team for 18.05
20:31 jenkins       * m.de.rooy: Bug 19904: (follow-up) Add Nick Clemens as RM assistant
20:31 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19904 enhancement, P5 - low, ---, m.de.rooy, Pushed to Master , Release team 18.05
21:01 * LeeJ        waves
21:01 LeeJ          hi #koha
21:01 LeeJ          cait: I'm around now :)
21:01 LeeJ          haha
21:01 davidnind     waves
21:01 LeeJ          hi davidnind
21:01 cait          hi all
21:01 LeeJ          just catching my breath and we'll start in a sec :)
21:01 davidnind     hi all as well
21:01 clintD        good morning
21:01 wahanui       well, it's morning somewhere, yes
21:01 cait          my internet connection is not very stabl
21:01 cait          e
21:02 cait          i might get kicked out, but hope not
21:02 LeeJ          cait: no worries :)
21:02 LeeJ          shall we begin?
21:02 Joubu         #startmeeting Documentation IRC meeting 11 April 2018
21:02 huginn        Meeting started Wed Apr 11 21:02:30 2018 UTC.  The chair is Joubu. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02 huginn        Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:02 huginn        The meeting name has been set to 'documentation_irc_meeting_11_april_2018'
21:02 Joubu         #topic Introductions
21:02 wahanui       #info wahanui, a bot that has become sentient
21:02 Joubu         #chair LeeJ
21:02 huginn        Current chairs: Joubu LeeJ
21:02 Joubu         #chair cait
21:02 huginn        Current chairs: Joubu LeeJ cait
21:02 Joubu         #info Jonathan Druart
21:02 LeeJ          #info LeeJ, Marywood University
21:03 georgew       #info George Williams, Northeast Kansas Library System
21:03 davidnind     #info David Nind, Wellington, New Zealand
21:03 cait          #Katrin Fischer, BSZ, Germany
21:03 caroline      #info Caroline Cyr La Rose, inLibro
21:03 clintD        #Clint Deckard, Anact, New Zealand
21:03 LeeJ          #topic What's been done so far
21:04 Joubu         #link https://wiki.koha-community.org/wiki/Documentation_IRC_meeting_11_April_2018
21:04 LeeJ          #info documentation (GitLab) training webinar was held as scheduled per last meeting's minutes by LeeJ
21:04 indradg       #info Indranil Das Gupta, L2C2 Technologies, India.
21:05 LeeJ          hello all :)
21:05 LeeJ          has anyone not been added to the kohadocs Taiga who wishes to be?
21:05 Joubu         #link https://tree.taiga.io/project/ldjamison-kohadocs-1805/
21:06 LeeJ          I'll take the silence as a no :)
21:06 LeeJ          #topic Workflows
21:07 LeeJ          Joubu cait I was hoping for brief clarification..how has it been handled in the past when a docs bug has been filed for the documentation but also might apply to the code base?
21:07 LeeJ          Bug 20555
21:07 LeeJ          as an example
21:08 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20555 enhancement, P5 - low, ---, koha-bugs, NEW , usage() function in cleanup_database.pl needs refactoring
21:08 LeeJ          whoops! wrong bug xD
21:08 LeeJ          actually that was right
21:09 Joubu         there is a "Manual" keyword
21:09 Joubu         I'd use it to tell the documentation team needs to adapt the manual
21:09 LeeJ          okay
21:10 LeeJ          because I'm taking the time right after the meeting to updating the edit the manual wiki with a proper procedure
21:10 tcohen        Joubu: added a followup on bug 20123
21:10 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20123 enhancement, P5 - low, ---, kyle, Pushed to Master , Allow multiple instances of Koha to have different timezones on the same server
21:12 cait          :(
21:12 LeeJ          hmm..anyone have a suggestion on how to update cleanup_database.pl per the bug/process of it?
21:12 davidnind     that will be useful, just trying to work through the workflow - will try with something easy first, then get stuck in
21:13 * cait        gets out the duct tape
21:13 LeeJ          davidnind: I'm always available to assist
21:13 tcohen        @seen Joubu
21:13 huginn        tcohen: Joubu was last seen in #koha 3 minutes and 53 seconds ago: <Joubu> I'd use it to tell the documentation team needs to adapt the manual
21:13 cait          LeeJ: i tihnk fix the script first, manual second
21:13 LeeJ          cait: right
21:14 davidnind     virtual duck tape, does it exist, where can I buy some?
21:15 LeeJ          Joubu: I think it would be your call on how best to word the -m flag..I'll admit I'm somewhat confused how it should be updated
21:15 huginn        News from kohagit: Bug 20123: (follow-up) Mock timezone in t/Auth_with_shibboleth.t <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=e5229fd68b13e69b47349e9b5c986a6243ee69c6>
21:16 Joubu         LeeJ: let's talk about it on the bug report later ;)
21:16 LeeJ          I want to thank barton for providing that bug..we can use it as training :)
21:16 LeeJ          Joubu: sounds good
21:16 LeeJ          I digress
21:17 LeeJ          #info LeeJ will update the Editing the Manual wiki page with a standardized workflow for handling documentation/documentation bugs
21:18 LeeJ          #info Joubu is still in need of feedback on Bug 19817
21:18 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19817 new feature, P5 - low, ---, jonathan.druart, Needs Signoff , Merge local and online documentations
21:18 LeeJ          anything to add from anyone before the next topic?
21:19 LeeJ          #topic Next steps
21:20 LeeJ          #info LeeJ will be sending out a Doodle poll to schedule a sprint day to hopefully get everyone organized..whatever day is picked he will make himself available the whole day
21:21 Joubu         Where can we see the progress on documentation of the 18.05 new features?
21:21 davidnind     excellent idea!
21:21 cait1         :)
21:21 cait1         if you pick a day after 20th i will try to join
21:21 caroline      it would be before the 18,05 release?
21:22 LeeJ          Joubu: I'll bang out the details of that when I get home from work because I needed to pick your brain on that very topic
21:22 LeeJ          caroline: yes :)
21:22 LeeJ          the goal of the sprint day is to catch the documentation up to the current status of the 18.05 code base
21:23 LeeJ          dotting our i's and crossing our t's so to speak
21:23 davidnind     I guess it should be in Taiga, I can go through and add all the bugs from Bugzilla for 18.05 commits
21:24 caroline      +1
21:24 cait1         davidnind++
21:24 LeeJ          davidnind that would be a big help
21:24 LeeJ          davidnind++
21:24 davidnind     then we can make sure the release notes are covered off for each item
21:24 davidnind     will start on this this evening
21:24 cait1         davidnind: i think there are some preliminary release notes you could use as base
21:24 LeeJ          I like the way you think :)
21:25 cait1         Joubu: does the page still exist?
21:25 Joubu         since the beginning of the release cycle, yes
21:25 barton        #info Barton Chittenden, BWS
21:25 Joubu         release notse?
21:25 Joubu         release notes?
21:25 wahanui       release notes are in misc/release_notes
21:25 davidnind     they are always a good starting point, will probably need some tweaking to reflect how people use Koha
21:25 LeeJ          :O
21:25 barton        (better late than never)
21:25 Joubu         release notes is https://gitlab.com/koha-community/koha-release-notes/blob/master/release_notes_17_12_00.md
21:25 cait1         Joubu: lost the link :(
21:26 davidnind     the new features and enhancements will probably require the most work :)
21:26 LeeJ          agreed davidnind
21:26 Joubu         release notes is https://gitlab.com/joubu/koha-release-notes/blob/master/release_notes_17_12_00.md
21:26 caroline      they're the most useful, they should be priority
21:26 Joubu         (I have forced pushed and it seems it has not been synced)
21:27 davidnind     although sometimes bug fixes can take up time as you try and work out what the problem is..was...
21:27 LeeJ          Joubu++ # for the link
21:27 LeeJ          davidnind: I'll hop on IRC when I'm home later and see how much we can get done
21:28 davidnind     home time for me will be in about 8-9 hours
21:28 LeeJ          #info LeeJ will be working with davidnind to update kohadocs with new 18.05 features
21:28 LeeJ          davidnind: ahh right. timezones :)
21:29 davidnind     I should probably do some work while I'm a work today
21:29 LeeJ          anyway..I'll hammer out those details with you later davidnind
21:29 davidnind     ;-)
21:29 LeeJ          anyone else have anything to add? anything I missed?
21:29 davidnind     a.. should be at!
21:30 cait1         i've added something about moving interesting things from the help files to th emanual
21:30 cait1         reconciling them before the help files get removed
21:30 cait1         but as git has it all, that is not as urgent as the new things i think
21:31 LeeJ          #idea cait mentioned moving interesting things from help files to the manual
21:32 davidnind     I guess it comes down to priorities in the time available to 18.05 - release notes, new features and enhancements documented, manual brought as up-to-date as possible (with sprint day)
21:32 barton        I like that idea.
21:33 davidnind     cait always has excellent ideas!
21:33 caroline      hear hear! :)
21:33 LeeJ          davidnind: I think the order should be new features then release notes..minor but still :)
21:33 LeeJ          cait1++
21:33 LeeJ          #info kohadocs updates will be handled with the priority of new features, release notes, enhancements, etc.
21:34 davidnind     that's fine too... better to have a plan than no plan at all
21:34 LeeJ          well if no one has anything else, let's figure next meeting time
21:35 LeeJ          Joubu: is the 18.05 release around May 28th?
21:35 Joubu         May 22th
21:35 cait1         22
21:35 LeeJ          ah ok
21:35 LeeJ          so then how about next meeting same day same time next month?
21:36 Joubu         It will be a Friday
21:36 LeeJ          oh dear
21:36 LeeJ          hmm
21:36 LeeJ          May 9th then?
21:36 Joubu         will be a dev meeting
21:37 Joubu         but before, like today actually
21:37 Joubu         so that's fine
21:37 caroline      may 9 works for me
21:37 LeeJ          so it'll be 14 UTC for dev?
21:37 Joubu         yes
21:37 LeeJ          okay
21:37 LeeJ          #topic Set time of next meeting
21:38 Joubu         #info Next meeting: 9 May 2018, 21 UTC
21:38 LeeJ          thank you Joubu :)
21:38 LeeJ          #endmeeting
21:38 huginn        Meeting ended Wed Apr 11 21:38:31 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
21:38 huginn        Minutes:        http://meetings.koha-community.org/2018/documentation_irc_meeting_11_april_2018.2018-04-11-21.02.html
21:38 huginn        Minutes (text): http://meetings.koha-community.org/2018/documentation_irc_meeting_11_april_2018.2018-04-11-21.02.txt
21:38 huginn        Log:            http://meetings.koha-community.org/2018/documentation_irc_meeting_11_april_2018.2018-04-11-21.02.log.html
21:38 LeeJ          thank you all for coming
21:38 davidnind     LeeJ++
21:38 LeeJ          davidnind++
21:38 caroline      Thanks LeeJ
21:38 LeeJ          thank you for coming caroline
21:39 LeeJ          alright! Time to head home then log back in at some point! :D
21:39 Joubu         bye #koha
21:39 davidnind     have a great day/evening everyone!
21:40 clintD        davidnind was the doc webinar recorded anywhere?
21:41 cait1         davidnind++ # awesome job on twitter, wiki and everywhere
21:42 davidnind     it wasn't ClintD, hopefully LeeJ's updates to wiki page should help. I'm sure he'd be happy to do a quick walk through for you.
21:42 davidnind     I think LeeJ had an earlier video he recorded, will find the link for this if I can and send it to you
21:42 clintD        ok, thank you
21:43 cait1         it's on the editing the manual?
21:43 cait1         page
21:43 cait1         editing manual?
21:43 cait1         hm
21:44 cait1         https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual
21:44 cait1         https://www.youtube.com/watch?v=tiwH7-wO2Gs
21:45 clintD        thank you cait, got that
21:45 davidnind     cait1: :-[, just learning my way at the moment with Twitter - trying not to post too much - there is a lot happening around the world with Koha
21:45 davidnind     cait++ should have thought of that!
21:45 cait1         I think you do very well
21:46 cait1         there is a lot of buzz from other projects in library space and we have been very quiet
21:46 cait1         it's good to see that changed
21:47 davidnind     I hope it will help - my initial 'plan' is to focus on 1) sharing what's happening in the community (events, meetings, etc)
21:48 davidnind     2) raising awareness (new Koha libraries, usage, case studies, etc)
21:49 davidnind     3) help with learning about Koha: features, tips, useful resources to get the most out of Koha (the manual will certainly help here)
21:49 caroline      davidnind where do you get the info? hashtag kohails?
21:50 cait1         excellent plan
21:50 davidnind     caroline: #kohails, search for koha + library, community members and support providers (twitter, websites, etc), mailing list
21:50 cait1         if we wanted to make you aware of something
21:50 cait1         what would be the best way?
21:50 jenkins       Yippee, build fixed!
21:50 wahanui       o/ '`'`'`'`'`'`'`'`'`
21:50 jenkins       Project Koha_Master_D8 build #430: FIXED in 32 min: https://jenkins.koha-community.org/job/Koha_Master_D8/430/
21:50 jenkins       Tomás Cohen Arazi: Bug 20123: (follow-up) Mock timezone in t/Auth_with_shibboleth.t
21:50 huginn        Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20123 enhancement, P5 - low, ---, kyle, Pushed to Master , Allow multiple instances of Koha to have different timezones on the same server
21:51 davidnind     have started a list of things I can monitor, including the IRC channel
21:51 davidnind     will share this on my git lab account in the next day or two
21:52 davidnind     happy for people to send me stuff - david dot nind at gmail dot com
21:52 wizzyrea      can also send via twitter eh, by tagging in @kohails
21:52 caroline      +1
21:52 cait1         would you also receive a pm to kohails?
21:52 davidnind     will add this to social media plan page I intend to add to wiki, to get some initial feedback
21:52 cait1         well direct message
21:54 davidnind     cait1: I hope that will work, have access to the kohails account using tweetdeck.twitter.com
21:55 cait1         hm i think dm might be turned off
21:55 cait1         email will work :)
21:56 wizzyrea      I don't feel like the community twitter should have DM's turned off
21:56 davidnind     will check the tweetdeck manual and test it out this evening
21:56 wizzyrea      (until such time as it is say, attracting harassment. Which it probably won't.)
21:56 caroline      it may be because it's not always monitored?
21:56 wizzyrea      DM's are like email.
21:57 wizzyrea      just in twitter.
21:57 caroline      if someone sends a dm and never gets an answer, it might not look good
21:57 davidnind     Jonathan has the full account login details, will get him to check if I can't change this in TweetDeck
21:57 wizzyrea      cool :)
21:57 davidnind     wizzyrea: agree!
21:58 cait1         @later LeeJ Bug 20565        - Clearer documentation of date, branches, itemtypes and categorycode parameters in 'Create report from SQL' help page
21:58 huginn        cait1: I'll give you the answer as soon as RDA is ready
21:59 davidnind     also item 4) in plan - encourage participation, for example remind about meetings, highlight how community members can contribute such as translation, manual, sign-off, etc
21:59 cait1         i like how you picked up questions
21:59 cait1         sadly i have no idea about what omeka exactly does
22:00 davidnind     and, one which I'll see how it works is 5) help with any questions: will resort to posting to mailing list if I can't readily find an answer
22:00 clintD        Omeka is a repository for digital resources
22:01 davidnind     for sharing digital collections: http://omeka.org/classic/
22:02 davidnind     clintD++
22:03 davidnind     right, better get back to work! see you all later...
22:30 talljoy       hi koha
22:35 talljoy       hi cait
23:33 * indradg     waves at talljoy
23:34 talljoy       hiya indradg
23:35 indradg       :)
23:36 talljoy       indradg, have you ever seen the 942$s (serial flag) in use?
23:37 indradg       talljoy, not that i can recall
23:39 talljoy       curious tag.  i suspect it is a deprecated tag.  i need to find someone from koha 2.0 days
23:41 indradg       yeah... i only started on Koha from 2.2
23:42 wizzyrea      oh are you migrating out of a 2.0
23:42 talljoy       ha.  thankfully no!
23:42 wizzyrea      those are fun.
23:42 talljoy       i had a library ask about the 942$s biblio.serial flag
23:43 wizzyrea      git would probably know
23:44 talljoy       git would know.
23:45 talljoy       i've pinged khall to investigate on my behalf.  benefit 1 - he's been around koha a while 2- he know git well.
23:45 talljoy       :D
23:46 rangi         its just a flag, wether the item is a serial or not, when you add a subscription to a biblio, it flips that to 1, its either on or off