14:01:46 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 14:01:46 Meeting started Mon Aug 3 14:01:46 2015 UTC. The chair is zoglesby. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:46 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:01:53 #meetingname Fedora Docs 14:01:53 The meeting name has been set to 'fedora_docs' 14:02:00 #topic Roll Call 14:02:01 * Capesteve waves 14:02:03 * pbokoc 14:02:11 * smccann is here 14:02:18 * kirsti is here 14:02:20 wdashley is here 14:03:18 .hello bex 14:03:19 bexelbie: bex 'Brian (bex) Exelbierd' 14:04:04 * grundblom here!! 14:04:31 #info Participants are reminded to make liberal use of #info #link #help in order to make the minutes "more better" 14:05:15 #topic Follow up on last week's action items 14:05:50 I did not see any action items in last weeks minutes, anything I may have missed? 14:08:13 #topic New Writers 14:08:36 This is the part of the program where new writers can introduce themselves. Anyone new here? 14:08:49 Started work on the storage chapter, making good progress 14:09:32 wdashley: good to hear, do you need any help? 14:10:08 not currently, just have my head dow. But will nedd some review help later 14:10:29 roger 14:11:14 #topic Release Notes Beats 14:12:03 Beats are open and ready to be written, I sent the email to docs@ not sure if randomuser sent an email to devel@ or not 14:12:36 #action zoglesby to follow up with randomuser about 'Release Notes Beats Open' email 14:12:57 beyond that any questions or issues about beats? 14:14:13 #info The tracker page still has lots of * please remove them from your name if you are still going to write that beat 14:14:16 #link https://fedoraproject.org/wiki/Category:Documentation_beats?rd=Docs/Beats 14:14:28 #undo 14:14:28 Removing item from minutes: 14:14:42 #link https://fedoraproject.org/wiki/Docs/Beats 14:16:35 #topic Publican/Publishing 14:16:56 Are there any updates on this? I don't have anything to share. 14:18:01 Not that I'm aware of :-( 14:18:06 * jsmith sighs 14:18:19 Hoping to talk about it more at Flock 14:18:21 jsmith: welcome and also :( 14:18:23 * lnovich is here 14:18:49 jsmith: I think your frustration is shared by all 14:19:02 jsmith: I am not sure how many people are going to be a flock to talk about it 14:19:14 zoglesby: Not enough :-( 14:19:21 definately not enough 14:19:21 We will definitely be talking at flock jsmith 14:19:26 but yeah, not enough people 14:19:38 * jsmith has a "Docs Tooling Workshop" on the schedule 14:19:39 but perhaps we can better sketch out something for others to comment on 14:19:47 That's the idea 14:19:51 and randomuser (and me) are giving a related talk 14:19:56 #info plan to talk about Publishing workflow at Flock if you attend 14:20:24 there is no such thing as virtual attendance unfortunately 14:21:00 lnovich: if we can get something going we can move the talking to irc as well as irl 14:21:24 Or we can try and use a voip/video conf solution 14:21:34 exactly 14:21:35 Should we bring that up on the list? 14:22:30 got to go, another meeting 14:23:11 if it means more attendance on this matter it may be worthwhile pursuing 14:23:30 agreed 14:23:54 we should be able to figure out better timing once we have a consensus with physical attendees 14:23:58 #action zoglesby to mail the list about a virt meeting around the time of flock for publishing efforts 14:24:01 but regardless, we have to report out 14:24:19 maybe I need to try and go... 14:25:03 oh, its in two'ish weeks 14:25:14 anything else here? 14:25:18 * Corey84 late 14:25:36 sorry folks, haven't quite figured out a new work schedule yet 14:25:46 that's the one next week on rochester right? 14:25:55 re:flock 14:26:06 #chair randomuser` 14:26:06 Current chairs: randomuser` zoglesby 14:26:21 Corey84: Aug 12-15 14:26:49 when is the docs talk scheduled? 14:26:57 was hoping to make the tail end 12 -13 tho are booked here 14:27:48 #link https://flock2015.sched.org/event/b493aa6d307a466191396da39d43c46d#.Vb96XHhMObI 14:28:21 I don't see the other talk 14:28:43 https://flock2015.sched.org/event/682d4ecb7cbf5ee9ee1166dc5de56e9b#.Vb96lXhMObI 14:28:57 * randomuser` loses the race 14:29:13 also, I need to add bexelbie as a speaker there 14:29:14 https://flock2015.sched.org/event/b493aa6d307a466191396da39d43c46d 14:29:24 randomuser`: which talk? 14:29:26 * lnovich thinks the timing for this talk couldn't be at a worse time... 14:29:42 spot, https://flock2015.sched.org/event/682d4ecb7cbf5ee9ee1166dc5de56e9b#.Vb96d5N0dhEs 14:29:46 lnovich: I wish you would have mentioned that earlier -- I think the schedule is now frozen :-( 14:30:03 randomuser`: take over the meeting, boss needs me. 14:30:04 brb 14:30:08 the worst times to get anything done is the end of the day and just after lunch 14:30:18 randomuser`: please ack before I run off 14:30:22 ack 14:30:52 randomuser`: he's a co-speaker there now. 14:31:03 thanks spot ! 14:31:19 spot++ 14:31:37 randomuser I can take over 14:31:48 #chair lnovich 14:31:48 Current chairs: lnovich randomuser` zoglesby 14:31:51 sure, go ahead 14:32:08 OK any more questions/comments/thoughts about Flock? 14:32:27 spot++ ty 14:32:27 bexelbie: Karma for spot changed to 4: https://badges.fedoraproject.org/tags/cookie/any 14:32:45 bexelbie: will you be able to see about getting an IRC channel or some other communication method open? 14:32:55 lnovich, yes, I will work on that 14:33:06 lnovich, for the talk? they have always set up channels per-room 14:33:07 with those in attendance :) 14:33:21 #action bexelbie - find a way for outside attendance to the tool talk 14:33:23 they sould have those set up - but for any further discussion we can set a time for #fedora-docs 14:33:36 ok sounds like a plan 14:35:03 shall we move on? 14:35:16 #topic Release Notes 14:35:36 We still need beat writers 14:35:41 indeed 14:36:04 anyone here new that doesn't know about beat writing? 14:36:42 not sure of it myself 14:36:44 #info Beats are used to generate Release Notes 14:36:54 I hope that definition is correct 14:37:16 Each person picks a topic they are interested in - or are working on 14:37:49 You need to contact the developer and ask/beg them for the feature list and descriptions for the components they are developing 14:38:07 and then write it up on the wiki page 14:38:15 like a journalist's beat, the relnotes beats are a relatively defined scope of Fedora topics to research and write about 14:38:38 and everybody loves a good beg :-) 14:39:02 I would encourage researching topics firsthand, and not limiting yourself to the ChangeSet 14:39:13 so the virtualization beat page for example is here https://fedoraproject.org/wiki/Documentation_Virtualization_Beat 14:39:30 and as you can see smccann it is open for contribution 14:39:54 oh, we should add a beat for container technology 14:40:03 grundblom, would probably appreciate that :) 14:40:03 but how do you find out if something is changed if it isn't in the changeset? 14:40:10 I know there is a general list for beats - randomuser do you have the link handy? 14:40:21 randomuser, what, I couldnt see what you said, the font was all sorts of strange... 14:40:37 I don't, it's, um, lists.fedoraproject.org/pipermail/relnotes-content 14:40:51 what I usually do is ask the developer who is in charge of making the changes 14:41:28 If you grab their attention after test day - they know at that point what is and what is not going in 14:41:41 I will usually pick out a few packages, compare current and previous version numbers, then look at packaging changelogs, packaged notes, upstream release notes, and such 14:43:53 anything else on release notes? - smccann if you have any more questions on Wed at office hours we can discuss 14:44:43 #topic Guide Status 14:44:53 sorry, connection problems 14:45:02 no worries randomuser 14:45:24 randomuser, arguebly not everyone would do that manually could we setup a script to check those 14:45:24 you still have 2 nicks online by the way 14:45:52 Corey84, there is a script to compare versions, but there's no programatic way to produce the content 14:45:59 ah 14:46:18 lnovich, the other is my bouncer/proxy which I can't access from here 14:46:25 Ok so then maybe we write a script AND a procedure on the wiki or elsewhere that people can follow 14:46:47 fwiw this is the SOP and always has been 14:47:02 yes and true - but for noobs it is all new 14:47:03 there is probably already wiki pages about writing release notes 14:47:20 ok so I can review them and make sure they are still accutate 14:47:34 #action lnovich to review RN wiki pages 14:47:58 anything cooking in guides? 14:48:07 https://fedoraproject.org/wiki/Docs_Project_workflow_-_beat_writing 14:48:44 I think were still working on the virt-getting-started guide right? 14:49:18 yes we are grundblom - actually smccann and kirsti are 14:49:53 fwiw I'm not actively doing anything on it. I'm elbows deep in virt-deploy 14:49:58 It is getting there I think - we have identified issues that needed changing and changes are being made 14:50:30 As Kirsti is a new contributor - she will take a bit longer to get on board 14:50:30 I have missed a couple of your office hours lnovich, so I bet I have missed a few things 14:50:46 but she is getting her first task list this week 14:51:00 and has successfully pulled the git repo 14:51:21 grundblom: 9AM EST Wed 14:51:44 Anyone who wants to join can join 14:51:59 #INFO Laura's office hours are 9AM EST Wed 14:52:14 anything else with guides? 14:53:13 I am back 14:54:06 ok next topic 14:54:11 I don't have any specific things for guides, but it might be a good idea to check in on a few 14:54:20 #topic BZs 14:54:27 there are bugs http://tinyurl.com/lbrq84 14:55:04 I know this is the pot calling the kettle black, but if you see a BZ that has been fixed - please change its status 14:56:13 randomuser` want to finish up the meeting and take over? 14:56:23 That might be a good thing for an upcoming office hours session - bug knockout time 14:56:29 bug smashing! 14:56:42 I can bring the flyswatter 14:56:47 but yes we should do that 14:56:58 I can bring the #closedwontfix 14:57:11 as long as you share :) 14:57:34 #info Upcoming thursday's office hours will be a bug smashing day 14:57:48 when are your hours randomuser` 14:57:59 err.. 1300 CDT 14:58:16 ok I'll make myself available 14:58:56 cool 14:59:07 #topic Open Floor 14:59:18 one minute, complain fast! 14:59:37 lnovich you have your office hours this week? 15:00:00 #INFO Laura's office hours are 9AM EST WED 15:00:14 and randomuser` want to call this meeting? 15:00:28 yup, looks like it's time 15:00:31 #endmeeting