14:03:04 #startmeeting docteam 14:03:04 Meeting started Wed May 7 14:03:04 2014 UTC and is due to finish in 60 minutes. The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:03:07 The meeting name has been set to 'docteam' 14:03:11 Okay, agenda is here: 14:03:17 https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting 14:03:26 First topic, as usual 14:03:31 #topic Action items from last meeting 14:04:01 pout. No one did this that I recall 14:04:01 everyone look at the requirements listing in http://justwriteclick.com/2014/04/10/tearing-down-obstacles-to-openstack-documentation-contributions/ and give feedback on the openstack-docs mailing list 14:04:40 and then I don't recall what this one was? annegentle to send post about doc tools requirements to openstack-docs mailing list 14:05:01 annegentle: oops :/ 14:05:26 annegentle: is there a thread on the ML for your blog post? 14:05:45 Sam-I-Am: I guess not? 14:05:53 I'm looking and I don't see one... bummah 14:05:59 doh 14:06:03 I've got a draft ready to send so I'll do that 14:06:15 ahh right. I never sent it. 14:06:17 Ok 14:06:20 sorry! 14:06:24 my bad 14:07:03 ok that's it for action items 14:07:13 since one didn't get done the other didn't either, naturally. 14:07:28 Okay this is the final week before the Summit 14:07:32 #topic Summit prep 14:07:57 Sam-I-Am has been doing a ton of work getting ready for the install guide session, thanks Matt! 14:08:14 nickchase and I are working on who talks about what in each of the cross project sessions 14:08:22 yeah... the audit was fun 14:08:37 trying to come up with more items for my session too 14:08:45 which hopefully others will be chiming in :) 14:08:51 remember, i'm the summit n00b 14:09:00 Yes for sure 14:09:09 Sam-I-Am: there's a 101 Session that you'll want to go to 14:09:36 annegentle: the dev summit 101? 14:09:56 #link http://junodesignsummit.sched.org/event/e04c26e2a5df3a5089b2ed701d2aac3b#.U2o-r61dU0w 14:10:07 Yep, that's the one ^^ we do it each summit and role play how sessions go 14:10:20 annegentle: ahh thats already on my calendar :) 14:10:29 Our Documentation track is grouped here 14:10:30 #link http://junodesignsummit.sched.org/overview/type/documentation#.U2o-x61dU0w 14:10:47 And the two cross-project sessions are 14:11:01 #link http://junodesignsummit.sched.org/event/626a1e21babaf30d98973f5eb7402fcf 14:11:09 #link http://junodesignsummit.sched.org/event/19381e6ad48e05abc9099eb7ff956231 14:11:27 i found it interesting how the summits have different scheduling sites... so... lots of schedule conflicts to fix 14:11:27 Any questions about the summit? 14:11:33 yeah it's tough 14:11:36 I fought against it and lost 14:12:30 So nickchase, I think that the first session is about requirements gathering 14:12:45 right, well, I suppose it'd have to be 14:12:49 nickchase: and I'm sending an email today to get people to start thinking about it, across openstack-dev and openstack mailing list 14:12:54 great 14:12:59 you will probably want to make sure that ... 14:13:34 you explain that the two sessions are together. I think that people may expect a certain amount of requirements gathering in the second session, from the description. 14:14:05 nickchase: ok 14:14:14 nickchase: I see the split as user doc vs. devs writing doc 14:15:01 annegentle: To a certain extent. But the devs need to have their say on what they need to make this process smoother for them. 14:15:47 nickchase: what are your goals and expected outcomes? I see seeds of a process. Are you outlining an etherpad with the blueprint -spec expectations ahead of time? 14:15:52 nickchase: absolutely 14:16:39 annegentle: Never having done this before, I didn't think about that, thank you. :) I will do that. My goals and expected outcomes are... 14:17:19 annegentle: that we get the devs to talk about their own processes and the circumstances under which they feel like they would contribute more regularly, and then we would ... 14:17:41 annegentle: either during the session or afterwards, depending on how it goes, figure out how to make that work for them. 14:17:48 annegentle: Or am I being unrealistic? 14:18:05 nickchase: I don't think that's unrealistic 14:18:12 nickchase: use https://etherpad.openstack.org/p/restructure-docs-session as a template 14:18:19 nickchase: and list your goals 14:18:41 nickchase: with questions you want answered 14:18:45 annegentle: Thanks, appreciate it. 14:20:05 annegentle - Thanks for the Summit 101 link! Just reposted for our team. 14:20:33 nickchase: I also think that the dev base is smaller than we really think. 14:21:00 annegentle: that could very well be. I suppose we'll find out! 14:21:03 nickchase: not to hash out your session now, but check out slide 33 of http://www.slideshare.net/littleidea/openstack-an-authentic-critique 14:21:25 one other question, how can we sit together at lunch Monday? 14:21:31 that'll let us continue discussing 14:21:37 to lead into the next one 14:22:39 I don't know a lot about lunch arrangements but typically it's at the convo center so I'll see what I can do 14:22:41 ok 14:22:50 #topic developer.openstack.org 14:23:00 We've got the domain registered and now we're working on copying the content to it 14:23:20 the content will be the same as api.openstack.org, which is just the landing page and all the pages related to http://api.openstack.org/api-ref.html 14:23:39 we may change that from a Cloud Sites set of pages to a Cloud Files static site 14:23:47 Just wanted to bring it to everyone's attention. 14:24:03 The content will be geared towards app devs consuming OpenStack resources 14:24:17 cool 14:24:46 SDKs, etc 14:25:14 We may move the user guide CLI over there, not sure yet. That's what I want to talk about in the session about requirements 14:25:29 #topic Doc contribution survey - results coming 14:25:47 We got less than 40 responses to the survey, but I think they offer insights 14:26:35 It was interesting, filling in the "other" portion to barriers was the most answered barrier 14:26:55 then it was Docbook, followed by not knowing where a bit of info goes, followed by Git/Gerrit 14:27:17 Even grouping the "other" question a pattern emerged that people just don't think they know enough to contribute 14:27:39 then when you look at who answered the survey, I see that the majority who answered contribute or use OpenStack less than 10 hours a week 14:27:59 so I'm not sure we got quite what we need from the survey, and it'll be important to test out the data at the Summit 14:28:04 nickchase: does that help you some too? ^^ 14:28:14 yes 14:28:19 My sense is that we need to shift towards asking more consumers to write docs than devs, but that is just a guess 14:28:32 perhaps two people who responded work on OpenStack full time 14:28:53 also people don't have a test bed to test things on 14:29:05 I'll send a mailing list post right after this meeting 14:29:10 annegentle: the problem here is that it's the devs we really need to hear from. I mean, they're the ones who are writing what in many cases turns out to be incomprehensible messages about what it is that we then need to document. 14:29:12 any questions? 14:29:29 nickchase: but that's where -specs is helping, have you been reviewing those? 14:29:44 nickchase: to me it's a matter of getting all the projects to follow nova/neutron's lead? 14:30:03 annegentle: not sure what you're referring to, there's been a LOT of stuff flowing past me 14:30:23 nickchase: ok, I mentioned it in an email I sent. the nova-specs backlog is over 100 blueprints to be reviewed 14:30:35 is/has 14:30:57 I'll wait to see if anyone has Qs... 14:31:25 #topic Doc tools news 14:31:26 annegentle: yes, I've been lookign at that 14:31:57 Ok all I've got here is that we can now use SCP rather than plain-ol' FTP to copy the HTML and PDF to the docs sites 14:32:17 And 0.13 of the openstack-doc-tools tool is the latest version 14:32:40 nickchase: sorry didn't mean to move too fast. So your sense is that that's useful for docs or not useful? 14:33:16 annegentle: don't let me hold you up. Useful, but not sufficient. 14:33:39 nickchase: yep it doesn't have the user / operator empathy that a docs person brings to the table 14:33:54 annegentle: right. 14:34:16 #topic Installation guide notes 14:34:29 I wanted to bring this up because Sam-I-Am did a ton of work auditing the install guides 14:34:54 #link https://etherpad.openstack.org/p/installation-guide-audit 14:35:00 so that's a great etherpad for the session 14:35:03 please add/change stuff 14:35:18 Sam-I-Am: all I'd say is add the template at the top that lists the session name, presenter, which room, etc. 14:35:41 ok... will need to find that template 14:36:09 Sam-I-Am: use the top of https://etherpad.openstack.org/p/restructure-docs-session 14:36:36 #topic Doc Sprint in Brisbane to coincide with Pycon AU 14:36:53 That's August 4-5, see http://2014.pycon-au.org/ 14:37:01 Super cool they're doing that 14:37:24 Ok lots of time for open discussion 14:37:26 #topic Open discussion 14:37:48 not much here... looking forward to the summit and seeing everyone 14:37:58 should be a tiring blast! 14:38:18 sam-i-am: that should sum it up. :) 14:38:33 tiring blast is exactly right! 14:38:41 I had a great time at Write the Docs in Portland 14:38:52 annegentle: cool 14:38:56 did you write some docs? 14:39:26 One person live blogged all the main talks, it was amazing 14:39:28 #link http://andrewspittle.com/tag/write-the-docs/ 14:39:30 that guy did! 14:39:40 In my six hours delayed plane situation I sure wrote some docs. 14:39:45 annegentle: were we supposed to meet today to talk about something? 14:39:57 maybe it was my session? 14:40:05 or the review guide... 14:40:06 Sam-I-Am: maybe the process session? 14:40:10 Sam-I-Am: yes 14:40:13 review guide 14:40:41 Sam-I-Am: and nickchase both, I want to encourage you to post to the mailing list this week, so we ensure we get people at the sessions beyond just "us" 14:41:02 post about the sessions? 14:41:31 to openstack-dev, you mean? 14:41:58 actually, I need to do at least one summit-related blog post as well 14:42:01 nickchase: for yours, yes. and openstack-docs too there are devs there interested in docs and of course we want them to attend 14:42:16 and I'm not ready to write about my main talk 14:42:22 Sam-I-Am: yes a brief description of the goals for the session 14:42:22 general openstack list? 14:42:43 Sam-I-Am: for yours, I would think openstack-doc would suffice, but you could certainly use the openstack list too 14:42:48 and a link to the etherpad, I assume? 14:43:12 nickchase: yep 14:43:24 At Write the Docs, two community presentations stood out to me. 14:43:25 #link http://andrewspittle.com/2014/05/05/write-the-docs-ali-spivak-communities-are-awesome/ 14:43:40 #link http://andrewspittle.com/2014/05/06/write-the-docs-drew-jaynes-putting-the-docs-cart-before-the-standards-horse/ 14:43:57 Wordpress actually has multiple doc teams for multiple audiences/toolchains 14:44:10 Codex is separate from the docs for developers of Wordpress 14:44:20 interesting 14:44:21 that was a nice confirmation 14:44:57 Definitely read the twitter stream 14:44:58 https://twitter.com/search?src=typd&q=%23writethedocs 14:45:06 one major theme was "treat docs like code" 14:45:08 so we're right on, man 14:45:58 The videos will be available and I highly recommend them. I watched all of last year's. 14:46:09 anything else? Want back 14 minutes of your day? 14:46:47 have it! 14:46:49 #endmeeting