03:00:58 #startmeeting DocTeamMeeting 03:00:58 Meeting started Tue Dec 17 03:00:58 2013 UTC and is due to finish in 60 minutes. The chair is Loquacities. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:01:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:01:02 The meeting name has been set to 'docteammeeting' 03:01:22 agenda is here: 03:01:26 #link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting 03:01:51 #topic Action items from the last meeting 03:02:12 chandankumar to update https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation with note about WIP 03:02:31 chandankumar isn't up yet, by the looks, so we can probably move right on 03:02:59 welcome NickChase 03:02:59 #topic Monthly Google Hangout starting Jan 2014 03:03:31 anne has agreed to start running these monthly, now 03:03:34 starting in jan 03:03:37 any comments on that? 03:03:48 sounds like a great idea 03:04:10 yeah, everyone seems very positive about it :) 03:04:17 it's continuing in line with our previous one, pretty much, isn;t it? 03:04:25 which was pretty cool 03:04:34 yep, pretty much 03:04:39 cool, it's a good idea :) 03:04:41 also, the office hours are officially dead now 03:04:44 sorry, forgot to switch 03:04:56 #topic Operations Guide developmental edit 03:05:08 i'm going to c&p some stuff from anne from the last meeting on this topic ... 03:05:15 ta 03:05:27 14:06:07 As most of you probably know, the Ops Guide is being edited by O'Reilly 03:05:28 14:06:34 We have our first set of comments, mostly high level, and next week we'll have annotaed PDFs of the first couple of chapters 03:05:28 14:06:43 I can't spell annotated apparently 03:05:28 14:07:14 then, by mid-January, we'll have edits of the entire book, and at the end of January we're doing a mini sprint in Boston with the original authors 03:05:28 14:07:46 nice 03:05:30 14:07:49 I think Brian, the O'Reilly editor, can meet us those days since they're nearby 03:05:50 14:08:48 Some of the tasks: expand the preface to situate the Ops Guide in relation to the other guides, an intro chapter about OpenStack showing a high-level overview and emphasizing how components work together 03:06:06 14:10:43 Another interesting comment we're working through is that the book contains tactics but not a lot of strategy 03:06:06 14:10:53 My favorite is that it is quite "clean" heh 03:06:06 14:11:12 So we'll answer questions like, how does the cloud controller make your job easier? what do you need to be concerned about? 03:06:10 i think that covers the highlights 03:06:14 hi all 03:06:17 any comments on that? 03:06:19 hey nermina 03:06:30 hi nermina 03:06:49 Loquacities, 03:07:03 just a question about timing for new info going in. Have a contributor. 03:07:03 Loquacities, insert misgivings about annotated PDFs here 03:07:09 ;) 03:07:33 sgordon: they're just for the review AIUI, what's the concern? 03:07:51 slong: i'm fairly certain we can't get any real new content into it at this stage 03:07:57 but i'm happy to chase that up with anne 03:08:06 can you drop me an email? 03:08:06 Ok, will wait until after the January sprint perhaps. 03:08:09 do we know what kind of content? 03:08:10 Loquacities, having already been through the process of actioning such a review of one of the guides in the past i feel for whoever ends up doing the work 03:08:24 slong: i think that would be wise 03:08:32 sgordon: ah, fair enough 03:08:36 concern noted, in that case ;) 03:08:41 fifieldt, rhel architecture, since it's pretty ubuntu-centric. 03:08:56 oh 03:08:59 right 03:09:37 Just would like to get it in before the next release. 03:09:43 slong: it's needed, for sure 03:09:47 do we know operators who have many months of experience running a production openstack cloud on rhel? 03:09:54 fifieldt, is that a joke? 03:09:55 yes 03:09:58 lol 03:10:10 that was what the mailing list thread was about, we were asked to identify someone 03:10:16 The contributor is one such, Graeme Gillies (if I spelled it right). 03:10:36 He's volunteered to take a look. 03:10:39 nice 03:10:42 doesn't look like a cloud operator to me ... ? 03:10:53 fifieldt, how do you figure 03:11:04 linkedin ? 03:11:12 he operates our internal openstack cloud 03:11:25 a lab cloud, then 03:11:39 fifieldt, it's not a lab cloud 03:11:43 it's production 03:12:06 cool, well maybe writing up a description of that for the examples in the tail end of the book would be a good start 03:12:11 but it's not like he's the only one, either 03:12:23 Just have to start somewhere. 03:12:33 of course 03:12:40 just want to avoid "vendor" labels 03:12:40 let's chat to anne about late additions 03:12:49 Definitely. 03:12:55 ok, moving on 03:12:56 fifieldt, given the way the book was set up that is a tad rich ;) 03:13:12 #topic Doc core can now set a patch to WIP 03:13:24 I'd be interested in knowing more sgordon, but let's do that in pm channel :) 03:13:34 14:13:03 This is just a public service reminder as a new part of our review process 03:13:34 14:14:03 Anyone up for updating the wiki with the new ability to set a patch as WIP? 03:13:35 14:14:19 I think it goes in https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation 03:13:49 i think the open question here is, when do we want to use this facility 03:14:04 so it doesn't look as though that's been updated yet 03:14:14 sgordon: i confess, i'm not across this issue 03:14:18 gerrit will automatically abandon a patch that has been minused and not touched for two weeks 03:14:28 but we need to determine what makes a patch something we want to push to WIP 03:14:37 I have an example of a -core using WIP: 03:14:39 https://review.openstack.org/#/c/61898/ 03:14:48 see this terrible patch and the change to WIP not done by mde 03:14:49 me* 03:15:14 hrm, ok 03:15:16 seems sane 03:16:32 no other comments on that? 03:16:43 well, sort of... 03:16:47 go ahead 03:17:29 There's nothing at all about WIP in the HowTo. Should be added for the normal user as well,or? 03:17:40 i noticed that the associated launchpad bug will change to 'in progress' but only after i submit something for review. would this set some sort of similar flag there? 03:17:43 yeah, good point slong 03:18:07 the bug changes in response to the Partial-Bug flag in the commit message 03:18:26 slong: it's probably worth mentioning that core is able to do this 03:18:46 Yes, both,would say. 03:18:53 yep 03:18:59 Didn't know to use WIP until fifieldt clued me in. 03:19:08 are you volunteering to update that, slong? ;) 03:19:09 yeah, would be good to put something in 03:19:10 On largish commits... 03:19:17 encouraging people to put stuff "up early" 03:20:24 Sure, but might have to wait a bit. 03:20:27 you can submit your own changes as WIP 03:20:40 slong: thanks 03:20:59 #action slong to update the HowTo to include WIP info 03:21:42 #topic Doc tools update - openstack-doc-tools repository 03:21:45 * slong can never tell when sgordon is pulling a funny 03:22:00 14:15:54 Andreas has been working steadily at the new repo setup 03:22:00 14:16:10 Here's a link to the review queue 03:22:00 14:16:12 #link https://review.openstack.org/#/q/status:open+project:openstack/openstack-doc-tools,n,z 03:22:00 14:17:11 He's also working through the right way to get consistent gate checks on all the docs repos 03:22:01 14:17:43 This move also helps with building translated documents 03:22:08 there was no further comment in last week's meeting 03:22:13 any comment from this side of the globe? 03:22:54 i'll take that as a no 03:22:58 #topic Doc Bug Day Dec 20 03:23:07 that's this friday, folks 03:23:11 yay :) 03:23:22 can I ask someone in .au to send a reminder when they wake up 03:23:26 to start the day 03:23:40 4am work for you? 03:23:47 00 utc to 00 utc? 03:23:58 i should plan to be up 24 hours... 03:24:17 lol, nice early start there slong :D 03:24:17 fifieldt: i can try and make sure i put something in the irc chan in our tz, if you like 03:24:28 I'm thinking also the mailing list 03:24:33 just replying to the post I have there 03:24:35 oh, that's a good idea too 03:24:53 it might also be a good idea to make some noise the day before, as well 03:24:57 just so people don't forget 03:25:16 ok, that's all i have on the agenda 03:25:21 #topic Open discussion 03:25:32 so whats the game plan for these sprints? 03:25:47 for the doc bug day? 03:25:49 yeah 03:25:53 just do as many bugs as you can :) 03:26:07 any priorities? heat? age? 03:26:12 docs! 03:26:21 ;) 03:26:39 :D 03:26:51 what about reviewing? leave that until later? 03:26:55 just get in an do what you can 03:27:00 and* 03:27:17 good question 03:27:21 what do you think fifieldt? 03:27:48 also wondering about working on the same thing someone else is working on 03:27:57 I think I'll switch between both reviewing and writing 03:28:05 make sure you assign yourself straight away 03:28:09 don't start writing until you do 03:28:10 fifieldt: yeah, i had vague plans of the same thing 03:28:23 and yes, change the bug owner to yourself before you start 03:28:39 sure. i've had them stolen before... 03:28:44 and triage before the day if you get a chance 03:28:45 and make sure you hit refresh on the bug before you take it, too 03:29:11 also found cases of similar bugs being worked on by multiple people at the same time 03:29:26 yep, it happens 03:29:44 Loquacities: is there any way to set 'in progress' in launchpad before the first submission for review? 03:29:58 yes, you can just change the status of the bug 03:30:03 i dont think i can triage anything in lp 03:30:06 yes, all users have this feature 03:30:12 but assigning it to yourself is the best way to indicate that you're working on it 03:30:47 ok, i see now :) 03:30:52 awesome 03:30:55 any other business? 03:31:54 oh, before i close the meeting, i wanted to reiterate anne's comment about the docs meeting ... 03:32:12 no one is expected to attend a docs meeting that is outside of their timezone 03:32:35 two a month is plenty, so hopefully this mechanism of alternating each week will work for that 03:33:00 i'm just online all the time 03:33:06 this is way outside of my time zone, but more convenient 03:33:11 nermina: sleep is for the weak ;) 03:33:14 :D nermina, you work slug 03:33:21 Sam-I-Am: whatever tz works for you is fine :) 03:33:27 it's overrated 03:33:42 ok, that's it folks ... 03:33:47 #endmeeting