18:01:02 #startmeeting Documentation IRC meeting 10 December 2020 18:01:02 Meeting started Thu Dec 10 18:01:02 2020 UTC. The chair is caroline. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:02 The meeting name has been set to 'documentation_irc_meeting_10_december_2020' 18:01:11 #link https://wiki.koha-community.org/wiki/Documentation_IRC_meeting_10_December_2020 18:01:23 #topic Introductions 18:01:31 please use "#info" in front of your introduction to have it show up in the automatic minutes 18:01:48 #info Caroline Cyr La Rose, inLibro, Montréal Qc Canada 18:01:54 #info Marie-Luce Laflamme, inlibro Montreal 18:02:19 #info Lucy Vaux-Harvey, PTFS Europe 18:02:31 hi lucyvh! 18:02:55 Hi there 18:02:55 hello, lucyvh 18:03:07 hi lucyvh 18:03:23 Evening 18:03:38 #info Martin Renvoize, PTFS Europe 18:04:04 #info Thomas Dukleth, Agogme, New York City [sometime employer died, leaving tens of thousands of books mess to clean up.] 18:05:01 #topic Review of action points 18:05:03 If anyone could use thousands of books and can collect them from just north of New York city please let me know. 18:05:40 I will skip david's as he's not here 18:05:49 davidnind will check how we can use gitlab to simplify the workflow 18:05:54 #action davidnind will check how we can use gitlab to simplify the workflow 18:06:21 next was me, I was supposed to check with ashimema on how to best insert the docs writing into the workflow 18:06:39 I think we settled on the Manual keyword that will be added 18:06:53 QA people can add it 18:06:54 Project Koha_19.11_D9 build #280: SUCCESS in 44 min: https://jenkins.koha-community.org/job/Koha_19.11_D9/280/ 18:07:19 I will also look through what is pushed to master to add the keyword 18:07:40 So writers, Taiga will not be used for the 21.05 cycle 18:07:55 #info Taiga will not be used for the 21.05 cycle 18:08:08 #info Use bugzilla and search for the Manual keyword 18:08:20 No more epics :( 18:08:37 The manual will be epic no need for Taiga ;) 18:08:50 You can still use Taiga to look for older things to add 18:09:14 True 18:09:55 cait1 and ashimema were supposed to look into cleaning up the Manual keywords already in bugzilla to start anew 18:09:58 this has been done 18:10:24 #info all old Manual keywords were removed from bugzilla to start anew with the 21.05 cycle 18:11:21 I was supposed to modify the "Documentation to-do" search on bz's main page to include Manual keywords 18:11:49 not done, not sure if I can do it on my own or if cait1 needs to do it since she was the one who added it 18:12:03 #action change the Documentation to-do search on bz main page to include Documentation component OR manual keyword 18:12:29 I was supposed to document the new workflow, which I didn't do either... :( 18:12:36 #action caroline will document workflow for 21.05 18:12:53 I could give a hand 18:13:22 But basically, it's what I said earlier, for writers, the only change is that ehnacements and new features will not be copied to Taiga, we will use the Manual keyword 18:13:48 Once you've put in the merge request, you can remove the Manual keyword from the bug 18:13:55 I hope that makes sense 18:14:19 anyone, interrupt me if you have questions... I feel like i'm giving a speech rather than participating in a meeting lol! 18:14:38 Workflow sounds fine 18:14:59 last action point from last meeting was to divide the the syspref file because it is getting too big 18:15:29 I started this, but haven't finished... I will try to work on ituntil next meeting 18:15:41 #action caroline (or anyone) to divide the syspref file as it is getting too big for updates through gitlab GUI 18:15:53 Is there anything I can do to help with this? 18:16:24 hm... I thought I had to do it in one go, but we can do it bit by bit 18:16:54 if you add a new syspref maybe create the file for that section? 18:17:03 I don't know if that would be too confusing for users 18:17:07 probably... 18:17:07 i guess probably is too hard. 18:17:26 wahanui agrees lol! 18:17:26 caroline: excuse me? 18:17:35 If I know the steps I'm happy to give it a go 18:17:56 As I'm the one who complained about it! 18:18:16 I will try to do it in one go over the holidays, but if I can't I'll write how to do it bit by bit and we can all pitch in 18:18:21 does that sound good? 18:18:38 Sounds good, thanks caroline 18:18:48 +1 18:18:52 +1 18:19:07 #topic Project updates 18:19:18 anyone have updates on ongoing projects? 18:19:59 I am still expecting some partially isolated time for wiki around January. 18:20:34 Minor translation workflow improvements as discussed earlier 18:20:56 Helping family with a mess after sometime employer's death is stealing all my time currently. 18:21:38 I.e. let you do merges via the gitlab UI for the translation pull request tool 18:22:11 yes so the new workflow is pull request from the tool, then merge in gitlab, right? 18:22:25 Yup 18:22:48 #info new workflow for translations: pull from https://translate.koha-community.org/tools/ then merge in gitlab 18:22:56 I'm just waiting on the OK from Bernardo for me to update his server.. sure he'll be happy for me to but it's polite to ask ;) 18:23:28 thanks ashimema++ for helping on this :D 18:24:36 #topic What's been done so far 18:24:43 anything else? 18:24:43 it has been said that anything else is necessarily going to be incremental. 18:25:29 Project updates and what's been done so far are so similar... I never know the difference 18:25:53 I used the former designation. 18:25:55 I guess what's been done so far is smaller things not related to major projects 18:26:47 If there is nothing else, we'll move on 18:26:49 #topic Content development guidelines 18:27:10 I think we talked about adding alt text to images last time 18:27:34 #link https://wiki.koha-community.org/wiki/ReStructuredText_-_Tips_and_Tricks#Images 18:27:40 I've added it here 18:28:05 +1 18:28:08 From now on, if you update an image or add a new image, remember to add the alt text tot 18:28:10 too 18:28:44 +1 18:29:00 I was thinking maybe it would be a good time to change the image naming/numbering convention? 18:29:33 Incremental names are easy, but they cause problems when people work on the manual at the same time 18:29:55 We talked about this some years ago, but no decision was taken 18:30:15 I was wondering if anyone had suggestions/comments/ideas/objections? 18:30:49 That sounds like a good idea 18:31:04 I struggle with the images 18:31:57 I was thinking it might be better to update images in sections, rather than piecemeal. So do a couple of sections each release? 18:32:21 Maybe not practical though 18:32:45 Good idea 18:33:11 I don't think it's even thinkable to update this all in one go... we have over 1500 images 18:33:32 Like alt text, we can do it bit by bit as we update 18:33:37 Yep 18:34:30 what would be a good convention, instead of imageXXXX, do we add the chapter? Or simply give it a name? 18:34:46 ACQXXXX or ACQ-budgetscreen ? 18:35:13 or just budgetscreen 18:35:21 Just the filename? 18:36:05 yeah, I don't see any downsides to the filename 18:36:39 I would like to have them organized... just so that it's not one loooooong list 18:36:54 maybe we could separate them like they are in the directory? 18:37:09 by koha module? 18:37:10 Good idea 18:37:23 module and then under each, filename, filename, etc 18:38:24 sounds good, much easier to locate in a directory than the whole liste 18:38:32 Split up as they are in source/ images? 18:38:33 Ok so how about this, if you update or add a new image, use the filename instead of imageXXXX 18:38:48 and add the module section if it's not already there 18:38:58 makes sense? 18:39:21 Something like semantic_something-semantic_something_else-number would give a smaller more manageable scope to numbers. 18:39:46 is there a character limit on file name? 18:39:59 +1 18:40:01 I don't think so 18:40:19 there is a character limit on URIs 18:40:29 how many? 18:41:22 URI character limit is hundreds of characters and not easily reached except by automated extension of naming. 18:41:27 * oleonard whispers "Too many to worry about" 18:41:42 Filenames have an OS limit. 18:42:50 ok, I don't think we need to worry about this... we already have 60 characters in our URL for images, then if a filename is too big, we'll have to worry about it on a case by case basis 18:43:55 I like the idea of the filename 18:44:09 MS Windows has the biggest constraint on filenames where some low level systems could still be tied to old MS DOS pathname limits such as 255 characters for the full path. 18:44:19 without the extension 18:44:31 so filename rather than filename.png 18:44:57 OKay 18:45:32 #agreed use filename rather than imageXXXX for image aliases and separate like they are in the directory 18:46:00 +1 18:46:06 #info when updating or adding a new image, use the filename and if the section is not already created, create it 18:46:29 yay! I'm so glad we're doing this! It's always bugged me 18:47:00 We have some time left I wanted to talk about notes 18:47:00 :) 18:47:18 I noticed there is a command (or whatever it's called) to make notes look nice 18:47:33 let me just find one 18:48:16 https://koha-community.org/manual/20.11/en/html/installation.html#language-picker 18:48:25 see the blue box? 18:48:34 I think that looks really nice 18:49:03 maybe we can change the color scheme, but even if we can't I think we should do notes like this 18:49:05 The URI character limit problem can be tripped over when using long and/or many GET strings after the question mark for a bookmarkable context. Use POST requests but then bookmarkable context is more difficult. 18:49:07 what do you think? 18:49:20 it really does highlight the message 18:49:31 Yes, looks good 18:50:19 Ok I'll add the command on this page https://wiki.koha-community.org/wiki/ReStructuredText_-_Tips_and_Tricks 18:50:25 And standardises the indenting which is good 18:50:45 And I'll try to find out if there is a different one for "Important" 18:51:01 warning, perhaps? 18:52:20 #action caroline will add to the Rst tips and tricks page how to wirte notes 18:52:46 #info going forward use the note command when adding notes to the manual 18:52:58 ok cool! :D 18:53:21 anything else? 18:53:21 anything else is, like, necessarily going to be incremental 18:54:07 #topic Next steps 18:54:37 I don't think there are any major developments in 21.05 yet, so continue documenting 20.11 18:55:06 #info Priorities : continue documenting 20.11 for the time being 18:55:15 You have at least a month ;) 18:55:27 #info Check Taiga for things to write about :D 18:55:42 But also.. hopefully this time around Devs will be documenting as we go.. :) 18:56:08 I like your optimism ashimema! :D 18:56:26 :) 18:56:31 #topic Set time of next meeting 18:56:35 * ashimema will be trying to for his Devs anyways.. 18:56:57 lucyvh, weay be calling on you for help there.. hebe 18:57:12 4 weeks from now is Jan 7, sound good? 18:57:40 suits me 18:58:28 today the meeting was at 18UTC, maybe we can do it earlier 18:58:33 ashimena +1 18:58:46 7th Jan suits me 18:59:43 #info Next meeting: 7 January 2021, 15 UTC 18:59:47 #endmeeting