14:01:11 #startmeeting Documentation IRC meeting 9 January 2020 14:01:11 Meeting started Thu Jan 9 14:01:11 2020 UTC. The chair is caroline_catlady. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:11 The meeting name has been set to 'documentation_irc_meeting_9_january_2020' 14:01:22 ooh.. meeting :) 14:01:35 #topic Introductions 14:01:43 please use "#info" in front of your introduction to have it show up in the automatic minutes 14:01:45 #info Martin Renvoize, PTFS Europe 14:01:51 #info Caroline Cyr La Rose, inLibro 14:02:08 #info Marie-Luce Laflamme, inLibro 14:02:16 #George Williams, Northeast Kansas Library System 14:02:24 #info Katrin Fischer, BSZ, Germany 14:02:37 davidnind says he set his alarm but might not have woken up... :( 14:02:50 #info George Williams, Northeast Kansas Library System 14:03:44 #info David Nind, Wellington, New Zealand 14:03:54 oh hi! 14:04:05 morning! 14:04:05 morning is always someone's afternoon 14:04:22 #topic Review of action points 14:04:27 #chair davidnind 14:04:27 Current chairs: caroline_catlady davidnind 14:04:41 Ok so action point from last time 14:04:52 review of documentation manager role 14:05:00 #link https://wiki.koha-community.org/wiki/Documentation_management 14:05:13 anybody have comments on what was done? 14:05:40 looks good so far 14:05:57 * caroline_catlady realizes she hasn't sent a reminder of the meeting on the list like it's written on that page ... -_- 14:06:16 will do better next time! 14:06:32 Also Review of transition workflow 14:06:43 #link https://gitlab.com/koha-community/koha-manual/issues/13 14:07:00 there has been some more dwork done on this 14:07:21 I branched 19.11 so we are effectively working on the 20.05 manual! 14:07:47 hoping to get 19.11 up to date asap before the new features and enhacements start rolling in for 20.05 14:08:19 davidnind: you had a concern about the branching? 14:09:01 that's all good 14:09:13 #info Thomas Dukleth, Agogme, New York City - [mild cold] 14:09:28 ok 14:09:43 * ashimema[m] should read the latest updates there.. will catch up 14:09:48 Last action point Managing branches and back porting changes 14:10:03 got in the swing of back porting changes, so happy to do that if you would like 14:10:18 Like I said, I branched 19.11, and I have been backporting commits as needed 14:10:25 #info Jonathan Druart 14:10:52 rangi said what I did was ok, so I'll try to document what I did for future reference 14:11:16 ++ 14:11:50 caroline_catlady++ 14:12:02 #topic Project updates 14:12:14 #link https://wiki.koha-community.org/wiki/Koha_Documentation_Team#To_do_lists_and_projects 14:12:43 anybody have updates on projects they have been working on? 14:14:08 I am back in New York where I can work on Koha instead of cleaning ceiling's etc. for my mother in California. 14:14:44 hehe! 14:15:19 nothing to add from me (did nothing over the xmas break :-() 14:15:33 * cait was lazy too 14:16:30 alright so we'll see next time 14:16:45 #topic What's been done so far 14:17:14 davidnind: has been doing some maintenance work 14:17:19 with bernardo 14:18:24 :) 14:18:26 lucyvh has been doing several changes from 18.11, thanks for catching us up! 14:18:48 lucyvh++ 14:19:00 ashimema[m] has the trophy for first commit to 19.11 :) add EDI LRP support to stock rotation 14:19:24 so happy to see all the updates! 14:19:31 and AndyBoze has the trophy for first commit to 20.05 and it's his first contribution! 14:20:17 We also have another first contributor : Alexander Borkowski (not sure what is the irc handle) 14:20:46 ashimema[m]++ lucyvh++ AndyBoze++ everyone++ :D 14:20:57 hehe.. i wrote that submission months ago when i wrote the code :) 14:21:05 * ashimema[m] would encourage devs to try to do the same. 14:21:22 awesome to see new contributors too :) 14:21:26 woop, woop 14:21:41 woop! 14:21:42 yes! yay! 14:22:28 awesome everyone! 14:22:33 caroline_catlady has been adding all the tasks to taiga, and a bit of a flurry of changes in the last week by Holly 14:22:50 Apologies, lost track of time! 14:22:55 right! I merged them and totally forgot to mention it :) 14:23:03 Hi everyone 14:23:20 hi lucyvh! we were just ++ing you for your great work :) 14:23:25 hi lucyvh! 14:24:02 #topic Content development guidelines 14:24:16 davidnind has been working on this 14:24:34 New section on commit messages 14:24:38 #link https://wiki.koha-community.org/wiki/Git_guide_for_documentation#Commit_messages 14:25:05 (though I don't think we will not refuse commits if they don't have this formar) 14:25:27 also more info on how to write links 14:25:30 #link https://wiki.koha-community.org/wiki/ReStructuredText_-_Tips_and_Tricks#Links 14:26:13 words to use instead of others 14:26:16 #link https://wiki.koha-community.org/wiki/Word_usage_-_A-Z 14:26:37 for example use staff clinet instead of intranet, etc... 14:26:42 *client 14:26:44 wow, very cool 14:26:53 awesome work 14:26:59 consistent use of words is helpful for translations as well 14:27:13 although one could argue that we don't have a client 14:27:34 in technical terms 14:27:34 Its so useful to have all this written up somewhere - amazing work! 14:27:45 I agree, but that's in the Koha terminology... 14:28:04 oh i see 14:28:07 Personnaly, I would prefer staff interface 14:28:12 same :) 14:28:24 we use the literal translation fo that in German 14:28:37 #link https://wiki.koha-community.org/wiki/Terminology 14:28:42 I've got a few more, but started with a couple (staff client was from the current terminology list at https://wiki.koha-community.org/wiki/Terminology) 14:28:56 so maybe we shoudl rethink that there than if we want to change 14:29:27 is it used a lot in the code of Koha? 14:29:34 do we want to change it? I prefer staff interface myself 14:29:51 Ok, so we'll change it for the documentation 14:30:00 +1 for staff interface 14:30:04 I think I've seen all of them used so far in the manual 14:30:06 ashimema[m]: you can decide what you want to do in Koha's code itself 14:30:09 code wise we say 'intranet'.. but that all hidden to end users in reality 14:30:17 My quick search only turns up one use of "staff client" in the templates 14:30:39 i think there is everything in the gui now 14:30:40 terms wise I'm happy with 'staff interface' as the standard 14:30:41 Even if "X client" may be technically correct in terms of function. People in the general population at least may relate better to "interface". 14:30:52 so not too late to change :) 14:31:03 ok davidnind can you change the wiki page? 14:31:05 I think it's most likely to come up allot in the manual but very rarely be a term we use in koha itself 14:31:23 i think probably in the prefs most 14:31:28 I will! 14:31:28 Switching from "intranet" to "staff client" was an improvement but also an arbitrary decision. 14:31:30 but t would be an easy clean-up job 14:31:41 coolios 14:31:49 oleonard: are you ok too with staff interface? 14:31:53 #action davidnind will change the manual terminology from staff client to staff interface 14:31:56 so maybe we should change both pages 14:32:06 I imagine that support companies might have standardized on "staff client" in their web sites and documentation? 14:32:16 Something to check on. 14:32:24 Otherwise I like staff interface. 14:32:32 we use intranet or staff interface in our local docs 14:32:34 quickly checking bywater for some samples 14:33:00 as the terminology page is part of the development guide, should we raise at development meeting as well? 14:33:01 #action caroline will add a task to change the terms in the manual 14:33:11 I hear staff client, staff interface, and intranet from ByWater all the time. It depends on who you're talking to. 14:34:02 hm couldn#t turn up an example yet 14:34:02 ByWater can patch those humans' operating systems in a snap right? 14:34:11 We use all those variations times also at PTFS 14:34:17 I'm sure they'd like to 14:34:37 It varies in the documentation I've seen from them to 14:34:48 thx georgew 14:34:49 And it changes overtime 14:35:17 so there isn't a standard, but for the manual, we want it to be consistent 14:35:27 I will be an easy task for a newbie to commit 14:36:03 we're also thinking of adding a glossary to the manual to help ppl who are coming from other systems 14:36:16 I started one on a local branch 14:36:41 I will commit it soon, but I'm not sure how to make it show up in the table of contents 14:36:44 is it automatic? 14:37:12 the glossary is autogenerated I think 14:37:20 is it? 14:37:35 caroline_catlady: i think it's automatic yes 14:37:42 hm would it be top level new file? 14:37:55 that's wahat I was thinking 14:38:00 so it could go at the end 14:38:05 let me quickly check 14:38:37 "caroline_catlady" at 127.0.0.1 pasted "here's what an entry looks like in my file" (5 lines) at http://paste.koha-community.org/18771 14:39:52 the "see" is "instead of term 1, use term 2 14:40:19 so in my example, loan will refer to checkout 14:40:23 i thought it was source/index.rst 14:41:03 the terms show up in the index, there is a link to that at the top and bottom of each manual page 14:41:24 ah it is: https://gitlab.com/koha-community/koha-manual/raw/master/source/index.rst 14:41:37 gitlab does some rendering that makes some not show, but you can see it in raw 14:41:42 you just sort your new file in there 14:42:03 ok thanks cait 14:42:21 davidnind: I found the index list, but it's empty 14:42:48 i thin it just looks like it on gitlab - did you try 'raw'? 14:43:00 or edit, if you are logge din 14:43:03 that's because there areno entries yet 14:43:12 https://koha-community.org/manual/19.11/en/html/genindex.html 14:43:55 ok so when I add my file, it will populate this? 14:44:20 should do, I think it did when I tested 14:44:31 ok cool! 14:45:01 #topic Next steps 14:45:16 I wanted to talk about priorities 14:45:55 oh, different file! 14:46:06 I'd really like to catch up 19.11 so that when the devs start to add new stuff to 20.05 we can stay on top 14:46:19 +1 14:46:25 so priority #1 is anything in 19.11 on Taiga 14:46:59 should we note versions in commit messages? 14:47:30 I started adding "new feature", "enhancement" and "screenshot" tags in taiga, and that is the prioriuty order too (new features, then enhancements, then screenshots) 14:47:30 probably a good idea 14:47:47 write the version number in the commit message or the commit comment 14:47:56 I think adding it to the merge request would be better, e.g. this was added in 19.05, etc 14:48:20 as long as it's written somewhere 14:49:44 There are some interesting agenda points still to cover, but I think we on't have enough time 14:50:06 is it ok if we move these to the next meeting? 14:50:20 that's fine with me 14:50:29 me too 14:50:36 ok good! 14:50:37 yes 14:50:46 #topic Set time of next meeting 14:51:19 feb 6? 20UTC? 14:51:38 +1 14:52:00 hope it's not too late for everyone else... 14:52:38 +1 14:52:42 1 14:52:51 +1 14:53:18 #info Next meeting: 6 February 2020, 20 UTC 14:53:25 #endmeeting