13:59:37 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 13:59:37 Meeting started Mon Nov 18 13:59:37 2013 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:59:38 #meetingname Fedora Docs 13:59:38 The meeting name has been set to 'fedora_docs' 13:59:38 #topic Roll Call 13:59:55 * jjmcd 14:00:10 I'm here! 14:00:11 * Capesteve waves 14:00:16 * jhradilek <-- 14:01:47 * pkovar is here 14:01:54 * randomuser refills his coffee 14:03:20 okay, that's time enough for roll call 14:03:30 #topic follow up on action items 14:03:56 jhradilek, can you share what you learned of publican, for the record? 14:04:39 Oh, sure. 14:05:32 So, the Fedora Documentation website and the infrastructure behind it is, of course, a high priority task for Rudi. Unfortunately, his hands are full right now, but he will be able to work on it in December. 14:05:58 Also, Publican 4 should be released very, very soon. 14:06:11 that's exciting 14:06:24 And it provides some very interesting features, like distributed sets in Git. 14:06:39 distributed sets? 14:06:50 http://jfearn.fedorapeople.org/en-US/Publican/3.2/html/Users_Guide/chap-Users_Guide-Using_sets.html#sect-Users_Guide-Using_sets-Distributed_sets 14:06:52 * randomuser isn't awake enough to follow along yet 14:07:28 Basically a set of books, but instead of having all of them in one repo, you can just add links to the repos to publican.cfg. 14:07:37 also, I like their branding there 14:08:55 oh, so we could create a single set out of all Fedora books? 14:09:27 so I could have one working directory, and build all the guides like `publican build ${opts} --config install-guide/installation-guide.cfg` ? 14:09:34 or.. what's the benefit? 14:09:37 that sounds like there might be some problems with that - unique IDs being necessary across all books, for example 14:10:28 pbokoc: Publican *tries* to solve that problem for you, but it doesn't always work. :) 14:11:10 randomuser: I don't think it will affect anything on our website, but it allows me to build all my books for a particular product with just one command. 14:11:19 ah, i see 14:12:45 thanks, jhradilek 14:12:50 #topic release notes 14:12:59 not a lot to say here 14:13:12 jjmcd i see has been poking at the radio stuff 14:13:21 Yeah, and a couple others 14:13:32 But still more I would like to do 14:13:36 this week is shot tho 14:13:40 * randomuser checks tx 14:13:58 looks like POTs need to be pushed for that, jjmcd ? 14:14:13 Yes, I think there is no more on radio anyway 14:14:31 I was hoping to get sci/tech done but ran out of cycles 14:15:30 * randomuser nods 14:16:07 jjmcd, if you discover anything that impacts the ARGuide, be sure to open bugs 14:16:24 I need to take a hard look at that - so much to do there 14:16:47 I guess I should make a to-do list in BZ 14:17:03 Gotta admit, been spending a lot more time on my BZ than Fedora's 14:17:26 there's a better chance of getting help if there are tickets :P 14:17:32 yepper 14:17:34 oh, you set up your own bz instance, jjmcd ? 14:17:49 Yeah, that "graph" thing is way helpful 14:18:10 Have a cronjob that prints my hot items each morning 14:18:14 * randomuser has been considering rt3 14:18:41 jjmcd: Try "task" {see http://taskwarrior.org/projects/taskwarrior/wiki } for short ToDo lists {say, less than 30 tasks } 14:18:56 Well, I have a couple hundred 14:19:19 I was using a purpose-built php script but just couldn't easily deal with the complexity 14:20:00 This will sound like a heresy from a Vim user, but have you tried Org Mode? :) 14:20:24 task 1: learn org mode 14:20:31 * jjmcd loves org mode 14:20:39 sound like you need a Priority Matrix 14:21:18 It is a tad tedious setting up all the dependencies in BZ, but the dependency graph and attaching stuff is a big win 14:22:11 I guess a couple hundred is an exaggeration, only 154 open ATM 14:22:39 This being retired stuff is hard 14:22:50 * randomuser sneaks in and adds tasks to jjmcd's queue 14:23:34 #topic Guide Status 14:23:39 Probably a third are publican docs NOT Fedora 14:24:05 pbokoc, i saw you opened a big pile of task bugs against the installation guide 14:24:53 yeah, I did. Not much has happened since though, I'm going to be crunching everything at the last minute 14:25:28 #info there are bugs opened for the Installation Guide if anyone wants to pick up some writing 14:27:16 luckily afaik most of the new features are fairly minor, so the most time-consuming task is probably going to be taking new screenshots for the installer 14:27:38 pbokoc, someone has probably already done that 14:27:38 and general housekeeping like checking URLs 14:27:47 just not for us :( 14:28:05 what do you mean? On the wiki? 14:28:23 i saw croberts floating a ticket on the marketing trac about it, although i don't know if that's installer screenshots or desktop ones 14:29:00 aha. Allright, I'll check if there's anything I can shamelessly steal 14:29:26 i'll ping if there is anything 14:29:30 ...that i find 14:29:32 ok 14:29:47 #info screenshots are needed for the installation guide 14:31:10 jhradilek, what do we need for the sysadmin guide? 14:32:40 * satellit_ screenshots of f21 anaconda: http://wiki.sugarlabs.org/go/Fedora_21 14:33:26 see, pbokoc - it was on the sugarlabs wiki, of course :) 14:33:33 thanks satellit_ 14:33:37 yw 14:33:43 hehe, where else :) 14:34:27 well, it's for F21... but there don't seem to be many differences 14:34:27 randomuser: First of all, I need to go over the open bugs and apply all patches that were submitted to me. 14:35:07 f20 has screenshots also see link on top of page 14:36:00 satellit_, ah, right. Thanks! 14:36:46 * satellit_ older anaconda on f20 though 14:38:00 it sounds like the IG is pretty straightforward; what about scheduling a day to review the sysadmin guide and get a task list going? 14:38:10 (probably after jhradilek applies patches? ) 14:39:08 satellit_: the gtk theme there seems to be a bit different though 14:39:19 looks a bit like unskinned gtk actually 14:39:33 f21 was mate install 14:40:00 ah, right 14:40:14 and f20 too i guess 14:40:16 only working rawhideon koji yesterday 14:43:03 randomuser: We wanted to publish one last Fed19 guide 14:43:20 mmm 14:43:30 I will try and do some FE19 and Fed 20 screenshots in this week or next 14:44:41 Capesteve: It is not worth the effort at this point, I would say. 14:44:59 maybe just publish what you have/ 14:45:10 The screenshots or the publishing of FED19 Sys Admin Guide? 14:45:39 anyway, I''ll go through the bugs that terminal raised 14:45:42 Capesteve: Publishing the Fedora 19 System Administrator's Guide. 14:45:47 oh 14:46:17 Let's try and release the Fedora 20 book in December. :) 14:48:17 * randomuser notes he has been building towards working on the cloud guide but needs more practice with the tools 14:49:51 #info there are open bugs to be worked on sysadmin guide, and the goal is to publish for f20 in december 14:50:08 #topic open floor 14:50:55 i think the conversation is better on the list than here, but do check the thread I started about doing something different, please 14:55:23 crickets? 14:55:31 fair enough 14:55:35 thanks for coming, all 14:55:43 .. 14:55:47 #endmeeting