14:02:05 #startmeeting Fedora Docs 14:02:05 Meeting started Mon Jul 10 14:02:05 2017 UTC. The chair is bexelbie. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:02:05 The meeting name has been set to 'fedora_docs' 14:02:15 .hello terminal__ 14:02:15 terminal__: Sorry, but you don't exist 14:02:26 .hello t3rm1n4l 14:02:26 .hello bex 14:02:27 terminal__: t3rm1n4l 'None' 14:02:30 bexelbie: bex 'Brian (bex) Exelbierd' 14:03:05 .hello rkratky 14:03:06 rkratky: rkratky 'None' 14:03:18 #topic Roll Call 14:03:36 hey all 14:03:38 I'm here but I'm in another meeting at the moment 14:03:47 hi 14:03:53 Why have only one meeting when you can have two :) 14:03:54 hi all 14:04:08 # topic Agenda 14:04:14 #topic Agenda 14:04:23 I believe we have only three topics to discuss, but would like ideas for more if needed 14:04:27 1. Release Notes Status 14:04:31 2. AsciiDoc Conversion 14:04:42 3. bex's harebrained idea (asciidoc publishing asap) 14:05:01 make that 4 14:05:06 1. Release Notes Status 14:05:12 2. Publishing for F26 14:05:17 3. Asciidoc Conversion 14:05:21 4. bex crazy pants idea 14:05:22 any others? 14:05:45 nothing else that i know of 14:06:28 ok, rolling with this 14:06:33 #topic Release Notes Status 14:06:42 rkratky, yruseva pbokoc ? 14:06:52 I got nothing 14:07:09 are the items you assigned yourself going well? on target? 14:07:10 I'm working through the ones I have assigned to myself, I'll be done in the evening 14:07:18 I mean, I§m all done w- mine. Reviewed and pushed, 14:07:54 sclark ^^ 14:08:17 looks like we have about 22 release notes issues still open 14:08:31 1 unaassigned 14:08:33 same for yruseva, she's working on pushing hers now 14:08:35 #link https://pagure.io/release-notes/issues 14:08:57 well, the issues being open are just there because people didn't close them yet. The commit log looks like we have a decent amount of content 14:09:07 I can take the unassigned one. 14:09:08 I haven't gone through them and checked though, it's just my impression 14:09:14 ok, so we may be good then 14:09:23 I also haven't had time to review them all either :( 14:09:33 hopefully we can move to close most of them 14:09:34 more like "not totally screwed, maybe", but yeah :) 14:09:41 pbokoc, exactly :) 14:09:53 I don't know that sclark and randomuser are with us 14:10:00 so we don't have their status, barring their tickets being updated 14:10:02 Oh, sgallagh commented that there's nothing to write about on the unassigned one. So I'm closing it, ok? 14:10:10 https://pagure.io/release-notes/issue/66 14:10:16 rkratky, cool 14:10:20 ? 14:10:32 Oh right. Yeah 14:10:51 so that's one more down :) 14:10:52 hah 14:11:11 ok, so we need to get the tickets reviewed for final closes and see if we need to prompt anyone 14:11:22 I will try to do it, but I get on a plane in the morning so i can't promise 14:11:24 sclark probably isn't, I think we're way out of his timezone, IIRC he was from Australia 14:11:32 ok 14:11:35 * yruseva rushes through the door 14:11:46 hopefully those will close too 14:11:48 I'll try to go through everything too this evening if I have the time 14:11:49 it's 10 pm here in west australia 14:11:57 midnight over east 14:12:09 I think we can move on to publishing - if there are no other comments. I don't know that reviewing the tickets one by one here will accomplish much 14:12:43 any objections ? 14:13:16 #topic publishing for F26 release 14:13:32 So, frankly, do we know how to do this? I don't think I have rights, and even if I do, I don't know how to do it 14:13:40 Can anyone other than randomuser do this? 14:13:43 I've got nothing here - randomuser kinda sorta said he'll do it 14:14:14 ok, conveniently I'll be in his timezone starting Wednedsday so I can lean on him a bit :) 14:14:16 yeah, pkovar could in theory. The problem here is, you need a version of publican that last shipped with F18 - so you need a VM with that and publican 14:14:28 pbokoc, ok 14:14:38 I believe we should work under the belief that randomuser will do this 14:14:41 i don't have a working setup at the moment 14:14:53 if randomuser does, thats great 14:15:05 at the same time, you need to push to the web.git repo on pagure, which you can't from that version of Fedora because of outdated ssl or something like that, pagure won't let you push 14:15:14 Is this ok: #action randomuser to publish F26 Installation Guide, SysAdmin guide and Release notes 14:15:14 but we dont have a backup plan. do we 14:15:29 pkovar, that's a nope 14:15:48 with a follow up #action bexelbie to follow up with randomuser as he wasn't online today 14:15:54 agreed? objections? 14:16:02 I mean, randomuser doesn't have a working setup, the plan is, run publican inside the VM, and then push from outside it - mount the disk image and use the host to do the actual push 14:16:08 and hope it works 14:16:21 bexelbie, agreed, although it would be best if we could catch him today 14:16:25 ah, okay 14:16:26 pbokoc, this is scaring me a bit - 14:16:33 and #4 may change this some 14:16:36 the release's tomorrow, so... 14:16:41 the due date is tomorrow? 14:16:42 #action randomuser to publish F26 Installation Guide, SysAdmin guide and Release notes 14:16:50 #action bexelbie to follow up with randomuser as he wasn't online today 14:16:54 ok, I'll try to find him today 14:16:58 * bexelbie goes to SMS him 14:17:21 bexelbie, eh, it's just a new ridiculous hack on top of another ridiculous hack that we've been doing for multiple releases now 14:17:29 pbokoc, ok 14:17:32 :o 14:17:34 I've SMS'ed him 14:17:49 do we have more to cover in publishing? otherwise we can move on to getting out of this hack :) 14:17:57 yes 14:18:03 pkovar, go ahead 14:18:18 also, i don't think anybody tested that the new location of the web repo actually works 14:18:28 i mean the scripting behind it 14:18:34 oh yeah, that's a good point 14:18:35 as the old fedorahosted repo is now gone 14:18:45 so, even if we manage to push to pagure 14:18:55 the publishing might turn out to be broken 14:18:58 on the scripting side 14:19:05 Is this aobut whether docs.fp.o actually updates? 14:19:06 just that you know 14:19:16 yes, pretty much 14:19:37 i couldn't test it due to pagure not talking to f18 anymore 14:19:59 ssh? 14:20:02 pkovar, ok - my hope is randomuser can find a way through this but we need to actually be doing it at this point to patch the hack it seems 14:20:05 monkeypatch if you will 14:20:19 yes, ssh, terminal__ 14:20:32 alright, i'll be around too, tmrw but no promises 14:20:58 I'll be on a plane most of the day for everyone - so I will not know what happened :) 14:21:12 actually that isn't completely true 14:21:15 I have a 7 hour layover 14:21:18 * terminal__ is freaking out 14:21:20 so maybe I can scream fire with everyone else :) 14:21:44 pretty much 14:21:50 ok, so any more fun with publishing or can we talk about getting out of this situation? 14:21:56 btw I *just* got a reply from one of the SMEs 14:22:11 yruseva, ugh and hooray 14:22:29 bexelbie, he replied promptly, I asked late :) 14:22:41 :D 14:22:51 hooray and ugh then :P 14:23:04 moving on to the next topic then, barring an objection 14:23:08 #topic asciidoc conversion 14:23:22 terminal__, has been working on converting the installation guide and system admininstration guide to asciidoc 14:23:27 can you update us terminal__ ? 14:23:55 I haven't done a lot recently, although I tacked on that RHEL guide links stuff to the sysadmin guide as an issue 14:24:19 but i did run another attempt at converting the install guide 14:24:25 how'd that go? 14:24:35 didn't make any difference 14:24:38 git says no change 14:25:17 ok, does that mean we have it and think it is roughly good in asciidoc or tha thte conversion failed? 14:25:31 I have to relocate, back in 2 minutes 14:25:46 it's not looking too bad, but there's some missing references 14:25:57 ok 14:26:06 2 figures, one table 14:26:32 not difficult, just got to work out where it's ref'd and insert the references 14:26:41 ok 14:27:14 but there's another RHEL guide linked in the install guide 14:27:24 the kernel crash dump guide... 14:27:30 .hello 14:27:30 linuxmodder: (hello ) -- Alias for "hellomynameis $1". 14:27:46 so of our big three (install, sysadmin, and release notes) it sounds like 2 are roughly converted to asciidoc, barring content updates (which I know pbokoc needed to make) 14:28:00 terminal__, it sounds like we could leave those for now and not be any worse off than we were 14:28:07 pretty much 14:28:10 if we wnated to prioritize the makrup change 14:28:10 ok 14:28:21 how long does it take to get the guides into "passable" asciidoc shape? 14:28:29 like if we started on release notes tomorrow 14:28:34 bexelbie, we did that last release cycle I'd recommend we not repeat and get further back 14:28:46 linuxmodder, did what? 14:29:27 bexelbie, this: [10 14:28:00]  terminal__, it sounds like we could leave those for now and not be any worse off than we were 14:29:36 but whatever not my call 14:29:51 linuxmodder, those are the RHEL guide references - they have been there for a long time, I am not sure I follow what you are suggesting 14:29:57 depends on if there's anything else i missed in scanning the doc, but it's not as massive as the sysadmin guide...if there's no formatting issues, i'd just have to update the refs, and make sure the links work 14:30:13 again nvm Doesn't apparently matter 14:30:38 linuxmodder, ok - I just didn't understand what you were suggesting - I am very happy to hear it and would like it to be considered if you wish to rephrase it 14:30:51 sysadmin unless someone worked on it recently had tons of outdated stuff in it 14:31:07 This is true 14:31:09 I have converted it to asciidocs, and updated all the links 14:31:16 Install Guide also needs some help 14:31:18 recently == < 2 months ago 14:31:31 it's still the same content though 14:31:41 does talk about F19 in the httpd section also 14:31:44 linuxmodder, I agree that the content needs help 14:31:53 but then so does the apache web page 14:32:01 but we haven't got content offers from people, so we are trying to get the format to one that will make contribution easier than DocBook 14:32:08 your patches to content would be greatly welcome 14:32:18 the oldest references any of those should have is 24 tbh 14:32:34 any older refs are beyond outdated and irrelavant 14:32:40 yup...but it's not going to be ready by the time F26 drops 14:32:57 needs more people updating content and getting it updated 14:33:36 the guides themselves are all outdated, but at least in asciidocs it's a lot easier for new contributors 14:33:55 and potentially existing 14:34:04 the conversion process takes minutes 14:34:23 so from a markup perspective, we could use what the new converted materials and probably have only a few display errors - is that a good read? 14:34:47 from a content perspective we need help from people to get that shaped up and hope that asciidoc will help makethat easier for folks like linuxmodder to contribute 14:34:48 it's not terrible 14:34:51 is that a good read/ 14:34:52 ? 14:35:26 markup looks fine for the most part...like i said a few missing references, the rest is content, and some formatting, but it's readable 14:35:35 terminal__, cool 14:35:43 any other markup conversion questions? 14:36:30 not from me 14:36:58 conversion is straightforward, it's just getting the doc updated and into shape after that that takes a little time 14:37:18 ok then I'd like to see if I can get meeting-feedback on something 14:37:22 #topic new publishing 14:37:31 not that i've got my head around the asciibinder stuff yet 14:37:33 I suggest we try to move off of DocBook with F26 (even now) 14:37:34 but yeah 14:37:50 It will not publish tomorrow, so tomorrow's publishing would be the last one with Docbook 14:38:09 my proposal is to use asciibinder + ryanlerch's theme to create a new docs site 14:38:23 we would use terminal__'s converted Sysadmin, install guide, and (not even started) release notes 14:38:31 to publish those three on a new docs.fp.o that only has F26 14:38:44 F25 and older would be on legacy.docs.fp.o (or something similar) 14:38:47 * randomuser shuffles in the back door 14:38:50 this will cause the following problems 14:38:52 o/ 14:38:56 1. There will be some display errors 14:38:58 o/ randomuser 14:39:05 2. There will be no translations at first 14:39:18 but we will get asciidoc publishing and conversion 14:39:26 we will have the building blocks for automated publishing and testing 14:39:41 on the translation front we aren't republishing regularly there now, so at least we will be consistent in languages 14:39:55 we have a process that should be 85% clean now that we can use once translation verifies the new strings 14:40:03 but it will have problems and we will have to fix them 14:40:15 I really think we can do this as I have piloted most of it with budget.fp.o 14:40:18 including publishing and staging 14:40:30 any comments? Is this completely insane? 14:40:59 all sounds reasonable to me 14:41:07 sounds fine to me also 14:41:11 we might not have another choice if web.git doesn't work 14:41:40 we need to get away from trying to rely on F18 and pagure to talk to each other :P 14:41:41 terminal__, it is a huge request, but how long would it take to convert the Release notes once the last content was pushed into docbook? 14:42:13 conversion itself takes minutes... 14:42:21 wait, what? Why would we not be able to use pagure to publish docbook? 14:42:23 but the cleanup you do is part of that 14:42:24 it's the verifying references and formatting after 14:42:35 yeah 14:42:47 how big are the release notes? 14:42:52 terminal__, I could help with the conversion. 14:43:01 I mean the sysadmin guide took me like 2-3 weeks 14:43:18 rkratky, that'd probably be necessary 14:43:19 RNs are relatively 'easy' content -- there shouldn't be much to fix. 14:43:34 esp. if the doc is large 14:43:49 randomuser, well, have you tried that? With the workaround of pushing from outside the VM - we're concerned that the migration to pagure was just someone changing a .git/config to point to pagure and pushing, and nobody actually set it up so that the pagure repo replaces the fedorahosted one on the website 14:43:56 we don't know for sure though 14:44:10 do we think it is reasonable to say that we would have all content converted to asciidoc and ready to be used by 24 July? 14:44:18 assuming no major problems 14:44:29 with the goal of pushing translation strings that week and publishing by 1 August? 14:44:30 also by the way, we have a better version of the script available internally, it has a lot of bug fixes. It's still not perfect, it still requires manual fixes to get the thing to even build, but it's likely to be better than the upstream version 14:44:36 pbokoc, i suspect that is the case, can check into it 14:44:56 #chair randomuser pbokoc terminal__ rkratky 14:44:56 Current chairs: bexelbie pbokoc randomuser rkratky terminal__ 14:45:01 bexelbie, I'm pretty confident Io could have the RN doc ready within one day of it being done. I tried with other docs. 14:45:01 sorry forgot to do that 14:45:04 anyone else I missed? 14:45:08 I'll ask someone to get it somewhere publicly available, like on github or something 14:46:25 a large majority of the issues i see from docbook to asciidoc conversion seem to be the manual linebreaks everywhere 14:46:40 with the current docscii method that is 14:46:52 #action randomuser to update infra to pull from https://pagure.io/fedora-docs-web for publishing 14:47:03 that's the right repo, correct? 14:47:26 randomuser, should be, yeah 14:47:26 terminal__, RNs have no (or very little) content other than regular text. The linebreaks shouldn't be an issue. 14:47:38 cool 14:48:28 randomuser, is the current docs publish, literally them copying the content of fedora-docs-web to the servers? 14:49:34 bexelbie, last I checked the proxies would clone/pull the git repo 14:49:49 once an hour 14:49:55 randomuser, cool that is how the new process works for budget.fp.o so we have even less work to do for a conversion :) 14:50:16 right, static content is fairly easy to distribute 14:50:19 the budget site has two branches, prod and stg so we can separate stage from prod and make it easy 14:50:39 my next goal is to get infra to do that on demand, and not via cron, but that is not a blocker 14:51:21 i'm curious but it sounds like a topic for another meeting 14:52:18 randomuser, yes and one after we have converted 14:52:29 I seriously believe we should commit that this is our last docbook publish 14:53:23 as you the person most responsible for providing the successor at this point, bexelbie, that's very encouraging to hear 14:53:51 to do it, we need to commit to get content changes to land in the asciidoc that terminal__ is working on 14:54:09 if we have support, I can work on building it out for success over the next two weeks 14:54:17 so what guides are ready to be published today in the docbook version 14:54:18 I genuinely can't get it done sooner because of hte LATAM org fad 14:54:19 ? 14:55:50 randomuser, nothing right now; I need to wrap up release notes and then I'll do a quick update for the install guide 14:56:26 for the sysadmin guide I guess we'll just increment the release number and pretend it's up to date, I don't think there's much more we can do at this point in time 14:56:36 I'll ping you when I'm done. Or e-mail the list or something 14:57:18 (of course if anyone else wants to do the sysadmin guide I'll be happy to hand that over...) 14:57:41 i can do once overs but no cycles til next week 14:57:42 okay, I'll be around after work 14:57:55 wrt sysadmin & installguide 14:58:03 and now I need to go find myself a meeting room for yet another meeting, yay 14:58:07 content reviews are helpful at any time, linuxmodder 14:58:41 yes, but in that case I'd save your energy for after the asciidoc conversion, because that's going to need a whole load of once overs 14:58:50 I'm out, l8r 15:00:36 I don't have a lot of spare time this week, works been pretty busy last few weeks, I may have a little time mid week atm but that's possibly about it 15:01:01 hi, folks, I believe we have the room next? (qa) 15:01:09 #endmeeting