21:02:25 #startmeeting Documentation IRC Meeting 31 August 21:02:25 Meeting started Thu Aug 31 21:02:25 2017 UTC. The chair is cait. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:02:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:02:25 The meeting name has been set to 'documentation_irc_meeting_31_august' 21:02:26 * BobB needs coffee 21:02:30 #topic Introductions 21:02:31 #info wahanui, a bot that has become sentient 21:02:31 16:00 p.m here 21:02:44 #link https://wiki.koha-community.org/wiki/Documentation_IRC_meeting_31_August Today's agenda 21:02:45 #info Bernardo Gonzalez Kriegel, Argentina 21:02:50 #info Bob Birchall, Calyx , Australia 21:02:51 #info Lee Jamison, Marywood University 21:02:57 #info Katrin Fischer, BSZ, Germany 21:03:02 #info Alex Sassmannshausen, Brussels 21:03:03 #info George Williams, Northeast Kansas Library System 21:03:04 #info Clint Deckard-Anact NZ 21:03:08 #info 21:03:19 #info Kelly McElligott Bywater Solutions 21:03:24 #info Jessica Zairo - Tampa Florida ByWater Solutions 21:03:25 #info Karen Holt, ByWater Solutions 21:03:30 #info Freddy Pelayo, Ensabap, Peru 21:03:37 #info Irma CALYX Australia 21:04:00 wow :) 21:04:04 cait++ 21:04:16 glad to see you all here to talk about documentation 21:04:19 moving on to our first topic 21:04:39 #topic How does it work? 21:04:55 #info Francois Charbonnier, inLibro, Canada 21:05:16 some of you might be aware that we switched the tools used to write and generate the manual 21:05:42 yes 21:05:44 up to 17.05 DocBook was used 21:05:53 #info Jonathan Druart 21:05:54 and the manual was one big XML file that was a challenge to edit 21:06:06 you'd need specific tools able to handle the file 21:06:35 so for 17.11 rangi has converted the manual to use reStructuredText and Sphinx for generating it 21:06:49 the new syntax is easier to edit 21:06:59 he has also split up the manual into several files 21:07:08 #info Brendan Gallagher ByWater 21:07:35 #info up to 17.05 the manual was using DocBook, now using reStructuredText and Sphinx 21:07:49 and the display is better :) 21:07:52 #link https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual Information how to edit the manual 21:08:06 so now that the technical bits have been improved 21:08:17 we need to start working out how to move forward with how to keep it up to date 21:08:32 but as this is still the 'how does it work topic' - let's talk about this later 21:08:46 if you go to the wiki, you will see that we have tried to describe ways on how to edit the manual 21:08:53 #info Barton Chittenden, bws. 21:08:56 the easiest way is using gitlab, as it doesn't require you to install anything 21:09:25 #info TGoat 21:09:26 #info TGoat is going to work on fundraising 21:09:26 you can do it all in the browser, make changes to a file and create a 'merge request' that the documentation team will review and then merge into the manual 21:09:35 and I took the liberty of creating a quick YouTube video to demonstrate how to make changes and commit them to be merged! 21:09:48 thx! 21:10:09 #link https://www.youtube.com/watch?v=tiwH7-wO2Gs video tutorial how to use GitLab 21:10:10 #info LeeJ created a YouTube video to make the process easier to understand 21:10:13 I can see it is linked in to the Getting_Involved page. That's cool :-) 21:10:24 LeeJ++ 21:10:29 :) 21:10:42 nicely jzairo has created a new merge request just before the meeting, so I can show you ;) 21:10:48 #link https://gitlab.com/koha-community-devs-users/kohadocs/merge_requests Merge requests 21:10:53 jzairo++ 21:11:12 if one wants to, you can of course also use git locally and submit changes from there, there is also some instructions for that 21:11:23 and LeeJ has started work to add the tools to the kohadevbox 21:11:40 #info LeeJ has started to add the kohadoc tools to kohadevbox 21:12:03 yes! with tcohen's help we have the ability to enable kohadocs as well as sync the kohadocs repo from the user.yml file 21:12:45 a great plus for Sphinx is that it#s super easy to generate the manual in different formats 21:12:58 html for our websites, but also epub 21:13:00 it's just one command 21:13:05 with that being said, creating a merge request is yet untested via command line as I have had a hard time figuring out a way to connect the keys GitLab requires to do it 21:13:18 #link https://gitlab.com/koha-community-devs-users/kohadocs Instructions on how to create the manual locally 21:13:41 so if anyone would like to help me figure out a way we'd be grateful :) 21:13:57 ok, any questions about the technical stuff? I will try to answer best I can :) 21:14:07 yes 21:14:20 how do we translate it? :) 21:14:28 you are jumping topics heh 21:14:31 is there a way to generate the manual for 16.05 with sphinx 21:14:33 ? 21:14:57 both good questions 21:15:06 I think we will talk about translating a little later if that's ok? 21:15:16 yep 21:15:25 francharb: I think it would technically be possible, but I am not sure if it makes sense 21:15:38 with the conversion the links in the help files in Koha have to be changed 21:15:55 and also a lot of work has been done to fix some other problems with the conversion like fixing the links inside the manual between chapters 21:16:04 it's because the translation would be easier from the splitted po files that comes with the new documentation process 21:16:09 ok 21:16:12 got it 21:16:38 Joubu++ for doing those 2 things for u 21:16:39 s 21:17:05 scripting++ :) 21:17:12 @cait, @Joubu issues fixed manually? 21:17:13 francharb: I'll give you the answer just as soon as RDA is ready 21:17:38 francharb: bug 18817 21:17:38 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18817 minor, P5 - low, ---, jonathan.druart, Pushed to Master , Update links in the help files for the new 17.11 manual 21:17:49 for the links from the Koha codebase 21:18:26 and this is the change for the manual: https://gitlab.com/koha-community-devs-users/kohadocs/merge_requests/34 21:19:08 ok 21:19:15 thanks 21:19:22 if it's ok i will move on 21:19:27 we will get to the translation bits sooner 21:19:36 #topic What's been done so far 21:19:49 #info We set up instructions and documentation on how to edit the manual 21:20:07 #info Alex Buckley added new chapters for the installation process and onboarding tool 21:20:16 yay! 21:20:27 heh :) 21:20:32 #info Lee J has updated and added missing system preference up to the current state of things 21:21:03 #info Joubu has fixed the inter-manual links and 17.11 will link to the new manual from the help files 21:21:18 #info Jessica Zairo has added information about the Article Request feature 21:21:27 did I forget something? 21:21:35 uhhh...not that I can think of 21:21:40 me either 21:21:47 so we have started, but a lot of work remains :) 21:21:56 hi 21:21:56 hello, wizzyrea 21:22:10 since Nicole started her new job the manual hasn't been regularly updated and we need to do a bit of catch up there 21:22:34 #link https://annuel2.framapad.org/p/KohaManualTodo to-do list for manual work 21:22:39 yeah, from time to time we come across the gaps 21:23:04 I have started a 'framapad' that works like an etherpad, so everyone can just go in and add something 21:23:27 #action all if you notice something is missing from the manual or needs to be corrected, please add a note to the to-do list 21:23:58 I have listed some of the bigger tasks at the top, but there is also a heading for every chapter 21:24:25 for example you could also help by taking the release notes and checking them against the manual, so we get a list of things to add 21:24:54 you can see that jzairo has added a note 'added JZ' to MarcItemFieldsToOrder (description needed) 21:25:09 that's the one in the merge request I showed earlier 21:25:14 jzairo++ 21:25:30 I'd also like to point out that from what I've looked over, the cronjobs section is a bit...haphazard :) 21:25:40 oh yes 21:25:45 heh 21:26:01 #info Katrin has removed the SOPAC2 related chapters 21:26:11 cait++ 21:26:19 #link https://koha-community.org/manual/17.11/html/ Sneak peak for the 17.11 manual created with Sphinx 21:26:36 peek... 21:26:39 ? 21:26:50 peek :) 21:27:00 (but it's ok) 21:27:13 at the moment that's generated manually by rangi - so it will not be updated immediately with a merge, but you will be able to see your changes there 21:27:22 and also good for checking what's still missing of course 21:27:55 perhaps it might be helpful if whoever adds a note to the to-do list to include a bug number next to their entry if it would be helpful in documenting the item to be added 21:28:00 is it planned to document how to generate the manual bu yourself? 21:28:02 it won't be linked to for now - as we are still working on things and 17.11 has not been released yet 21:28:18 francharb: we already have, take alook at the gitlab start page for the kohadocs I linked earlier 21:28:35 it's super easy, clone the kohadocs repo, install some packages, run vrey few commands 21:28:53 perfect! 21:28:53 perfect is the enemy of good 21:29:32 kellym++ I just saw another merge request in my inbox :D 21:29:38 ok, now comes the hard part 21:29:50 I am working with Jzairo on learning the process! 21:29:56 #topic Next steps 21:30:04 the manual is huuuuuuuge 21:30:26 and getting huger :) 21:30:36 we think keeping it current can't be done by a single person - we need a team of people doing this 21:30:57 ^exactly 21:31:04 so we worked to make it as easy as we can and we can help everyone who wants to give it a try 21:31:25 it's been a bear for a few years now 21:31:34 could we split it apart? 21:31:44 but rangi and me can't write it all :) even with the help we already got, the more the better it will be 21:31:55 and I've been helping when I can :D 21:32:17 barton: if someone wanted to take on a chapter or so - just note it on the todo list 21:32:50 @cait, to me the problem is that sometimes I'm not even sure how new features work 21:32:51 francharb: I'll give you the answer just as soon as RDA is ready 21:33:14 #info manual writing is not a single person job - needs a team of people 21:33:21 ouch huginn, too soon. 21:33:26 Part of this could be solved by making it a requirement of the QA process to have a draft chapter for the manual for new features perhaps? 21:33:31 (was that already decided upon?) 21:33:36 teamwork! 21:33:39 not yet 21:33:42 can we ask the sign-offer to do a bit of wrap up about what they tested and how the feature works? 21:33:52 I second atheia's suggestion 21:33:57 me too 21:34:01 Well — personally I think it should be the dev's responsibility… 21:34:02 francharb: we could but actually the developers should provide that with their commit messages 21:34:04 and test plans 21:34:05 test plans are awesome. at least it gives context for where to go even if minimal. 21:34:08 that's actually a great idea 21:34:12 if anything is unclear, it's always ok to note on the bug and ask 21:34:26 +1 21:34:40 also sign-offers can take notes of course, where something additional had to be set up 21:34:58 agreed. 21:35:07 i try that when I run into sometihng, but not sure we can make it a general rule, but it#s a rule that we should have test plans and descriptive commit messages 21:35:16 Joubu just sent an emai ltoday to remind devs :) 21:35:17 I think asking sign-offers to do more is problematic considering how hard it can be to get people just to sign off on things 21:35:29 georgewilliams: yeah, I am a ibt worried about that too 21:35:34 true 21:35:37 +1 21:36:08 that's what so important about fundraising georgewilliams .. but that's a whole different topic 21:36:12 but yeah, if you don't understand, please ask and make notes 21:36:15 even documentation bug reports 21:36:22 Whereas if an organization / individual has a stake in adding a feature, they would also have the incentive to document it (even if they don't enjoy that process) 21:36:38 cait the 'todo' list is where everything is controlled? 21:37:00 so if working on something, we should grab it there? 21:37:05 #action all - a 'Manual' keyword has been added to Bugzilla - please mark bugs that you think needs something added or changed in the manual (ideally with a comment) 21:37:22 it would be sad to document something and then find someone else beat you to it 21:37:27 BobB: for now I think yes - I wanted to keep it a bit lower barrier than bugzilla even 21:37:31 I think that documentation should be a QA requirement -- not necessarily that the dev needs to do it themselves, but they should be responsible for making sure that it gets done. 21:37:32 if that doesn't work we can of course do something else 21:37:41 I think the developper must provide a description of what the new ft/enh is supposed to do. But it would make sense to have dedicated persons to "translate" developper language into manual sentences :) 21:37:56 barton +1 21:38:04 Joubu+ 21:38:14 barton++ Joubu++ 21:38:18 Barton, I like your idea. 21:38:29 Joubu+ 21:38:37 I will be terrible at describing correctly what my features do :) 21:38:38 Joubu++ 21:38:42 #action all - if you start working on some addition to the manual, please add a note on the to-do list (like 'cait working on this') 21:39:46 here now 21:40:03 there is also a module for documentation on Bugzilla 21:40:13 Whilst I understand your perspective Joubu [some people just aren't great communicators — or there might be language issues for devs], at the same time I feel devs should be expected to take responsibility for the code they add by documenting it. 21:40:14 I will try to add saved searches for both and the links to the wiki and the to-do list 21:40:28 hi rangi 21:40:33 #info Indranil Das Gupta, L2C2 Technologies, India 21:40:40 That's why I like Barton's harder requirement of the dev/organization having responsibility to get someone to write the documentation. 21:40:46 #action cait to add saved searches and links to them for the Manual keyword and Documentation module from Bugzilla 21:40:51 That could be a dedicated specialist or anyone else… 21:42:17 I am not sure we have the people for that 21:42:24 The manual needs to keep a certain homogeneity/consistency, if 30 different guys are going to describe features in 30 different ways... it will be a mess 21:42:25 but devs should try to document as best as they can 21:42:34 Joubu: thats what editors do 21:42:39 im happy to edit 21:42:43 rangi+ 21:42:53 but i dont have time to read everyones features to figure out what they do 21:42:58 I would prefer to work with someone, incrementaly 21:43:07 if they write it as best they can, i can edit that 21:43:17 (new features this is) 21:43:18 also that is too much work 21:43:31 the workflow is that the documentor submits a merge request? then an editor can finesse it, is that right? 21:43:31 rangi: yes, it's more or less what we said, devs have to describe the feature in the commit message + test plan already 21:43:44 Joubu: yeah, but they don't ;) 21:43:49 BobB: yes 21:43:50 bag: supporting undocumented features is a lot of work too. 21:43:55 yep or can help the committer improve it 21:44:20 maybe they don't, but they should 21:44:24 yeah i think if we have a good manual, we are also less likely to break features noone knew about (hopefully) :) 21:44:31 (and have to) 21:44:31 I mean for an editor barton ;) 21:44:54 bag: we have a coms team at work i can lean on for help 21:44:55 Joubu — just to clarify, do you also agree that having this description, whether as a draft chapter or extensive commit messages, should be a QA requirement for new features? 21:45:06 ah k, 21:45:11 atheia: itis 21:45:14 what they cant do is figure out from a 10 line commit message what the feature does 21:45:15 sorry saw your later messag later :-) 21:45:30 but they can certainly tidy up peoples english 21:45:35 i mean we already have rules about test plans and commit messages 21:46:36 sweet - up - let’s get all the commits first - and then we can figure out the quality aspect - and it looks like rangi’s got ideas for that 21:46:36 we must all have some specs/docs from the people who want the feature right? even making them available would help 21:46:47 yep 21:47:07 and if a library writes something and is not sure about how to get it in the manual 21:47:08 jzairo++ 21:47:11 I am willing to format it 21:47:16 would it be worth entertaining the idea of a documentation/manual notes textarea in the bug header? For example, say under the field "Text to go in the release notes"? 21:47:28 in terms of bugs for new features 21:47:33 i think its easier to find people to 'fix' stuff, than to write stuff :) 21:47:36 hmm not a bad idea 21:47:43 LeeJ +1 21:47:46 vaguely hard with screen shots. 21:47:53 LeeJ +1 21:47:59 I was going to suggest to revive the koha-docs mailing list for things like that 21:48:11 LeeJ: I am not sure, but the fields might be limited in size 21:48:14 good point wizzyrea - can we hack bugzilla to meet that need? 21:48:15 cait +1 21:48:37 i like the ml idea 21:48:43 I'd subscribe to koha-docs in a heartbeat. 21:48:44 because people dont need a login for that 21:48:50 sec I wil get a link 21:48:55 hm they have to sign up tho 21:49:02 yeah but thats it 21:49:07 then the mail just arrives 21:49:08 is a login a big barrier - (I don’t know) 21:49:10 Why not use the regular one with a [koha-docs] tag? That can motivate people to be involved if they see stuffs going on 21:49:15 wizzyrea maybe have some sort of annotation mark in the potential documentation textarea corresponding to a bug attachment of screenshots? 21:49:16 #link https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs koha-docs mailing list - send us things for the manual! 21:49:46 LeeJ: the area is very small, maybe easier to just write a comment and set the keyword 21:49:52 my honest opinion is that bugzilla isn't the place for that 21:49:53 or sent an email to the koha-docs 21:49:54 hell if people just put a letter in an envelope and mailed it to me 21:49:55 it's not the best tool. 21:50:01 it would be better than now 21:50:08 +1 21:50:12 but i think the ml is good, because lots of people can see it 21:50:12 just throwing out ideas :) 21:50:25 we can certainly use the release notes from bugzilla too 21:50:28 I think we need to built this up - we will happily take any submissions and help people who want to help 21:50:33 teo 21:50:37 yep even 21:50:55 ill take it by carrier pigeon if need be :) 21:51:22 [off] https://wiki.koha-community.org/wiki/Chris_Cormack ? :) 21:51:37 how about filing a linked documentation bug to every new feature / enhancement? The QA tool can check for existence linked doc bug for enh etc? The doc team / volunteers can track the open doc bugs and expand on the dev notes with screenshots and such? 21:51:41 [off] hahahahahaha 21:51:56 yes thats the documentation bird 21:52:30 indradg: that would be good, ideally, but also just random pastes, etc are fine too, what we are lacking is content, not process :) 21:52:51 yes content is the key 21:52:54 it's also a little easier for now to just add the keyword to the bug 21:53:08 less work for the person going through those atm 21:53:21 if suddenly we get so much, that we need to implement stricter process, we can deal with that, i will love that to happen, but for now, however people want to submit changes is great 21:53:24 but we might get to a more refined process once the ball is rolling 21:53:33 yes, what she said 21:53:36 :) 21:53:50 what is the current content rate - 2~3 a week? 21:53:59 a month 21:54:10 wow 21:54:24 yep, we got room to improve ;) 21:54:33 without LeeJ, jzairo, cait, and kelly .. its almost zero 21:54:40 holy..... 21:54:41 That’s probably an important data point to be included as an #note or whateever in the meeting notes 21:54:42 to give some examples 21:54:47 we are looking for people to write: 21:54:50 - patron clubs 21:55:05 - advanced cataloguing editor (rancor) 21:55:25 I can get patrons clubs in there 21:55:26 - housebound 21:55:33 and an update for rancor 21:55:39 :) 21:55:44 jzairo++ 21:55:46 just to give examples for big stuff that is missing 21:55:49 and being missed! 21:56:05 awesome jzairo - we need to recruit others to help submit ;) 21:56:19 probably a good thing to bring to the kohaus meetings jzairo 21:56:20 Bywater has some great tutorials (love them) - a lot of that would make good manual content 21:56:22 Ooh housebound has no documentation? 21:56:23 cait: maybe a good starting point would be just to compile a list in the to-do of just the titles of missing entries? 21:56:38 I should be able to get a draft for that… 21:56:40 atheia: developer missed to write it up ;) 21:56:41 vi misc/cronjobs/CONFIGURE.gmail 21:56:47 indeed *blush* 21:56:47 oops, sorry 21:56:49 georgewilliams and CrispyBran are here jzairo 21:56:58 and TGoat ^^ 21:57:00 heh, multitasking Joubu 21:57:01 (wt is that??) 21:57:09 LeeJ: yep - I think release notes woudl be good starting point, check enh listed there 21:57:26 #action atheia to write something about housebound 21:57:36 atheia++ you’re all good dood 21:57:37 with the tool alexbuckley_ is working on, it would be great to link the bits straight to the manual too 21:57:41 jzairo: do you really want to take on both? or start with patron clubs? :) 21:57:42 ??? 21:57:49 (the list of heres what changed in your upgrade too) 21:57:52 tool even 21:58:00 I have been working with kidclamp on rancor 21:58:13 cool 21:58:19 and khall talked to me about patron clubs 21:58:31 so I can try and tackle both of those 21:58:48 #action jzairo to take on patron clubs and advanced cataloguing 21:59:39 jzairo++ 21:59:46 cool :) 21:59:53 i am sure there will be more on the list to pick soon! 22:00:03 i'd like to add another topic to talk about translation, if that's ok? 22:00:14 ok 22:00:15 #topic Translation 22:00:19 yes! :) 22:00:25 sorry you had to wait so long Joubu :) 22:00:28 #link https://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=runnamed&list_id=211550&namedcmd=Open%20Documentation 22:00:33 cheer up Joubu :D 22:00:55 barton: coudl you add in Keyword = Manual? that would be awesome 22:01:03 hm not sure you can do or 22:01:04 barton: does not work 22:01:13 so translation 22:01:13 so translation is working now too? 22:01:24 with DocBook the translation was done using a po file 22:01:24 Hi, I was working on this a bit 22:01:31 Joubu: I think I need to make it public. 22:01:40 Sonia noted on the list that she would really like to add translated screenshots too 22:02:09 to translate you need to generate po files, and then translate them 22:02:30 cait: Keyword = Manual => Zarro Boogs found. 22:02:39 I need to install a tool, sphinx-intl 22:02:44 barton: hm can't be - I will try and take a look later 22:03:26 for example: make gettext; sphinx-intl update --language=fr; translate po in source/locale/fr/LC_MESSAGES/; make -e SPHINXOPTS="-D language='fr'" html 22:04:07 i used old translations, with a bit of scripting to fix things 22:04:32 here you can see the result: http://translate.koha-community.org/manual/16.11/ 22:04:35 which version are you working on @bgkriegel? 22:04:42 those are old languages 22:04:48 ok 22:04:51 16.11 22:04:56 francharb: not the last one 22:05:04 but it's doable 22:05:13 I think Sonia was also aksing how to get the manual files for 17.05 22:05:29 with all the changes coming in, i am not sure when it will make sense to start translating 22:05:34 each language adds 2~3 Mb of space, perhaps we could add the files to the repo 22:05:44 po files 22:05:45 po files are outdated 22:05:45 do the translations carry over if no changes? 22:05:58 It should be 22:06:08 I'm afraid I have to clock off — sorry for leaving mid-meeting. Au revoir! 22:06:11 the same way translation works for the interface 22:06:22 yeap 22:06:35 we don't stop translation for the interface because of new features... 22:07:13 I guess it's doable having new material for the manuel and translating at the same time 22:07:14 I too have to head out..I'm available by email if anyone needs to reach me :) 22:07:27 I added those po files on translation server: http://translate.koha-community.org/projects/man1611/ 22:07:55 bgkriegel++ 22:07:56 thanks @ 22:08:11 so what's the next step? i think the first Sphinx manual we have is 17.05 - right rangi? 22:08:21 Question : how often should the manual po files be updated ? 22:08:21 but I need to do the same job for 17.05 22:08:22 #info Zeno Tajoli, CINECA, Italy 22:08:37 16.11 use sphinx 22:09:25 ah, i htink we just didn't link it then 22:10:12 #info bgkriegel is working on creating po files for the new manuals 22:10:26 about the screenshots - I told Sonia it should be possible 22:10:27 The result is not good for arabic, perhaps I need to research a bit more how to do it for RTL languages 22:10:59 maybe sending the fiels with the same file names? 22:11:18 #info still some issues with Arabic (RTL languages) 22:11:48 so basically, what can we say to Sonia? 22:12:11 When will she be able to translate the manual in French? 22:12:14 Is it planned to have this page http://translate.koha-community.org/manual/ generated automaticly every day, every week? 22:12:26 bgkriegel: (Hi!!) What need to be done to be ready? Do you need help? 22:12:29 So we can work on the manual translation and see the results ? 22:12:30 yeap, will do it 22:12:59 i didn't know about that page! 22:13:06 ( Hi Joubu:)! ) 22:13:09 For now, we can't control the the translation easily 22:13:15 #link http://translate.koha-community.org/manual/ translated manuals overview page 22:13:24 @cait, I discovered it recently as well 22:13:25 francharb: I'll give you the answer just as soon as RDA is ready 22:13:39 I love you huginn 22:14:26 ok, moving on? :) 22:15:03 #topic Getting more people involved 22:15:09 actually we talked a bit about this 22:15:14 About https://koha-community.org/documentation/ ? 22:15:21 please if you run across someone who you think would want to help, tell them :) 22:15:31 or if someone has a great documentation they could share 22:15:34 not sure I understood, maybe I missed something, will reread 22:15:38 There are missing link 22:15:41 links 22:16:24 ok, before we close 22:16:32 any questions left open? things people want to add? 22:16:48 Manuals in french and italian are not linked 22:17:04 tajoli: not generated yet 22:17:25 will do later 22:17:44 #topic Set date of next meeting 22:17:54 is there interest in holding another meeting, maybe in a month? 22:18:44 yes cait 22:18:54 i think we should, for sure 22:18:55 someone please let me know when the manual links on the website need to be added for italian and french 22:18:56 yes 22:19:05 september 6th? 22:19:21 october you mean? 22:19:22 that's next week cait 22:19:31 #info Let wizzyrea know when links need to be added to manuals on k-c.org 22:19:38 just can't read a calendar 22:19:41 :) 22:19:44 do you mean october 6? 22:19:51 29th i think 22:19:55 was what i meant :) 22:20:00 last week of the next month 22:20:32 not Friday please - it becomes Saturday here 22:20:47 i was aiming for thursday 22:20:50 it's too late for me :) 22:20:51 28th 22:20:54 same time? 22:21:06 same time works for me :) 22:21:15 same time is good here 22:21:26 28th Sept? 22:21:28 thanks for the meeting. hope i can make it for the next one! anydate should work for me 22:21:30 bye 22:21:31 good for me 22:21:32 yes clintD 22:21:48 About links to italian manuals: I think could be added as soon as possibile. 3.20, 3.22 adnd 16.05 are 100% translated 22:21:56 #agreed Next meeting will be on 28th September, 22 UTC 22:22:06 #endmeeting