21:07:27 #startmeeting Documentation IRC meeting 2 October 2018 21:07:27 Meeting started Tue Oct 2 21:07:27 2018 UTC. The chair is caroline. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:07:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:07:27 The meeting name has been set to 'documentation_irc_meeting_2_october_2018' 21:07:43 #chair cait 21:07:43 Current chairs: cait caroline 21:07:49 #chair davidnind 21:07:49 Current chairs: cait caroline davidnind 21:07:53 mwa hahah! 21:08:19 #topic Introductions 21:08:34 #info Katrin Fischer, BSZ Germany 21:08:36 (please use "#info" in front of your introduction to have it show up in the automatic minutes) 21:08:45 #info Caroline Cyr La Rose, inLibro 21:08:54 #info David Nind, Wellington, New Zealand 21:09:13 Joubu? 21:09:27 #info Jonathan Druart 21:09:30 #topic What's been done so far 21:09:56 KohaCon18 & hackfest 21:10:07 rangi and cait gave a presentation on documenting Koha with a live edit of the manual (!!) 21:10:13 #link https://www.youtube.com/watch?v=XXn9k4Ir8is&index=24&list=PLV_OXyJ1D3BgcRtxrjVkCBXjSt7Dr1qKy&t=0s 21:10:19 cait++ rangi++ 21:10:25 It generated a lot of interest 21:10:27 rangi++ cait++ 21:10:35 rangi did the demo - he is the brave one 21:10:39 I don't know if ppl asked them questions in private afterwards, but I know a couple approached me with questions 21:10:57 he challenged them to make a edit for a fix of the version number and 2 did 21:11:15 Maybe future writers? :D rangi noticed new contributors. 21:11:25 during the hackfest, I gave a workshop on editing the manual and there was 8-10 ppl in attendance. 21:11:27 he gave out some chocolate fish as well I think 21:11:37 caroline++ 21:11:55 That's a NZ thing, it's not as much an incentive for the rest of us ;) 21:11:58 caroline++ 21:12:02 she was awesome :) 21:12:04 The wiki page was really useful 21:12:08 #link https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual 21:12:20 hehe thx :) We all did a great job 21:12:22 I thought it went very well - there was a lot of interest, and I think everyone managed to get something commited 21:13:07 Any other comments? 21:13:25 moving on 21:13:29 #topic Workflows 21:13:53 Does anybody have anything to say about this? It's a topic by default so I never know 21:14:18 i think no changes 21:14:19 (I have to leave sooner than expected, sorry! See you tomorrow) 21:14:22 so we can probably move on? 21:14:28 Is everyone okay if I add a section on setting up a local copy of Sphinx, so you can generate an updated docs 21:14:28 #topic Next steps 21:14:45 davidnind: of course! 21:15:02 wasn't as complicated as I thought 21:15:20 I'm eager to see it, I didn't know it was possible 21:15:30 So you can see in real time your changes? 21:15:45 yep - doesn't take too long to generate 21:15:50 Cool! 21:16:07 was easy to setup on Linux, can do on Windows, but don't have a mac to test 21:16:11 Please do! I'm always anxious with the syntax because I don't know how it will turn out 21:16:20 you have to regenerate 21:16:28 added to my task list! 21:16:28 but it does work :) and you can have your own epub too 21:16:32 like the doctor? 21:16:39 heh 21:16:46 i so want to say yes to that 21:16:46 :) 21:17:09 Alrighty 21:17:26 #action davidnind will write a section on setting up a local copy of Sphinx, so you can generate an updated docs 21:17:48 #topic Automation of screenshots 21:17:57 I noticed a lot of screenshots were out of date in the manual 21:18:05 I added a dedicated section in Taiga, but it discouraged me a little bit 21:18:09 #link https://tree.taiga.io/project/ldjamison-kohadocs-1805/us/586 21:18:25 During hackfest, I spoke with Joubu about his tool to take automatic screenshots. He said no one had really sent him comments, so we weren't sure if it was because there was no interest, or because of another reason (too busy, email got lost in pile of emails, etc.) 21:18:35 We discussed of the pros and cons and I wrote them down so we could discuss them here 21:18:41 #link https://www.evernote.com/shard/s162/sh/03edec69-1fd2-4f30-b562-f12ffc1f9e0b/b4179d876d0fedaa086a35d116a0f44c 21:18:49 PROS 21:18:53 1) Screenshots are always up-to-date with the latest version, do it once and they're always there 21:18:57 2) Screenshots can be generated in all languages 21:19:01 3) Script will test all pages, and regressions will be found 21:19:08 CONS 21:19:14 1) Harder to add images to the manual, only advanced editors will be able to add them 21:19:19 2) Joubu still has to work on it, he stopped because of the lack of comments 21:19:22 3) Some images might be hard to generate (50% easy, 30% medium, 20% maybe not attainable) 21:20:33 Someone wrote on the wiki "Have been experimenting with Selenium+Robot Framework+Screencapture library - looks promising" I'm guessing that's Joubu 21:20:45 That's me - I have been experimenting with Selenium + Robot Framework + Screencapture library 21:20:51 ah ok! 21:20:52 forgot to add my name 21:21:05 also ran out of time to add my notes and add repository 21:21:09 i am not sure i understand how to do it, but it might be easier than i think 21:21:21 So what is the workflow for your thing davidnind? 21:21:37 it took me a while to find something useful and relatively easy 21:22:12 Basically, inc plain language you write a script, something like this: 21:22:28 Valid Login 21:22:29 Open Browser To Login Page 21:22:29 Input Username koha 21:22:29 Input Password koha 21:22:29 Capture and crop page screenshot images/login_page.png 21:22:29 ... css=#login 21:22:29 Submit Credentials 21:22:31 Projects Page Should Be Open 21:22:31 [Teardown] Close Browser 21:23:05 interesting! 21:23:08 It looks simple enough 21:23:23 You then run a command from the command line and it folows the steps - can be against any Koha installation (I used the docker testing) 21:23:50 You can take screenshots of parts of pages based on css classes 21:24:02 It's very similar to what Joubu showed me. He was working with https://docs.cucumber.io/gherkin/reference/ 21:24:19 You can also add data to fields and capture that before it presses submit 21:24:51 davidnind: did you think it was very long to write up everything? 21:24:56 Will have a look at that - I think I did come across cucumber, but thought it was a bit complicated - will check it again 21:25:27 I ran out of time before this meeting, but will add wiki page and repository 21:25:43 thank you 21:25:49 It may not cover all screenshots, but maybe most (I hope) 21:26:25 Would take a bit of time to setup existing screenshots, but would make it much easy in the future 21:26:29 Personnaly, I think this would be very interesting, especially to have up-to-date screenshots and also screenshots in all languages 21:26:36 * rangi is just heading out 21:26:39 but davidnind http://git.koha-community.org/gitweb/?p=kohadocs.git;a=blob;f=README.md;hb=2482c4476c54347e652824ad2ec41e3a37b78c0b 21:26:45 we used to have instructions 21:26:58 this commit killed them 21:27:00 http://git.koha-community.org/gitweb/?p=kohadocs.git;a=commit;h=14e3bbb13fbe0c3d6eae8877fcddd9ff75d41f53 21:27:05 would be good to get them back :) 21:27:19 Will have a look, thanks rangi! 21:28:01 For languages you could change the Koha install language and then run 'test' 21:28:57 I'm sure there will be some problems... 21:29:36 Anyway will write up and share, and see if it is viable 21:29:40 oh oops 21:29:42 about the docs 21:29:46 I think it's still worth a try 21:30:03 can we add bringing back the readme page? 21:30:10 Looked at a lot of other options, but all seemed to require some sort of programming skills 21:30:43 cait what do you mean is there no readme anymore? 21:31:03 the current readme is very brief! 21:31:09 because rangi just said it got killed 21:31:22 I'll add it to taiga 21:31:46 #action caroline will add bring back the readme page as a task on taiga 21:31:52 yeah it's gone: https://gitlab.com/koha-community/koha-manual 21:31:58 it used to be instructions 21:32:19 with how to do sphinx, generate locally etc 21:32:23 #action davidnind will write up his notes on Selenium+Robot Framework+Screencapture library and share them with the group 21:32:47 the instructions look exactly like what I ended up doing! 21:33:32 sorry we lost them 21:33:39 the spelling check is useful as well - have to remember to write US english! 21:33:57 hehe! 21:34:01 things happen! 21:34:43 ready for the next topic? 21:34:57 yep! 21:35:04 #topic Organization of images in images.rst 21:35:22 been a bit slack on sending to the list... 21:35:37 you do so many things 21:35:48 not really! 21:36:05 I procrastinate a lot! 21:36:27 leaning towards the option of organising the index of images using categories by module 21:36:47 +1 21:36:53 e.g. cat-0001, circ-0001 21:37:01 and leaving the source images as they are 21:37:40 that way you can hopefully check if there is an image first in that category instead of creating another one 21:37:41 so not chaging file names/locations, just the numbering? 21:37:42 ok for me 21:37:56 I was thinking 3 capital letters + 3 numbers 21:37:59 there are about 1473 images at the moment 21:38:21 phew! 21:38:25 will post to docs list this evening (for me) 21:39:21 davidnind++ 21:39:22 ok so we'll discuss this via email and hopefully agree on a method (I hate hate hate merge conflicts because of images!) 21:39:23 as an aside I used the pngcrush tool and it turned images from about 82.3 MB down to 54.6 MB, about a 1/3rd reduction in size 21:39:47 :) 21:39:49 davidnind++ 21:40:55 caroline++ fixing all the docbugs! 21:41:00 #action davidnind will write a proposition to organize images to the docs mailing list and we will discuss by email 21:41:30 #topic Description of development process 21:41:46 It was mentioned on IRC that the development process/version maintenance was not documented. Someone was specifically asking why version 17.11.09 came out after version 18.05.03, which is a reasonable question, I think. 21:41:56 I was wondering if we wanted to document the outline of the development process, or is that too technical? 21:42:04 There is also the question of placement. Would that be in the introduction? in the FAQ? 21:42:20 I noticed there was a brief outline on the community website 21:42:34 hm there is information on the wiki 21:42:37 https://koha-community.org/about/release-schedule/ 21:42:45 but we might want to have osmething more 21:42:54 maybe a non-technical descriptoin with links to wiki for more? 21:43:20 Perhaps in an appendix on the development process, with a section in the about section about numbering and the release cycle? 21:43:59 loved the development process talk cait - was a great overview all in one place 21:44:17 cait++ both presentations were great! 21:45:08 The wiki is so big... trying to find the info in https://wiki.koha-community.org/wiki/Category:Development 21:46:05 This ? https://wiki.koha-community.org/wiki/Release_maintenance 21:46:21 i think all technical 21:46:31 but the second shoudl be current at least 21:46:36 Yes very. 21:47:37 we probably need something new 21:48:24 Ok, so do we agree to write something very non-technical for end users to understand the development process/cycle? 21:48:38 +1 21:48:41 makes sense to me! 21:48:46 #agreed write something very non-technical for end users to understand the development process/cycle 21:48:56 appendix? faq? 21:49:15 faq still needs a major clean up 21:49:33 maybe a new section? 21:49:42 or in the "about"? 21:49:44 I think as an appendix, but having a brief intro in about Koha section 21:50:06 ok so appendix/new section 21:50:31 #agreed the development process/cycle will be in an appendix 21:51:32 #action caroline will add the development process section to taiga (just to remember to do it) 21:51:51 #topic Set time of next meeting 21:52:32 Do we want to change the time? 21:52:49 happy for it to be earlier if it suits you all better (https://www.timeanddate.com/worldclock/) 21:53:09 earlier? I though it was like 7am in NZ 21:53:22 11pm here os not against earlier 21:53:27 nearly 11am (daylight savings time) 21:53:53 omg ok, so how about 8 for you? 21:53:56 we are moving in a few weeks... so might be even later then 21:54:16 what time is it for LeeJ 21:54:31 Same as me I think. Right now it's almost 6 pm 21:55:12 UTC 19? 21:55:21 what is now? 21:55:43 nearly UTC 22:00 21:55:58 today's meeting was at UTC 21 21:56:15 so it would be 2 hours earlier 21:57:09 https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=10&day=2&hour=19&min=0&sec=0&p1=165&p2=22&p3=195 21:57:26 19 sounds good 21:57:33 Is Nov 6 ok? 21:57:46 yes 21:57:49 is fine with me 21:58:17 * caroline mutters don't mess it up... dont mess it up 21:58:34 #info Next meeting: 6 November 2018, 19 UTC 21:58:45 heh 21:58:46 #endmeeting