13:30:44 #startmeeting docwebteam 13:30:45 Meeting started Tue Feb 12 13:30:44 2013 UTC. The chair is fifieldt. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:30:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:30:48 The meeting name has been set to 'docwebteam' 13:30:53 ok 13:31:05 so the previous meeting was on 2013-01-08 13:31:15 we had 4 action items 13:31:26 #1: annegentle-web to share the proposal for the book sprint 13:31:45 I believe Anne did this and asked for feedback on the outline on etherpad 13:31:48 can someone confirm? 13:32:06 #info http://wiki.openstack.org/Meetings/DocTeamMeeting 13:32:21 #topic action items 13:33:23 In my mind, I didn't see it. I'm checking my mail. 13:33:31 thanks Daisy 13:33:44 hello 13:33:52 hi EmilienM 13:34:03 I don't find such mail in my mail box. 13:34:12 OK, so maybe she hasn't done it yet 13:34:15 that's fine 13:34:28 Yeah. Maybe she is too busy. 13:34:37 so I would propose that she, or some delegate explain the principle of the doc sprint and ask for feedback onto the etherpad ? 13:34:46 #link http://etherpad.openstack.org/EssexOperationsGuide 13:35:10 does that sound reasonable?> 13:35:29 I'm fine with it. 13:35:56 #action AnneGentle or delegate to explain the principle of the doc sprint and ask for feedback onto the etherpad prior to the doc sprint (i.e. this week ASAP) 13:36:11 OK, the next action item 13:36:14 #2: annegentle-web to investigate wiki migration status 13:36:22 I believe that I saw an email about this from Anne 13:36:53 [Openstack] Progress on wiki migration to Mediawiki on 19/1 13:36:58 so I believe this action item is done 13:37:08 the next action item 13:37:10 #3: Daisy write up what the role of a lead translator would be? And what permissions they'd need where? 13:37:17 Daisy, I saw the email from you today 13:37:30 so I'd consider that you did this quite well and are just waiting on feedback ? 13:37:37 Oh. My mail doesn't cover this topic. 13:37:57 I can write another mail this week to include this information. 13:38:23 that would be excellent, I think 13:38:51 perhaps tied in with your existing proposal somehow? :) you're the expert .... 13:38:53 #action Daisy write up what the role of a lead translator would be? And what permissions they'd need where? 13:39:17 #action all to provide feedback on Daisy's proposal for translation access control 13:39:34 I'm on vacation this week, Tom, for Chinese New years holiday. 13:39:35 The final action point we have listed is: 13:39:39 of course! 13:39:48 please, enjoy your holiday! 13:39:53 So I will do it next week week. 13:40:03 this seems entirely reasonable :) 13:40:10 恭喜发财 13:40:23 #4 EmilienM to reply to comments & fix bugs if they exist. 13:40:42 EmilienM, are you happy with the bug progress compared to last meeting? 13:41:07 fifieldt: yes :) 13:41:08 is anything bothering you (apart from our overwhelming lack of people) ? :) 13:42:01 ok, cool - let's consider this one ongoing work, rather than a specific action item 13:42:28 ladquin, just pinging you in case you're around for the doc meeting and need anything :) 13:42:48 I am. Hey there, folks 13:43:05 Hi ladquin! 13:43:11 but no needs so far, thanks! 13:43:39 All, after our action items the next on the agenda is : Wiki migration, Grizzly priorities, Do we need an #openstack-doc IRC channel?, Doc tools update, Open discussion 13:43:45 does anyone have anything to add to that agenda? 13:44:53 no, I don't have. 13:45:19 thanks Daisy -- EmilienM, writerDiane ? 13:47:31 ok, assuming not 13:47:45 I don't want to touch wiki migration without AnneGentle 13:48:01 but perhaps we can do an easy one like "Do we need an #openstack-doc IRC channel?" 13:48:16 do people want to attempt to answer that? 13:48:24 #topic Do we need an #openstack-doc IRC channel? 13:49:39 yes ! 13:50:02 cool 13:50:03 I'm glad to have one, although I cannot answer why. 13:50:13 indeed 13:50:20 I'm interested in justifications too 13:50:54 here's a potential one: for coordination between the documentation team, to promote interactive discussions, rather than having them via email 13:50:59 I guess, some doc team members should be there any time, in order to answer questions from developers and users. 13:51:08 that's also good 13:51:20 I think it'd be worth it. Lurking in -dev I see many of the questions are about docs, so even if we're few people at first, it would get crowded soon, I guess 13:51:42 indeed, so many questions about docs ladquin 13:51:44 great explaination, ladquin ! 13:52:13 fifieldt: +1 13:52:18 I agree - separate openstack-docs would be good 13:52:28 ok, it seems we're in agreeance 13:52:35 great ! 13:52:38 #action all to start using #openstack-docs 13:53:07 #action AnneGentle to formalise #openstack-docs, including justification for separate channel and any other necessary work to register the channel 13:53:07 we shall broadcast it to the community. 13:53:27 #action AnneGentle to email the community once the channel is setup 13:53:27 :) 13:53:39 Assigning action items to people who aren't here is evil .. but fun 13:53:49 hehe 13:54:10 good work, Tom. 13:54:16 So left on the agenda we have: Wiki migration, Grizzly priorities, Doc tools update, Open discussion 13:55:01 So left on the agenda we have: Wiki migration, Grizzly priorities, Doc tools update, Open discussion 13:55:09 I'm not sure on the wiki migration status, but perhaps we could look at Grizzly priorities 13:55:16 #topic Grizzly Priorities 13:55:17 I agree. 13:55:40 #link https://launchpad.net/openstack-manuals/+milestone/grizzly 13:55:49 #link https://launchpad.net/openstack-api-site/+milestone/grizzly 13:56:19 first, ladquin, do you have a feeling on how things are going for grizzly API-wise? 13:56:24 it seems like you're doing quite well 13:58:03 fifieldt, I think we might be ok for grizzly, but it seems tome that there are some unreported work thats not there too 13:58:10 ah, right 13:58:20 annegentle may give us a better idea 13:58:37 are you going to be looking for missing things, or do you need us to remind people to use DocImpact again for API changes? 14:00:02 While Laura is looking, here are the stats for the manuals project right now: 19 New, 47 Confirmed, 1 Triaged, 2 In Progress, 15 Fix Released 14:00:08 it's a lot of work 14:00:15 with pretty much everything marked as "Medium" 14:00:21 fifieldt, oh no they use it a lot! :P but perhaps I'm going through too much detail 14:00:32 no worries :) 14:00:45 OK - so just let just know if you need anything 14:01:01 looking at the grizzly milesone bug lists for both projects, is there anything that jumps out as more important or less important for people? 14:01:27 fifieldt, what I'm really missing right now is samples, I've filed some bugs, but I can try to generate them myself (under supervision) 14:01:37 ah, right 14:01:43 do you need a test environment ladquin? 14:03:40 personally, I think Quantum and Cinder docs right now are lacking. I also really want to see Cells as a first-class citizen of the documents 14:03:58 any other ideas? 14:04:30 I do have one, I just couldn't dedicate a lot of time to testing the apis, as it was not a priority (maybe now) 14:04:48 no dramas :) 14:05:05 my personal aim: get the grizzly version of everything out to the release as close as possible 14:05:23 ok, since noone has any ideas right now, I propose we take this discussion back to the mailing list 14:05:35 #action all to discuss grizzly priorities on the mailing list (and work on them!) 14:06:11 Since we don't have the people here to talk about wiki migration or doc tools, this only leaves open discussion 14:06:15 #topic open discussion 14:06:42 over to you, EmilienM, lorin1, ladquin, Daisy for your thoughts on anything and everything :) 14:08:53 Don't really have anything to add here... 14:09:10 Oh, I should mention the Cells docs 14:09:14 ya? 14:09:29 I have a WIP branch, I'm waiting for Chris Behrens to give me the OK that's accurate. 14:09:45 I pinged him a couple of days ago on this, he said all of the pending code landed, he needs to look over the docs again. 14:09:53 Sometimes Chris is slow 14:10:02 if you need help, we're running Cells in production 14:10:04 Is there someone else we could ping re cells? 14:10:13 so I might be able to look over it with colleagues 14:10:15 fifeldt: Can you look over the WIP branch? 14:10:19 sure 14:10:30 OK, I'm going to set it to a regular merge proposal. 14:10:42 #action fifieldt to look over Cells WIP branch or ask his colleagues to fix it 14:10:59 Also, I'd like to eventually morph that into a chapter on "Partitioning your OpenStack cloud" and provide an overview of regions, zones, cells, availability zones, and host aggregates. 14:11:06 sounds sorely needed 14:11:08 :) 14:12:09 OK, if noone else has anything to say ... we can close the meeting? 14:12:19 ok 14:12:28 good for me. 14:12:54 EmilienM ? 14:13:35 Excellent. Thanks all for attending the meeting. I'll try to followup with Anne about the meeting time and hope to see all of you on the mailing list until next meeting :) 14:13:48 #action fifieldt to followup with AnneGentle about the meeting time 14:13:51 #endmeeting