14:00:33 #startmeeting fedora-docs 14:00:33 Meeting started Mon Aug 21 14:00:33 2017 UTC. The chair is bexelbie. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:33 The meeting name has been set to 'fedora-docs' 14:01:14 #roll call 14:01:20 #topic Roll Call 14:01:23 .hello bex 14:01:26 bexelbie: bex 'Brian (bex) Exelbierd' 14:01:28 kjandova__, are you here? 14:01:42 I'm here 14:02:44 I think we might be it :| 14:02:57 however, I would like to outline the way forward for docs with you here so it is logged publicly 14:02:58 ok? 14:03:09 ok 14:03:33 .hello2 14:03:35 x3mboy: x3mboy 'Eduard Lucena' 14:03:39 x3mboy, o/ 14:03:43 bexelbie, o/ 14:03:48 I am going to be right back - I am sorry - one sec 14:03:53 Np 14:03:54 * bexelbie goes for emergency coffee 14:04:02 #topic Pause for Emergency Coffee 14:04:05 * x3mboy too 14:04:07 :D 14:05:51 * kjandova__ three :D 14:06:13 #topic Rolling out the New Docs System 14:06:19 x3mboy, thank you for your patience 14:06:28 I am sorry - lunch suddenly hit me hard and I needed this espresso 14:06:46 it would have been faster, but kjandova__ beat me to the coffee machine :P 14:06:57 So, down to business 14:07:15 we have a test website that everyone seems ok with (as in no big problems left) 14:07:25 #link https://bex.fedorapeople.org/fedora-docs-web/ 14:07:38 I believe that to get this publishing, we need to do the following 14:07:59 rename pagure.io/docs-reboot/ https://pagure.io/fedora-docs/ 14:08:14 I believe that may be able to be done by me - or it may require an infra ticket 14:08:20 this is a good final name and seems easy to locate 14:08:22 any opinions? 14:08:48 It's a good option to go 14:09:02 If infra ticket is needed, I can open it 14:09:13 cool 14:09:22 I'll see if I can get the rename done and let you and kjandova__ know 14:09:43 I'll try this right after the meeting 14:10:05 next seems to be that we need to move docs.fp.o to be published from the new repo and have hte existing docs.fp.o move to docs-old.fp.o 14:10:07 sound right? 14:10:27 Yes 14:10:34 This will 100% sure require an infra ticket to make happen. x3mboy would you want this or would you like kjandova__ to chase this down? She is here to help us too :) 14:10:53 Ok, let her do it then 14:10:53 :D 14:10:57 :D 14:11:04 * bexelbie catches up on action items 14:11:11 I'm a little nervous today 14:11:17 Better to now take anything 14:11:17 :D 14:11:25 s/now/not/g 14:11:36 #action bexelbie to try to migrate docs-reboot to fedora-docs namespace. If that fails, x3mboy or kjandova__ will help with opening a ticket to do it 14:12:07 #action kjandova__ to open an infrastructure ticket (like this one: https://pagure.io/fedora-infrastructure/issue/5973) to move docs.fp.o to docs-old.fp.o and replace docs.fp.o and docs.stg.fp.o with the new publishing repo from #1 14:12:16 at this point we are live :) 14:12:20 however, there is housekeeping to do 14:12:42 I believe we should move all the old docs repos to a new name space, fedora-docs-old/XXX where XXX is the repo name 14:13:12 I suspect the right way to do this is to collect the names and then email docs@fp.o and if no one objects in a few days, do the move 14:13:13 wdyt? 14:13:47 kjandova__, would you be willing to work on the list of "old docs" repos? 14:14:05 * randomuser arrives 14:14:46 o/ randomuser 14:15:15 bexelbie, sure 14:15:20 randomuser, do you have a bouncer to read back? 14:15:28 I'm super excited about our progress, kjandova++ 14:15:28 randomuser: Karma for kjandova changed to 1 (for the f26 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:15:47 #action kjandova__ to figure out which repos should be moved to fedora-docs-old 14:15:48 bexelbie, I do, you're talking about renaming the docs-reboot repo to something more suggestive of production use 14:16:05 randomuser, yes :) and renaming the old repos into a -old space 14:16:07 for cleanliness 14:16:30 we are also replacing content repos? 14:16:55 new repos for System Administration Guide, Installation Guide, and Release Notes were created under docs-reboot 14:16:58 to make them faster to clone 14:17:07 ah 14:17:07 we can merge that into the old guide repos if there is a strong feeling to do so 14:17:38 nah, having the old content would be useful during conversion but after not so much 14:17:46 agreed 14:18:02 I think we need to do an Authors harvest as the authors names in at least one of the guides seems wrong ... but yeah 14:18:37 Is the current docs gropu the right group to have commit access to the new repos? 14:19:03 https://pagure.io/group/fedora-docs 14:19:04 well, it's a pagure group in this context, not a fas group, right? 14:19:11 randomuser, yes 14:19:19 should be good 14:19:25 Also, can we please simplify the System Administrator's Guide and get rid of content that doesn't make sense for Fedora and especially Fedora Workstation? 14:19:29 Like OProfile? 14:19:40 jhradilek++ 14:19:41 randomuser: Karma for jhradile changed to 1 (for the f26 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:19:53 jhradilek, your PR is very welcome. right now I'd like to focus on getting the publishing done in a separate parallel process 14:20:10 Also, we need to keep content that makes sense for all editions of Fedora 14:20:12 As we move towards more atomic content, per-article author attribution might have to go away too 14:20:16 we shouldn't be writing docs for just one edition 14:20:38 * bexelbie would like to see the content set up to easily reduce for just the edition the user is working with 14:21:08 https://pagure.io/docs-reboot/system-administrators-guide <--- jhradilek 14:21:10 Fair point, but I would expect us to try and focus on the majority of users first. 14:21:32 filtering per edition sounds like a good asciibinder sprint, bexelbie 14:21:37 bexelbie: Thanks. 14:21:41 so far we have been focused on getting publishing even working 14:21:47 no one has really done any serious content work 14:21:51 I would welcome seeing some 14:22:01 randomuser, yes! 14:22:22 #action bexelbie to make sure the fedora-docs group has access to the new repos 14:22:29 so I don't forget 14:22:50 jhradilek, perhaps you could section that off as a "fedora server" section or something 14:23:06 Sorry, I'm back 14:23:14 * bexelbie would like to see if the idea of separate install guides that draw from common shared content for each edition would make sense 14:23:21 so users don't get shown material that doesn't apply to them 14:23:25 bexelbie: I'll see what I can do about that pull request, but I really shouldn't be promissing anything. :) 14:23:46 includes in general are interesting, but I don't think we need to make it a priority 14:24:05 I think we will be getting better systems from the workshop at flock 14:24:06 a system that relies heavily on includes would be difficult for the uninitiated 14:24:14 it can be for sure 14:25:09 the last bit of houskeeping I can come up with is to republish the publican site one last time when it is moved to docs-old.fp.o to not have any F26 material and to include a note on how to find the current content 14:25:16 I believe only you could do that randomuser 14:25:42 hopefully not *only*, but yeah, I can do that :) 14:26:28 "This is our most desperate hour. Publish for us randomuser. You're my only hope. " 14:26:34 #action randomuser to prepare branch of web.git with only content #action bexelbie to update the new docs site front page with the translation commment change from JB 14:27:43 again so I don't forget 14:28:18 If we do this, I think we are done and can move on to focusing on content, translations, CI/CD and other fun stuff 14:28:23 did we miss any basics? 14:29:46 .hello kjandova 14:29:48 kjandova__: kjandova 'Kristýna Jandová' 14:30:11 Should we talk about what comes after this (and post-Flock?) 14:30:54 personally, I'm looking forward to writing some stuff instead of struggling with publishing tools 14:31:07 :) 14:31:17 #topic What happens after all of this? 14:31:28 huge +1 to randomuser helping to wrangle content :) 14:31:41 * bexelbie would like to do a training on how to manually publish and use that to get docs written 14:32:30 indeed, it would be good to have that workflow documented and well known 14:32:46 yep 14:32:58 I am hoping that will happen as a result of people hitting content post-rollout 14:33:09 we def need that and I am happy to help contribute to that doc 14:33:20 * x3mboy expect bexelbie going into the classroom session as instructor 14:33:34 x3mboy, ugh - was just thinking that :P 14:33:37 About How to publish a doc into the docs 14:33:50 I think that would be a good thing for randomuser and me to collaborate on :) 14:33:57 * bexelbie hopes he doesn't see what I just did there 14:34:00 :) 14:35:12 x3mboy, give me some time to recover after Flock and to talk randomuser into it - and one or both of us will do a classroom session 14:35:28 Perfect! 14:35:34 sorry, yes, a classroom session would be better after flock 14:35:39 I can set up everything when you're reade 14:35:42 ready* 14:35:59 I like how you say "once we figure it out ourselves" randomuser :) 14:36:41 On the translation front, JB is ready to help and seems eager to get that process rolling. We will definitely find some po4a bugs (or if someone is feeling froggy write a new asciidoctor API thing with bugs that are different from the po4a bugs) 14:36:42 ha, bexelbie, I like how you make it "we" as if you are as ill-informed as I 14:37:02 but hopefully JB's work will result in translators feeling empowered and loved again 14:37:11 you were talking about CentOS CI, do we all have access? 14:37:28 I have a CentOS CI job 14:37:34 right now I think only I have access that can be fixed 14:37:38 it is not yet set up or running 14:37:43 it just exists as a placeholder 14:38:03 I need to schedule some time with bstinson after Flock to get it reasonably configured so that we have it executing a script in source control 14:38:11 then the folks that wanted to help with CI will have an easy time doing so 14:38:32 * randomuser nods 14:38:32 I am not trying to cut anyone out of hte bstinson meeting and will publicize it when it happens 14:38:51 I just figured I'd be kind to bstinson and serve as the Fedora front-end to him and then I'd reshare information 14:39:00 I also just like making bstinson hear dings from his irc client 14:39:03 bstinson, bstinson bstinson 14:39:04 :) 14:39:20 say my name 3 times and I appear, you know :) 14:39:26 dude! 14:39:51 post flock I intend to say your name with a calendar invite :) 14:39:55 oh hey Brian 14:40:20 \o/ i'm pretty excited to see this docs stuff run through CentOS CI 14:40:55 I am excited to see a Jenkins job triggered by fedmsg :) 14:41:03 ohh shiny 14:41:22 and I haven't told bstinson about some our ideas around branch and PR building yet :P 14:41:25 but baby steps :) 14:42:32 I know the minutes have a wall of action items 14:42:36 anything else we should talk about today? 14:42:58 hmm 14:44:17 I think we're good 14:44:25 cool 14:44:27 Thank you everyone! 14:44:41 I'll spend some time work on the renames and my stuff today. I fly out on Wednesday and don't want to leave anyone blocked. 14:44:45 kjandova__, are you coming to Flock? you should be bought many beers for your efforts 14:44:45 closing the meeting in 5 14:45:41 randomuser, no, I'm not coming to flock, so no beer for you :D 14:45:59 wait, does this mean I forced to go out for a beer with kjandova__ 14:46:01 scandal! 14:46:12 #endmeeting