14:05:17 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 14:05:17 Meeting started Mon Nov 9 14:05:17 2015 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:05:17 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:05:19 #meetingname Fedora Docs 14:05:19 The meeting name has been set to 'fedora_docs' 14:05:20 #topic Roll Call 14:05:22 * randomuser kicks zodbot 14:05:49 .hello ryanlerch 14:05:50 ryanlerch: ryanlerch 'ryan lerch' 14:05:58 hello ryanlerch ! 14:06:00 * kirsti is in 14:06:06 hi randomuser! 14:06:11 uggg, time change 14:06:14 thanks for staying up :) 14:06:20 randomuser: :) 14:06:22 * zoglesby is here 14:06:44 * d0nn1e is here 14:09:01 well, I guess we're all here 14:09:11 #topic Follow up on last week's action items 14:09:37 * randomuser finds notes 14:09:49 #info randomuser published a bunch of stuff 14:10:24 linux-modder was going to start looking at the security guide, which we'll discuss during the guide section if he is around 14:10:36 aaand, thats 14:10:42 pretty much it for action items 14:10:59 #topic New Writers 14:11:13 any new writers here, or reports of them? 14:11:44 * ryanlerch is kinda a new old writer :) 14:12:32 ryanlerch: I don’t think most people where would remember you being active in docs 14:12:57 yeah, it was a long time ago :) 14:13:00 * randomuser assumes ryanlerch has done everything 14:14:09 how are you finding your reintroduction, ryanlerch ? Any questions or concerns? 14:15:10 not really -- just want to help to try to join docs and the magazine crew -- we are all writers for fedora, just dont really talk :) 14:15:14 * lnovich is here I forgot about the time change... 14:15:21 hi lnovich! 14:15:37 hello ryanlerch! 14:15:37 not *join*, more connect 14:16:09 * ryanlerch is not suggesting a merger between docs and the magazine :) 14:17:05 I think that the prevalence of technical content in the magazine demonstrates holes in the docs contribution model, but we don't have to get into that :P 14:17:20 also keen to jump in and help out in docs for the f24 cycle :) 14:18:19 but yeah, is that good enough for a re-introduction? 14:18:45 good enough :) 14:18:52 yay! 14:19:05 #topic Release Notes 14:19:10 we're done, hooray! 14:19:19 congrats to everyone on a successful F23 release 14:19:45 #action randomuser to reintroduce prerelease content into rawhide relnotes and push rpm 14:20:16 it takes about 15 minutes or so, let me know if you'd like to learn how and help maintain that package 14:21:44 randomuser, I'll be interested once you folks think I'm ready, but it's been a while since I've built an rpm from scratch. I can refresh my memory with my maximum rpm book 14:22:42 are the RPM's for pushing to the docs website? or for inclusion in the Fedora repos? 14:22:46 d0nn1e, sure, we can go through it together. 14:22:58 ryanlerch, nah, this is specifically the relnotes rpm, no others are packaged 14:22:58 * ryanlerch cant remember exactly how it works 14:23:13 ryanlerch: the repo, we still use publican to build the website 14:23:20 ah, i remmeber now 14:23:22 there was a scheme for publishing everything via koji + rpms but it didn't really grow legs 14:23:29 as it build it locally and git push 14:23:36 ah thats right 14:23:54 publican can build web rpms, that is what i was thinking of 14:24:03 sorry for sidetracking... 14:24:21 okay, not too much more we can say on release notes right now 14:24:34 #topic Publishing 14:24:52 I'm working on gathering up metadata and parsing it into different data structures 14:25:21 there's a JSON representation of the category structure and where articles fall within it right now 14:25:55 the next thing is to actually figure out what information should be presented to the visitor, and structure the data accordingly 14:26:58 I can think of a few ways; articles with similar tags, languages of an article, and so on - but I'm concerned that the result will be too heavy for effective browsing 14:27:28 ... as static content with client-side scripting 14:27:33 but we'll see, I guess 14:28:19 i was thinking that for an article, it might be good to have a field for aslo -- this could be useful for linking from apps.fp.org/packages and other places too 14:28:34 * randomuser nods 14:28:52 I've been thinking a lot about custom restructuredtext things, ryanlerch 14:29:14 ie ":rhbz: 125864" linking to said bug 14:29:16 randomuser: i'm willing to help with some mockups for this 14:29:32 ryanlerch, I was really, really hoping you'd say that :) 14:29:40 +1 14:29:42 how do we start ? 14:30:26 randomuser: that is going to be the tough part -- having some idea of content structure would be the first point to start at IMHO 14:30:45 actaully, not even structure -- more a list of article ideas 14:31:23 ryanlerch, I'll bullet point out some "what we know" stuff and put it up somewhere for you to read in the morning 14:31:25 from that, we could see the coverage, and build the idea of how to structure it 14:32:08 randomuser: if it helps, i spun up an etherpad the other day we used on for the release (to coordinate markerting stuff) 14:32:20 but it is still up if you need a scratchpad 14:32:41 I'd prefer some other way, etherpads are not very discoverable 14:33:04 yeah, i was more thinking for the inital dump of thoughts 14:33:16 anyway it seems that instance is down 14:33:35 * ryanlerch is a horrible sysadmin 14:33:39 heh 14:33:52 a github issue might do 14:34:05 keeps all the info in one place, anyway 14:34:53 is there a fedora docs github org? 14:35:01 but for whiteboarding... yeah, i can see a pad 14:35:10 ryanlerch, no, it's my personal 'anerist' project 14:35:26 .hello jbwilla 14:35:27 Southern_Gentlem: Sorry, but you don't exist 14:35:29 we could set up an org, though 14:35:33 haha! 14:35:38 .hello jbwillia 14:35:38 Southern_Gentlem: jbwillia 'Ben Williams' 14:37:01 http://etherpad-rlerch.rhcloud.com/ 14:37:06 #action randomuser to prep some info for ryanlerch to start mockup conversation 14:37:20 #link http://etherpad-rlerch.rhcloud.com/p/anerist-mockup 14:37:47 that could go away at any time, so only use for whiteboarding, then move somewhere else :) 14:37:53 * randomuser nods 14:38:09 randomuser: there is always pagure.io too 14:38:11 this is a solid action item for this topic; anything else we should cover? 14:38:28 ryanlerch, yeah, it will go there eventually 14:38:41 * ryanlerch is working on making it prettier too :) 14:38:42 sooner if more people are participating 14:40:22 #topic Guide Status 14:41:20 Capesteve looked over the firewall guide and gave me some notes, which I should probably implement 14:41:27 stephenw++ 14:42:08 #action randomuser to apply capesteve's review to firewall guide 14:42:32 you may have noticed grubdblom has dug into our bz queue, which is awesome - it could be useful again! 14:43:12 go grubdblom! 14:44:05 if pbokoc was around I'd ask if we really want to keep doing the powershell checksum, but since he's not, that's all I have on guides 14:44:12 who else has guide news? 14:46:12 is the powershell stuff broken again? 14:47:36 zoglesby, there's a new bug, apparently it doesn't work on some or all systems for ISOs > 2GB 14:48:21 also, while it's fun, it isn't the most straightforward or approachable method for getting a checksum 14:48:50 perhaps not worth the continued effort - I'm befuddled as to how array indexing keeps breaking 14:48:58 well, its better than linking to a tool whos domain expired and is now trying to give people malware 14:50:00 true; I think one of the writing tools we *do* recommend has checksum functionality, though 14:51:43 in what guide? I don’t see it in the install guide, and readme-burning-iso is out of date 14:52:12 the, err... suse writer thing 14:52:31 yep, now I see it 14:55:20 well, enough on that 14:55:27 let's skip to open floor 14:55:36 #topic Open floor discussion 14:57:40 go ahead, speak your mind... 14:58:13 anyone in Cz thinking of going to or submitting a talk to devconf? 15:00:37 I don't think anyone from cz is here 15:00:58 and, we're at the end of the hour - I'm going to close early, as I have another thing in a couple minutes 15:01:06 #endmeeting