21:09:15 #startmeeting Documentation IRC meeting 4 September 2018 21:09:15 Meeting started Tue Sep 4 21:09:15 2018 UTC. The chair is LeeJ. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:09:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:09:15 The meeting name has been set to 'documentation_irc_meeting_4_september_2018' 21:09:30 #topic Introductions 21:09:40 #info Lee Jamison, Marywood University 21:09:58 #info Caroline Cyr La Rose, inLibro 21:10:14 #info Kelly McElligott Bywatert 21:10:23 #info David Nind, Wellington, New Zealand 21:11:03 * LeeJ pokes cait 21:11:39 #info Katrin Fischer, Germany 21:11:54 #topic What's been done so far 21:12:30 for a change, I'm relying on all of you for this one :) haha 21:12:51 * caroline_ raises hand 21:12:58 caroline_: all you :) 21:13:47 Last meeting we discussed closing the framapad in favour of Taiga, so I went through all the points in the pad and added them to taiga 21:13:56 caroline_++ 21:14:04 caroline_: thank you :) 21:14:18 The pad now has a link to bugzilla for people who might have favourited it and want to report documentation "bugs" 21:14:32 that's all 21:14:37 I agree with that since that was the original intention of moving from framapad to taiga 21:15:12 caroline_: hmm..should that go to bugzilla? or to the gitlab issues under koha-manual? 21:15:44 cait davidnind kellym thoughts? 21:15:58 LeeJ: to keep you up to speed, the decision was to use bugzilla for regular people to filed documentation requests, taiga for the docs team and gitlab issues for issues concerning the "generation" of the manual 21:16:05 *file 21:16:09 ah! 21:16:24 disregard my question then..that makes sense 21:16:34 I removed the link to the framapad from the wiki 21:16:36 we also decided on a status quo for the mailing list since it's not very busy 21:17:08 I'll have to go through the last meeting's minutes tonight/tomorrow to catch up haha 21:17:17 I am not sure! 21:17:38 kellym: disregard my question..caroline cleared it up1 21:17:40 *up! 21:17:52 good- I too will have to look at last months notes 21:18:36 #link https://wiki.koha-community.org/wiki/Documentation_IRC_meeting_14_August_2018 21:18:46 thanks leej 21:19:02 anyone have anything else to add before we talk about what to do moving forward? 21:19:21 nothing from me - have started a couple of more easier tasks, just need to finish and submit! 21:19:31 davidnind++ 21:19:37 have been very lazy.... 21:19:58 davidnind: I see your lazy and raise you lazy but busy :P 21:20:32 okay then! 21:20:42 #topic Next steps 21:21:56 #info currently 6 merge requests in queue - 2 WIP, 2 ready to merge, and one to address with the person who submitted it (since LeeJ forgot/neglected to respond about it previously) 21:22:46 caroline_ davidnind cait kellym anything to add regarding moving forward towards release? suggestions/things to point out/ideas, etc.? 21:23:11 nothing to add from me 21:23:20 busy with qa, might join documentation efforts late 21:23:22 do release notes come out one by one or all at the same time? 21:23:31 depends on RM 21:23:39 last release I know davidnind and LeeJ added all the release notes to taiga 21:23:50 no, I would like to help, but need to get more familiar with the new way of updating. Was there going to be a tutorial on adding images to the manual for edits/updates? I am excited for Kohacon presentation about Documentation 21:23:54 Joubu generate d them regularly and early, not sure if that script still works 21:24:08 caroline_: correct..last release Joubu had a rolling release notes doc that davidnind and I scraped from 21:24:10 mainly LeeJ did that 21:24:16 kellym: we can cover that at the hackfest maybe 21:24:18 wil you be there? 21:24:44 I won’t be at Hackfest, just the first few days. Cait will you be there, can we catch up about this? 21:24:56 i will be there and we can try 21:24:57 kellym I'm always available to discuss via phone/email or give help with..but probably the presentation will cover it...unfortunately I can't attend this year :( 21:25:08 not sure if we will get to images 21:25:25 I can add a section on images on the wiki 21:25:30 caroline_++ 21:25:40 On this page : https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual 21:25:46 but asking caroline might work even better :) 21:25:50 I heard you wouldn’t be there LeeJ - too bad! But once I see the presentation, maybe I will get in touch with you after the conference at some point, Awesome Caroline_ 21:26:07 or I will ask caroline_ 21:26:12 #action caroline_ will add a section on the wiki about adding images to the manual 21:26:27 kellym either way works for me :) 21:26:36 awesome 21:26:45 anything else to add from anyone? :) 21:27:07 would like to categorise the images somehow - it's getting to be a loooong list - will post ideas on docs mailing list 21:27:09 kellym: I'll try to do it before kohacon (if I have time) so you can read it and follow up with question 21:27:20 davidnind: good idea!! 21:27:28 davidnind++ 21:27:36 davidnind++ 21:27:38 that would be great caroline_ 21:27:43 @caroline_++ 21:27:44 kellym: I suck 21:27:52 caroline_++ 21:28:04 davidnind++ 21:28:22 everyone ++ :) 21:28:50 davidnind maybe we could have different areas of numbers for different sections? 21:29:01 i think the image are going to conflict a lot if everyone tries to use the next number 21:29:12 not sure how to solve that best 21:29:37 caroline_++ davidnind++ 21:29:57 cait: perhaps that could be a thinking point between now and next meeting? 21:30:21 sure 21:30:27 that was my thought e.g. 01 for cataloguing, then a sequential number e.g. 01-001-image-name 21:30:46 davidnind: I like that format 21:31:10 there are some librarians around, 'we' could come up with some sort of categorisation scheme I'm sure :-D 21:31:16 as long as it's not tied to chapters because those tend to change 21:31:43 mwahaha! images will be classified like a boss! 21:31:44 what if it's tied to modules...? 21:31:46 tied to modules I think 21:31:57 modules is the best way 21:32:01 like 01 for cataloging, 02 for circulation, etc. 21:32:10 yep 21:32:35 which would make it basically a namespace (for my fellow OOP-minded individuals) 21:32:58 it would still get to be a long list, but at least you would be looking in the right area 21:33:07 maybe it oculd also be cat0001 21:33:08 ? 21:33:11 memo codes 21:33:20 cait: that too! 21:33:21 and it would creat less conflicts like cait said 21:33:43 ouch, we're being bitten by https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18723 21:33:43 04Bug 18723: critical, P5 - low, ---, victor.grousset, BLOCKED , Dot not recognized as decimal separator 21:34:07 any idea if this is going to be fixed in a upcoming point release ? 21:34:31 lavamind: we're currently in a meeting, would you mind waiting until after and you can get some help? 21:34:51 LeeJ: oh of course, sorry about that!! 21:35:01 lavamind: no problem at all :) 21:35:38 I think cait 's suggestion of prefixing with a 'module identifier' of sorts might make it easier for quick reference 21:35:59 I like that too 21:36:19 so say cat0001, circ0002, acq0003, ser0004, cres0005, etc. 21:36:53 thanks to davidnind for getting the ball rolling...the thought never crossed my mind :) 21:37:48 Trying to solve my own problem - working out what image is what without duplicating (or minimising any way) 21:38:38 davidnind: and you always manage to help everyone else out simultaneously :) 21:39:50 #action submit a RFC of sorts to the mailing list to determine a new naming/organization scheme for the koha-manual images which can be voted on in the October 2018 meeting 21:39:58 sound good everyone? 21:40:04 +1 21:40:05 +1 21:40:08 +1 21:40:09 +1 21:40:11 sweet :) 21:40:51 if no one has anything else we can wrap this meeting up 21:42:32 #topic Set time of next meeting 21:43:16 how do we feel about October 4th at the same time? Any objections? 21:43:50 October 3? 21:44:08 both should work for me 21:44:12 *facepalm* I do that every time lol 21:44:20 weekend? holiday? 21:44:22 conflict? 21:44:32 No LeeJ it's not you. I just can't on Thursdays 21:45:04 ah first wednesday usually is general meeting 21:45:05 works fine for me - hope it is not tooo late or early for everyone else 21:45:15 hmm...I just realized that would cut it close with my one class ending lol...October 2nd at the same time (tuesday)? 21:45:35 works for me 21:45:43 fine with me 21:45:48 yup! 21:46:40 #info Next meeting: 2 October 2018, 21:00 UTC 21:46:57 #endmeeting