20:00:34 #startmeeting General IRC meeting 13 December 2017 20:00:34 Meeting started Wed Dec 13 20:00:34 2017 UTC. The chair is kidclamp. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:34 The meeting name has been set to 'general_irc_meeting_13_december_2017' 20:00:44 #topic Introductions 20:00:44 #info wahanui, a bot that has become sentient 20:00:53 #chair cait 20:00:53 Current chairs: cait kidclamp 20:00:56 #chair Joubu 20:00:56 Current chairs: Joubu cait kidclamp 20:01:02 #info George Williams, Northeast Kansas Library System 20:01:09 #info Nick Clemens, ByWater Solutions 20:01:18 i have soup on the stove, probably not good to make me chair :) 20:01:24 #info Caroline Cyr La Rose, inLibro (Canada) 20:01:29 #info Katrin Fischer, BSZ, Germany 20:01:29 can't hurt 20:01:30 #info Jonathan Druart 20:01:33 #link https://wiki.koha-community.org/wiki/General_IRC_meeting_13_December_2017 20:01:45 #info Bob Birchall, Calyx, Australia 20:01:50 #info Michael Cabus bywater solutions Princeton NJ 20:01:51 #info Joel Sasse Plum Creek USA 20:01:52 #info Chris Cormack, Catalyst IT, NZ 20:01:53 #info Thomas Dukleth, Agogme, New York City [Currently in California until 27 Dec.] 20:01:56 #info Clint Deckard Anact NZ 20:01:59 Your Linode, bugs, has exceeded the notification threshold (90) for CPU Usage by averaging 94.7% for the last 2 hours. 20:02:01 #info Brendan Gallagher ByWater 20:02:17 #info Victor Grousset, BibLibre, France 20:02:21 oh 20:02:24 if the bugzilla is slow, its because someone is beating the hell out of it currently, so ill be sorta here, sorta trying to fix that 20:03:02 * Joubu guesses it's greenjimll :D 20:03:13 rangi: the kind of beating that also happened with the wiki? 20:03:35 #topic Announcements 20:03:45 floor is open 20:03:51 It is still my birthday 20:03:55 tuxayo: don't know, I don't look after the wiki 20:03:59 but probably 20:04:02 happy birthday thd 20:04:05 happy birthday thd 20:04:08 happy birthday thd 20:04:14 #info it is thd's birthday all day 20:04:17 I have delayed the party until after the meeting. 20:04:22 happy birthday thd 20:04:35 happy birthday 20:04:40 I usually have to collect a 2 year old from school at this time. 20:05:04 #info Josef Moravec, Munucipal Library UO, Czech Republic 20:05:09 #topic Update on releases 20:05:36 In other more important news, at home in New York I have redundant internet from two different ISPs ending a 9 month period of no internet at home. 20:05:53 #info Mason James, NZ 20:06:05 #info Liz Rea, Catalyst NZ 20:06:16 #info 17.11 see dev meeting, will be pushing and announce string freeze for 15th 20:06:23 ranig any 16.11 update? 20:06:31 rangi even 20:06:33 same as that 20:06:46 #info ditto for others :-) 20:06:49 rangi: there is a test failing, I submit a follow-up. I guess you saw it 20:07:06 submitted* 20:07:10 yep thanks 20:07:11 #info see dev meeeting for 18.05 goals and notes 20:07:40 #topic FAQs - website, manual or wiki? 20:08:05 cait? 20:08:05 cait is, like, the best friend you could ever have 20:08:08 oh sorry 20:08:12 the soup :) 20:08:25 ok, we currently have some faqs on the website and some in the manual 20:08:35 i tihnk they are all in need of updating 20:08:48 the question is where we want them to go 20:08:57 and i am throwing in the wiki as a third option ;) 20:09:15 I think the manual 20:09:29 they'll get looked at each release (in theory) 20:09:38 The wiki is more accessible 20:09:45 i think website makes it a bit hard because not so many have access 20:09:46 i.e. more people can contribute 20:09:51 linking to the wiki or manual make both sense to me 20:09:52 I was thinking the wiki 20:09:52 i agree with wizzyrea, the manual is where new people tend to look first 20:09:54 everyone has manual 20:09:57 access as well 20:10:02 to submit patches 20:10:07 The wiki should be the easiest place for the most current information, however, document structure of FAQs is better suited to the website or manual. 20:10:16 yeah, but it's not easy to understand 20:10:22 with the wiki we can react to mailing list questions etc more quickly 20:10:28 it's a bit less complicated even than the manual 20:10:33 so i am a bit more pro wiki 20:10:51 I don't like the wiki because it is TOO easy to update, so gets bad information more easily. 20:10:56 and less oversight. 20:11:03 I am also pro wiki. and we could add the best questions to the manual 20:11:04 I would suggest the wiki and have links to the faqs in the manual 20:11:31 wizzyrea: i check the recent updates regularly, atm it seems mostly ok 20:11:40 theres way more wrong info on the wiki than there is right 20:11:42 wiki and cherry pick for manual? I think both are usefull in diff ways 20:11:45 There is no reason information cannot be in multiple places with a message to check the wiki for most current updates. 20:11:46 ^ 20:11:51 thats a separate problem tho 20:11:51 both? Put them in the manual and update the wiki? Or the reverse 20:11:52 but the stuff that is right is very usefull 20:12:08 the stuff that is right should be in the manual 20:12:09 imo. 20:12:14 duplicates means double the work tho 20:12:19 i tihnk the wiki is more technical 20:12:21 no, automatically 20:12:22 we could also divide it 20:12:27 but not sure if that will work well 20:12:33 i'd prefer one spot 20:12:42 hm documentation team is not around 20:12:46 we could do some 4th solution 20:13:08 We could always ad an extension or create some automated method of pulling from one place to populate another. 20:13:15 which is a dedicated FAQ with easy access but that is neither the website, wiki, or manual. 20:13:20 s/ad/add/ 20:13:30 would require a new account etc probably 20:13:51 depends on where it is. 20:14:03 I don't care for the idea of a fourth place - three's enough 20:14:18 well at least one of those places would be going away 20:14:21 (the website) 20:14:26 wizzyrea: Do you have some particular dedicated FAQ system in mind? 20:14:52 I don't 20:14:56 because I haven't looked 20:14:59 :) 20:15:16 i think as all need to be cleaned up right now, we could move them all into one place - or should decide to have clear categories on what goes where 20:15:19 I think it makes sense to have the wiki (for easy edit) then pull the good info for the manual every major release 20:15:21 but I would be happy to look 20:15:40 that sounds like an awful lot of work - bc someone has to go in and find the good info 20:15:47 computers can't judge that. 20:15:48 * thd has investigated automated FAQ generation in the long past using vim. 20:16:13 I agree one place is best, and the wiki is easiest to edit ... 20:16:14 the bar doesn't have to be high, but I feel there does have to be a bar 20:16:19 I do not expect 100 new Q&A every 6 months 20:16:25 as long as there is a clear link to it in the manual 20:17:08 well for the log I think that will be a mess 20:17:09 doesn't the documentation team have to go over our commits in the manual anyway? 20:17:09 there are questions repeating on the mailing lists - those could be turned into faq 20:17:14 but you do you 20:17:16 in the manual yes 20:17:19 push is moderated 20:17:24 wizzyrea: some custom markup nomenclature could sort the problem of distinguishing one thing from another in a wiki based FAQ for selection into other locations. 20:17:47 for the record i agree with wizzyrea 20:17:50 so it's not necessarily more work, just different 20:18:27 should we have a vote between wiki and manual? 20:18:30 i think website is out? 20:18:52 #info Joy Nelson Bywater 20:18:53 website is least accessible and highest barriers. 20:18:56 so yes. 20:18:57 only a few people can edit the website 20:19:18 kidclamp: could you start a vote maybe? 20:19:36 just a last note - manual is versioned, so have to be careful with links from website, maybe a page between with links for the faq to different versions 20:19:55 one sec 20:19:58 I guess the real question I am asking myself is, who are the faqs supposed to benefit, and where are they most likely to look to find them 20:20:08 BobB: Only a few people can edit the website live but there is no reason we could not institute a drafting process for something such as FAQ content for the website. 20:20:09 none of those are problems that can't be solved 20:20:23 I could probably pretty easily pull in faq's from the manual 20:20:28 to the website 20:20:34 When I was new, I was far more likely to look on the wiki than the manual because the wiki was easier to navigate and search 20:20:37 so just manual or wiki? or either or both? 20:20:41 #info Aleisha Amohia, Catalyst IT, NZ 20:20:47 ah but the manual is much different now 20:20:57 It has gotten a lot better 20:21:31 its just another task for someone 20:21:50 it's always been a task for "someone" 20:21:51 :) 20:22:13 i think we can start reworking them once we have agreed on one spot 20:22:16 #startvote Should we maintain the FAQ as a wiki page, or in the manual? Manual, wiki 20:22:16 Begin voting on: Should we maintain the FAQ as a wiki page, or in the manual? Valid vote options are Manual, wiki. 20:22:16 Vote using '#vote OPTION'. Only your last vote counts. 20:22:21 right now it's quite confusing 20:22:36 #vote wiki 20:22:36 both? 20:22:36 both is probably best :) 20:22:36 we have the wiki for the quick and easy edit, then the manual team pick and reorder items to put them into the next manual version 20:22:36 then wiki is reset with the content from the manual 20:22:36 yes dup of info is bad, I am just tryin to find an agreement for the 2 points of view :) 20:22:54 i think people might be confused when looking at the different versions - search 2 spots 20:22:55 #vote Manual 20:23:08 and the manual team is using kanban and stil have the framapad open i think 20:23:11 #vote wiki 20:23:13 so lots of options 20:23:22 #vote both... 20:23:22 Joubu: both... is not a valid option. Valid options are Manual, wiki. 20:23:33 #vote Manual 20:23:45 (well actually #vote anything but the wiki) 20:23:53 #vote Manual 20:24:00 #vote Manual 20:24:03 #vote Wiki 20:24:10 both, but if I have to choose... wiki 20:24:13 abstain - no valid option, so being quiet :) 20:24:18 #vote wiki 20:24:27 #vote Manual 20:24:53 #vote Manual 20:25:01 #vote Manual 20:25:12 #vote Manual 20:25:25 last call 20:25:42 #abstain 20:25:50 do not know how to do that 20:26:38 #endvote 20:26:38 Voted on "Should we maintain the FAQ as a wiki page, or in the manual?" Results are 20:26:38 wiki (4): kidclamp, caroline, talljoy, georgew 20:26:38 Manual (8): clintD, wizzyrea, josef_moravec, bag, alexbuckley, thd, aleisha_, rangi 20:27:06 at leats we got a decision now and can start cleaning up :) 20:27:08 so let's write that page now 20:27:16 so let's improve that page now :) 20:27:27 hehe 20:27:28 #info vote results 4 for wiki, 8 for manual, FAQ will be maintained on the manual 20:27:29 #link https://koha-community.org/manual/17.11/en/html/17_miscellaneous.html#faqs 20:27:42 wizzyrea: should we let you know once stuff has been moved or how to go about it? 20:28:17 i think first would be to make it a separate chapter :) 20:28:20 ot of misc 20:29:18 move on? 20:29:23 the other thing with the manual that i just remembered, is it is translatable 20:29:38 ^^^^^^^^^^^^^^^^^ 20:29:40 that's all the topics, just next meeting 20:29:49 so discussion has time if wanted 20:30:00 yep just let me know how you want to handle links to it 20:30:06 I can make the existing faq go away lickety split 20:30:06 (without someone having to maintain multiple pages) 20:30:34 https://koha-community.org/manual/17.11/fr/html/17_miscellaneous.html#faqs eg <-- only partially done 20:30:36 wiki should also be translatable but the procedure for that was sidestepped in the rush to put up a wiki when the old one went down. 20:31:02 Next doc meeting is too far, I'd like to get opinion about what we already discussed few months ago: How can we merge the online and offline manuals 20:31:19 We should remove the help pages and onboard the manual 20:31:40 I have concerns 20:31:43 we also need to start writing some guides, the manual is good, when you already know koha 20:31:45 the first step would be to link to the online manual, then let the ability to provide a local path to point to a local version 20:31:50 1. not every koha has internet access 20:31:59 yes, what I said :) 20:32:23 ok phew 20:32:23 then I think we should add a way to edit the manual (for local use in a first time) 20:32:40 is there a bug for that Joubu? 20:32:45 and eventually the ability to merge request (but let's mark that TODO LATER) 20:32:50 technically those files are already editable with correct config, but I think the how to has been lost to the mists of time 20:33:08 plus slightly terrifying 20:33:34 there is 18472 and 18483, I am not willing to push them. That's why I am looking for another option 20:33:59 ideas/opinions? 20:34:29 bug 18472 bug 18483 20:34:29 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18472 enhancement, P5 - low, ---, veron, Passed QA , Add system preferences to manage online help system 20:34:30 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18483 enhancement, P4, ---, veron, In Discussion , Customised help: Enhance staff client with news based, easily editable help system 20:34:30 think about it for the next manual meeting :) 20:35:24 something else or we move on to set the time of the next meeting? 20:35:25 While you are 'all' here for the IRC meeting, we are looking forward to having Koha as part of the Catalyst Open Source Academy next month. Thank you all for being part of it :) 20:35:34 Long ago we had a discussion ... 20:35:41 oh yes, tag your bugs academy 20:35:50 please and to be thanking you 20:36:08 we investigated software for managing the manual ... 20:36:51 ... as nengard was doing much of the work alone her preference became the choice 20:36:57 Would be probably possible to automatically generate integrated help pages from manual? 20:37:32 ?? 20:37:50 and then probably something like bug 18438 on top of it to local customization? 20:37:50 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18438 major, P5 - low, ---, alexbuckley, Pushed to Stable , Check in: Modal about holds hides important check in messages 20:38:16 nengard: You do not remember that discussion. Actually we may have voted in your preference. 20:38:27 i didn't read back to see what you were talking about :) 20:39:05 josef_moravec: I think it's good to have the manual outside of the Koha code, otherwise we are going to embed all the translated versions of the manual 20:39:13 its moot now 20:39:20 cos it's not even xml anymore 20:39:58 #topic Set time of next meeting 20:40:18 I think we should have a manual package that koha-common depends on 20:40:23 and you get both 20:40:27 but they are independent 20:40:52 we discussed last time to make it an option 20:40:52 or even that it doesn't depend on it, it could be optional, for example if you install Koha and have internet, you don't need the manual package 20:40:58 There were a few options and are probably more now which manage documentation in different formats online, print, etc; work well with collaboration; support version control in git well; etc. 20:41:01 use the installed manual locally or link to the external 20:41:04 i tihnk that would be nice 20:41:22 for all the hosted koha an online manual on the internet is not a big issue 20:41:29 yeah, we could create a manual vhost on the server, so your koha server could have manual.mydns.com 20:41:36 and you just go to your own copy 20:41:51 a package could do all that for you 20:42:32 and it could set a flag that says "hi I'm installed locally, all your links should point to me!" 20:42:41 if we have a configurable url 20:42:52 it'd be configurable just like the koha ones are 20:42:55 you could also have a customized manual for all oyur servers if you decided to 20:43:05 Next meeting: 10 January 2018, 14 UTC ? 20:43:22 ok for me 20:43:48 wizzyrea++ 20:44:13 #info Next meeting: 10 January 2018, 14 UTC 20:44:16 Yaay 14 UTC 20:44:22 can I end? 20:44:41 ok by me 20:44:42 yep 20:44:45 yes 20:44:45 #endmeeting