21:00:37 #startmeeting Documentation IRC meeting 19 October 2017 21:00:37 Meeting started Thu Oct 19 21:00:37 2017 UTC. The chair is cait. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:37 The meeting name has been set to 'documentation_irc_meeting_19_october_2017' 21:01:00 #topic introductions 21:01:01 #info wahanui, a bot that has become sentient 21:01:14 #info George Williams, Northeast Kansas Library System 21:01:20 please introduce yourself using #info :) 21:01:25 #info Bob Birchall, Calyx, Australia 21:01:26 #info Jonathan Druart 21:01:30 #info Michael Cabus, ByWater Solutions 21:01:31 #info Katrin Fischer, BSZ, Germany 21:02:03 #link https://wiki.koha-community.org/wiki/Documentation_IRC_meeting_19_October_2017 today's agenda 21:02:06 #info Chris Cormack, Catalyst NZ 21:02:15 #chair rangi 21:02:15 Current chairs: cait rangi 21:02:26 thx all cor coming! 21:02:39 #topic How does it work? 21:02:59 I don't have new information since the last meeting, instrcutions are available on the wiki 21:03:04 but are there any questions about the process? 21:03:37 I'm just getting my act together (missed last( but will review instructions :) 21:03:55 let me know if I can help :) 21:04:13 #link https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual Instructions on how to edit hte manual 21:04:18 moving on 21:04:23 no contribution from me yet, cait, hoping to get to it in the next couple of weeks 21:04:56 BobB: thx! Irma has sent a merge request - waiting for her feedback on my comment 21:04:59 #topic What's been done so far 21:05:18 #info LeeJ has been cleaning up the cronjobs chapter and adding new things to it 21:05:49 #info Joubu fixed the problem with the screenshots that were not migrated correctly 21:06:07 #info jzairo has been working on a patron clubs feature - merged not long ago today 21:06:27 #info Documentation Sprint has been quite good, we got some first time contributors, more listed on the wiki 21:06:40 #link https://wiki.koha-community.org/wiki/2017-10-05_Documentation_Sprint_Day Past Documentation Sprint day 21:07:07 #info kellym has been updating the authorized values list 21:07:20 hope i didn't miss someone - every contribution is much appreciated 21:07:30 #info kelly mcelligott bywater 21:07:33 i fixed the search 21:07:40 thats about all I got done 21:07:51 #info rangi fixed the search problem! 21:07:52 sorry :) 21:08:18 i'd like to move on to todo if that' sok 21:08:25 #topic Next steps 21:08:50 #link https://annuel2.framapad.org/p/KohaManualTodo todo list 21:09:20 we've listed some areas where descriptions are missing, authorised values and notices for examples 21:09:46 i think it would be good to take a look at the feature lists of the last releaess and check against the manuals what is missing 21:10:03 if someone wants to volunteer to fill up the list it would be nice :) 21:10:15 rangi, any technical todos? 21:10:49 there are nicer ways to do translation than the way we currently do it for the old manual, id like to get one of those working 21:11:17 yes, translation is a big TODO 21:11:22 https://pypi.python.org/pypi/sphinx-intl 21:11:44 we can still use pootle, but there are easier was to generate the .po file 21:11:47 bye 21:12:13 hm but still po files then? 21:12:26 i thin one problem with pootle is if hte po files orders alphabetic 21:12:27 yes 21:12:34 would be nice to have th estrings in the order they appear 21:12:48 people can use transifex or anything they want with the .po file 21:13:12 cait I can add to the to do list for 17.05 release including new sys pref and features 21:13:15 its the currently the way we generate it, and regenerate the docs that is the messy bit 21:13:22 Are there notes somewhere already about that? 21:13:36 Joubu: about what? 21:13:37 kellym-kohamtg: thx! sysprefs should be done up to 17.05, but everything else we didn't check 21:13:43 manual translation 21:13:58 the different possibilities, what has been tried already, etc. 21:13:58 #action kellym to add missing 17.05 features to to-do list 21:14:03 i dont have the docs for the old docxml way, that was done by bernardo 21:14:15 but this looks like the best way for sphinx 21:14:18 http://www.sphinx-doc.org/en/stable/intl.html 21:14:21 for the old way there is inofrmation on the wiki 21:14:30 and https://pypi.python.org/pypi/sphinx-intl 21:14:31 we haven't added anything there for sphinx yet 21:14:55 when will want to pick the strings that are already translated on the old manual I guess? 21:15:03 :s/when/we 21:15:10 (sorry, tired...) 21:15:15 for the ones that are translated yes 21:15:28 (which is spanish, french, chinese and german?) 21:15:38 we can start fresh with the others 21:15:45 not german 21:15:48 but there are some 21:15:50 italian maybe too 21:16:02 ah yes substitute italian for german 21:16:07 it's been a lot of work, would be good to save it 21:16:34 the old way you get lots of duplicated stuff 21:16:44 (like we do in our .tt) 21:17:12 im hoping we can reduce lots of that 21:17:24 I will try to have a look at that, if nobody else does 21:17:29 ot as much in the manuals as in the interface i think, but yeah 21:18:14 why duplicated stuff? 21:18:30 strings should appear only once in the manual, so should not be picked twice 21:18:40 heh no 21:18:44 lots of strings repeat 21:18:59 ok sounds fun 21:19:16 but i think sphinx-intl will do a much better job 21:19:43 we will see :) 21:19:55 i still think translating in context would make up for repeats 21:20:10 ok, so the plan would be to first make it translatable easily, then reinject the strings that are already translated 21:20:16 not having context or knowing what the paragraph before referenced to is making things hard 21:20:19 yeah 21:20:44 manual translation coudl be different to gui 21:21:45 ok 21:21:50 is there any action item we can look? 21:21:57 i really dont want to build any more tools we have to look after 21:21:59 is someone volunteering to look into options? 21:22:16 if we can use tools others are maintaining, rather than our own scripts its a massive win 21:23:12 I really would like to announce that the manual for 17.11 is ready, so I will try to have a look 21:23:21 cool 21:23:22 at least estimate the amount of work we need 21:24:11 thanks Joubu 21:24:49 #action Joubu is goingto look into options for manual translation 21:24:55 ok 21:24:59 something else? 21:24:59 well, something else is doing that, before you ran my rebuild 21:25:06 yes 21:25:07 wait 21:25:14 what's next? :) 21:25:26 getting more people involved 21:25:29 I would like to know what do we do for the new ft 21:25:40 new features? 21:25:40 new features are almost invariable meant for master 21:25:41 the ones that are going to be in 17.11 21:26:02 we have a possible backlog to 16.11 or 16.05, not sure yet 21:26:12 kellym-kohamtg: was going to look at 17.05 release notes 21:26:24 yes cait! 21:26:31 maybe we could provide 'alpha' release notes for 17.11 to get people started? 21:26:38 they are there now 21:26:47 link? 21:26:47 link is both helpful/unhelpful 21:27:10 https://koha-community.org/manual/17.11/html/ 21:27:17 its always that pattern 21:27:22 I would like to do something for the release notes, provide them very early and make the contribution/fix easy 21:27:25 yeah, but not release notes to see what will be added :) 21:27:38 and highlight what is missing (new) 21:27:39 ah right, misread 21:27:52 Joubu: hm? 21:28:03 Joubu: you could use gitlab ci or jenkins 21:28:14 to publish them somewhere 21:28:19 constantly bulid them 21:28:20 could work 21:28:21 new ft will be highlighted in the release note, with the "release notes" field 21:28:26 ah 21:28:37 - Is it enough to put that in the manual? 21:28:38 jenkins sounds like a good idea to me 21:28:42 no 21:28:48 - Does we ask dev to make something bigger for the manual? 21:28:56 - It is not a job for dev 21:29:07 because you can't see where it should go and it's suppoed to be a summary I think - not instructions how to use 21:29:20 - Do we want to have all these ft with enough doc when 17.11 is out? 21:29:49 without having the list I fear that we might not have enough people rightnow 21:30:00 we could try to get more people involved by having such a list 21:30:13 and if peope send me text i can make the patches to include 21:30:16 if that's a barrier 21:30:21 add screenshots too if they are sent separately 21:31:02 Joubu: could you check where we could keep the pre-release notes? and then we send an email to the mailng list to aks people to send merge requests or texts to koha-docs mailing list to include? 21:31:31 Anyone around that is willing to help documenting the new 17.11 features? 21:32:06 caboose-afk: don't go... was going to ask you about styling the manual :) 21:32:09 I definitely want to get involved 21:32:22 yeah I want to help with that for sure cait! 21:32:47 someone left some notes about ways on how to do that on the todo list 21:32:57 sweet 21:33:09 haven't had time to review, but might be a starting point 21:33:15 cool, I am on it 21:33:59 #info caboose to look into styling/improving the manual look and feel 21:34:24 Joubu: willing to try, but can't do it alone, so let's try mailing list next 21:34:54 #info If people want to send text and screenshots instead of merge requests, cait will turn that into patches 21:35:16 #action caboose to look into styling/improving the manual look and feel 21:35:32 #action Joubu to generate pre-release notes for manual work 21:35:59 search has been fixed 21:36:07 * Joubu duplicates himself 21:36:08 so i think we covered about all of the next steps topics listed now 21:36:28 sounds good :) 21:36:33 moving on? 21:36:41 #topic Getting more people involved 21:36:48 actually that fits with the question about 17.11 21:37:07 i think too early for another sprint maybe 21:37:10 any other ideas? 21:37:10 any other ideas are welcome as well 21:38:30 as a company we want to help .... 21:38:41 people should stop sleeping 21:38:50 but there are so many competing demands on everyone's time 21:38:59 Joubu: not sure I can do with even less... 21:39:07 somehow we really need to get users to own this - librarians 21:39:12 ^ 21:39:19 BobB: we understand, it's just turning into a global problem :) 21:39:51 As a librarian I want to help too but, like BobB says, there are a lot of demands on my time 21:39:55 all the koha people are super busy, which is good, so we need more of us and get libraries involved 21:40:02 so keep pounding the mailing list? 21:40:09 georgewilliams: what would make it easy for you? 21:40:16 If there were two of me 21:40:21 LOL 21:40:22 heh 21:40:43 maybe another thought 21:40:51 * wizzyrea fires up the cloning machine 21:40:52 (just a number, this year we have ~20 authors per months, last years it was ~30) 21:40:57 #info Please think about putting your name down for documentation team 18.05 21:40:58 I'm being crushed by demands for help from the 51 libraries in our system, so my biggest issue is a complete lack of time 21:42:03 georgewilliams: maybe start small... you are lookign for something in the manual, don't find it, note it on the todo 21:42:15 That I can probably do 21:42:23 also when you notice a typo or whatever 21:42:26 That's a good idea - a good starting point 21:42:28 cait: maybe you should (just in case...) add a message on the kanba. There was a documation epic with lot of people interesting by contributing to the manual 21:42:33 the todo is made so it can't be done quickly, no log in or anything 21:42:36 kanban* 21:43:03 #info If you ntoice something missing on the manual, a typo, some error, please take a short moment to note on the to-do list! 21:43:16 #action cait to update the kanban with latest developments/needs 21:43:37 and if any of you know someone who would be good to contribute something, please ask them 21:44:00 moving onto setting a date for the next meeting ok? 21:44:04 it's awfully late here 21:44:05 And I'll also report on this meeting and the need for contributers at the next Koha-US meeting 21:44:14 excellent! 21:44:24 :) 21:44:35 #action georgewilliams to report about the documentation meeting and the need for contributors at the next Koha-US meeting 21:44:56 cool 21:45:18 #topic Set time of next meeting 21:45:26 so release is end of nov 21:45:31 should we meet agian before? 21:46:43 in 3 weeks 21:46:48 perfect 21:47:09 Joubu: can you suggest a date? 21:47:33 +3w, Now 8th :) 21:47:38 Nov 21:47:43 is that ok for everyone? 21:47:46 yes 21:47:55 yep 21:47:57 yes 21:48:08 hm let me quickly chekc my calendar 21:48:33 ha, it's a Wed 21:48:36 maybe 9th then 21:48:41 Nov 8 is a Wednesday 21:49:07 hm will be having trainign that week 21:49:22 so that week is generally bad for me, unless somoene else could chair 21:49:56 is a week later still ok? maybe monday? 21:50:05 that works for me 21:50:08 13th 21:50:25 same time? at least we should go into winter time before that, so a little bette rfor me (if I calculated correctly) 21:50:49 13th works here 21:50:52 that date works for me! 21:52:04 #agreed next meeting will be on Monday, 13 November, 21 UTC 21:52:07 #endmeeting