23:00:05 #startmeeting product-team 23:00:06 Meeting started Wed Mar 4 23:00:05 2015 UTC and is due to finish in 60 minutes. The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 23:00:09 The meeting name has been set to 'product_team' 23:00:15 roll call 23:00:43 Roland Chan, Aptira 23:00:54 mikec 23:01:03 Naren Narendra 23:01:06 morning rolandchan 23:01:12 hey guys 23:01:13 afternoon 23:01:32 \o/ 23:01:45 o/ 23:02:00 ello ello 23:02:16 carol, shamail? 23:02:47 imad, russellb, anyone else 23:02:56 Carol's here 23:03:27 agenda 23:03:30 #link https://wiki.openstack.org/wiki/Meetings/product-team#Agenda.2C_04_March_2015 23:03:42 first up 23:04:03 we held a f2f openstack board meeting yesterday 23:04:22 our work was much discussed 23:05:00 yay? 23:05:06 our group will be folded in as a working group under the user committee 23:05:13 everyone was very postivie 23:05:19 positive 23:05:29 what does that mean? folded under the user committee? 23:05:32 and the tc members present very supportive 23:05:41 hey barrett 23:05:50 the board wants to show support 23:06:00 without setting the direction 23:06:04 great! 23:06:05 great sign.. 23:06:15 agreed 23:06:20 are there other WG under the user committee? 23:06:29 i answered a lot of questions about what and why 23:07:17 #link https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups 23:07:49 telco, WTE, application ecosystem, api, log rationalization, etc 23:08:10 ok, so then i guess is good :) 23:08:14 these are the horizontial teams 23:08:17 Kewl. 23:08:28 mscohen: very good feedback 23:08:44 and this will give us a more visability 23:10:05 a ran a breakout group on this 23:10:36 with imad, eileen evans, robert esker, and Mark McLoughlin 23:11:15 What was the proposal from the breakout? 23:11:15 they want us to target the tokyo summit 23:11:24 to go public 23:11:32 with a multi-release roadmap 23:11:42 Excellent! 23:11:46 great! 23:11:49 ++ 23:12:01 Hi all, that's good news 23:12:04 i told the breakout group in detail about what we are working on 23:12:20 they liked it all 23:12:53 Mark McLoughlin, monty taylor, and russel brant were positive 23:12:56 in the meanwhile, the f/b that we are getting from PTLs is how to co-ordinate cross project comm and secondly, they want help to identify what customers are using and interested to use (features) in each of the project.... how do we tackle that 23:13:07 good sign for us working with the TC 23:13:53 i may lose you all in about 10-15 minutes 23:13:57 landing soon 23:14:16 so lets run through the first part of the agenda 23:14:28 then you guys can do updates when i drop off 23:14:30 I don't think we are ready for cross project comm... It is definitely a need for us to be successful. 23:14:47 Sounds good sarob 23:14:50 shamail:agree 23:15:09 #topic operators midcycle 23:15:33 id like to only present what data we have gathered 23:15:43 and make a request for the missing data 23:16:01 i dont want to jump the gun 23:16:03 Gathered from whom? PTLs? 23:16:14 barrett right 23:16:30 agree 23:16:37 we should present our plans to the TC next 23:16:45 For the data from the PTLs, I'm not convinced we should present that - I'd rather share back with PTLs first. 23:16:46 OK - I've taken the info in the etherpad and created a draft roadmap 23:16:57 provides a way for us to nudge the other PTLs to spend some time with us 23:16:58 i dont want the TC to think we doing an end run with the operators 23:17:13 we actually got feedback from most PTLs I think 23:17:20 Agree we need to share with TC - can we do that via email? 23:17:24 gathering data and socializing is working 23:17:33 lets play that out 23:17:35 We're still missing several projects 23:17:52 barrett right 23:17:54 Given we're missing Nova, Cinder, Horizon 23:18:01 FYI - i am getting from cinder hopefully by end of next week 23:18:04 as key projects 23:18:08 I took the info from the etherpad and worked with Kenny and Shamail to create a draft roadmap and sent the link to the mail list 23:18:11 *getting data 23:18:23 presenting to Operators early next week feels like an end-run to me. 23:18:31 Thierry will be at midcycle ops meetup. We can pitch to him.... 23:18:36 #action barrett, sarob present data gathered highlights, request missing data at operator midcycle 23:18:44 rockyg good idea 23:18:46 Who is attending from this team? 23:18:51 With Kilo deadline of March 5th, we should expect more responsiveness from the PTLs next week 23:18:59 true 23:18:59 I am. Or at least trying to. 23:19:15 I am...also wondering if the weather will be an issue 23:19:18 #link https://etherpad.openstack.org/p/PHL-ops-meetup 23:19:32 i am attending 23:19:39 the agenda is very full, so we may need to do the thing one on one 23:19:45 or in breakout group 23:20:04 nevertheless, its an opportunity 23:20:09 sarob agree 23:20:10 moving on 23:20:17 cause im going downnnn 23:20:30 #topic integration timeline 23:20:41 We should pitch to ttx but line up to be on agenda for a future TC meeting 23:20:41 #link https://wiki.openstack.org/wiki/ProductTeam#Timeline_for_Integration_of_the_Product_team_with_other_teams.3B_PTLs.2C_TC.2C_and_other_User_Committee_working_groups 23:20:54 shamail agreed 23:20:54 I'm sure the dialog will be interactive 23:21:21 so i started to rough out an implementation plan for this group 23:21:37 with tokyo nov2015 as our target 23:21:56 TC present before vancouver 23:22:23 then we can add in more milestones 23:22:48 sound like a plan to come up with the plan? 23:23:06 yep 23:23:11 sarob agree 23:23:12 yup 23:23:13 Need to agree on process/workflow as well 23:23:17 You have my feedback and I agree with your responses. Some of my comment are still open in doc 23:23:22 works for me. just need owners... 23:23:44 We can make plans on mailing list 23:23:48 lets keep our subteams plugging away 23:24:09 shamail: def socialize our plan of plan on the product ML 23:24:17 Lol 23:24:30 So meta 23:24:52 * sarob hearty laugh 23:25:32 if i can jump to roadmap since i will be offline soon 23:25:52 #topic roadmap process update 23:26:26 #link https://docs.google.com/document/d/13JPDDiBGGXf5dtP0u8C-1So2Mjb3yEmGhv_ijVqyEf0/edit?usp=sharing 23:26:52 i threw this together last week 23:26:57 rough start 23:27:05 Looks like a good start 23:27:08 reuses some ideas from defcore 23:27:21 Oops, I remarked too soon. My comment about the doc was related to this. 23:28:21 the basic idea is we use gerrit for technical community review each step of the process 23:28:41 we tie our milestones to the release milestones 23:28:45 DefCore needs to be acknowledged but probably out of band to our work for now. I also want to make sure we get use-cases from other groups (beyond WTE) as well 23:28:51 we only use the same tools as the PTLs 23:29:04 shamail def 23:29:05 Sarob: +1 23:29:22 * Shamail apologizes for timing being off... I'm on a phone client. 23:29:30 i want our companies to start feeding our product user stories into WTE 23:29:37 +1 23:29:46 But what about Telco, API, etc? 23:29:48 i am working this team process into vmware 23:30:02 Telco WG is good place for Telco User Stories 23:30:05 I know OPNFV is trying to enable their liason to OpenStack 23:30:08 of course 23:30:11 Telco is already gathering user stories 23:30:18 Seems like we might want to foster the start of other WGs: HPC, CSP..? 23:30:27 barrett: I agree, I just want to make sure they know we exist as well 23:30:37 i meant to say other user committee working groups will feed product team 23:30:53 user stories through patching to gerrit 23:31:03 barrett: +1 on asking others to build too 23:31:04 voting will be public 23:31:25 voting on what? 23:31:30 Would announce ML make sense or the community newsletter? 23:31:46 barrett on each step in the roadmap process 23:31:58 just like any other openstack project 23:32:26 sarob: +1 but where would they land? Cross project repo? 23:32:29 sarob: not quite seeing how that will work, but am sure it will become clear as we move forward 23:34:29 I wonder if his wifi got shut down 23:34:34 He said he was about to land 23:34:43 Think so 23:35:10 Do we need more on this topic? 23:35:36 I think we have enough for now. There's a doc to provide feedback if needed. 23:35:36 If not, we should go to the updates 23:35:39 As part of the overall plan, we need to address gathering user stories and identifying gaps 23:35:47 I agree with the concept though (let's see how it works) because working on our process, information collection, etc. needs to be done using the same methods as other projects and needs to be accessible to all. 23:35:55 And queue the topic change 23:36:08 #topic update socialize and gather data group 23:36:22 Thanks Rockyg 23:36:34 so it looks like we want to present something at the operator summit? 23:36:39 on socialization 23:36:43 Yeah. it won't turn out as a topic, but it will let readers know. 23:36:51 Yep 23:36:59 i won’t be there but anyone from the group can do it. 23:37:12 We should at least let the Ops know that we exist and what we are working on and towards 23:37:23 i agree 23:37:38 we could show what we have as WIP. 23:37:39 Also think we should ask them for use cases and give them a place and format 23:37:51 ++ on use cases 23:38:10 We should have a place they can propose them. 23:38:11 I think the plan would be to show what've we've collected so far and ask for others to respond to help us finish collection. 23:38:15 here's some slides that could be a starting point for what we'd share...https://docs.google.com/presentation/d/1396hSpQuOYM-XbLenkY1HzNCwiWsk-uN42eofpTbOUY/edit#slide=id.g637b47041_0378 23:38:31 i also made a spreadsheet of it about a week back https://docs.google.com/spreadsheets/d/1kupS0hXh9aA15dJOs2A8XHbrisvnls94F7thJekT4jk/edit#gid=0 23:38:39 Rockyg: +1 goes hand in hand w/ other topic 23:39:10 mscohen - nice! 23:39:21 Spreadsheet might be the right way to present at the moment. 23:39:32 let me update it again. i think some new data came in 23:39:34 Ops summit is show current feedback from PTLs, ask others to help, and show where use cases can be submitted? 23:39:42 It shows data collected but makes no judgements/presents no opinions yet 23:40:04 there are a few things you can show…like data for M is very thin 23:40:06 Bingo. 23:40:08 So, we need to determine how to collect use cases by Monday, then. 23:40:29 I think that's probably a stretch goal Rockyg 23:40:36 Sharing current feedback would be P0 23:40:43 shamail: agree;-) 23:40:50 Is the call to action for the Operators: Provide Use cases to shape M? 23:41:23 we could do something else simple like create a google form for operators to input use cases. Get someone to pop it up in front of everyone in one of the sessions 23:41:24 And maybe adjust priorities on L? 23:41:25 + use-cases for "verticals" to respective group (WTE, Telco, etc) 23:41:46 +1 for semi-structured data. 23:41:53 and the google form. 23:42:06 +1 on structure and form 23:42:08 I think we shouldn't ask ops for that yet Rockyg. It might be seen as going to end run again. 23:42:21 And a good example use case or two? 23:42:43 We should just ask for submissions, prioritization can't be done until we have spoke with TC. 23:42:44 k. 23:43:06 Shamail: If we ask for Use cases and their view on gaps, I think we're OK. We have this dialog periodically with Operators (like San Antonio in August) 23:43:18 My guess would be they (and PTLs) will own prioritization initially (IMHO only) 23:43:20 Well, we could report back what the ops think are fires.... 23:43:34 As part of the preso to them. 23:43:35 Agreed Barrett. I was referring to prioritization 23:43:49 True. 23:44:27 We just have to be careful to make sure people understand we are collecting feedback (including importance) but not actually taking action on that data yet 23:44:40 Shamail: Agree 23:44:48 So, socialize and gather data active at meetup. Provide info on what we are doing and gather hot topics from Ops 23:45:10 Rockyg: +1 AND CORNER TTX 23:45:15 :-) 23:45:22 Aye, aye! 23:45:25 From reading the PTL answers to "what can Product WG do to help" seems like providing feedback and helping to prioritize is what some want 23:45:53 Agreed, but we want TC to weigh in first before we help with that 23:46:48 So can we use the info from the Operators next week, along with the form that we come up with to capture it, in the conversation with the TC? 23:46:51 Just an FYI, I think TC would *love* if we could provide some data on gap analysis 23:46:53 We can help, for now, by collecting importance from ops, our companies, and customers 23:47:07 not immediately, but work with them to see what they need. 23:47:23 I would think so and agree rockyg 23:47:29 Shamail: ++ 23:48:07 By the way, NarenNarendra mentioned cinder by end of week 23:48:15 Enough on S&G? Next up wourd be roadmap process update 23:48:24 Do we have a volunteer to draft the feedback form? 23:48:26 Any updates on other missing ones? Can anyone from the team help? 23:48:50 I'm still working on Ironic - hopefully soon. 23:48:50 if naren has trouble with cinder, i can def help there 23:49:01 Sorry again, phone is delayed :( 23:49:02 If we don't get the form before, those of us at the meetup can throw something together there.... 23:49:14 What about Nova input? 23:49:35 nova is a big gap. Steve had said he’d do that it looks like 23:50:02 That's Mikal Still, John Garbutt, Joe Gordon. We'll need to clear what we get from last two with Mikal 23:50:10 Also for Infra and Release cycle, I don't think Stefano asked the "what are your current priorities" questions. If no one else has done so I'll follow up with him. 23:50:36 We shouls put some milestone around collection so we know when to start asking for help. 23:50:41 Should* 23:51:52 I'm sorry everyone. I have to drop off as well. I have to start driving. 23:52:08 #topic update product roadmap process 23:52:16 Do we have anything on that? 23:52:28 Good luck at the ops summit!!! I will see you next time. 23:52:33 We've got spreadsheet: 23:53:07 We've got spreadsheet:#link https://docs.google.com/spreadsheets/d/1kupS0hXh9aA15dJOs2A8XHbrisvnls94F7thJekT4jk/edit#gid=0 23:53:29 sarob put up a doc earlier for comment. 23:53:35 and first draft preso: 23:53:46 #link https://docs.google.com/presentation/d/1396hSpQuOYM-XbLenkY1HzNCwiWsk-uN42eofpTbOUY/edit#slide=id.g637b47041_0141 23:54:43 and the process doc from sarob: 23:55:04 #link https://docs.google.com/document/d/13JPDDiBGGXf5dtP0u8C-1So2Mjb3yEmGhv_ijVqyEf0/ 23:55:40 So, got that rolandchan.... 23:56:22 If we just want to note those docs, that could be enough for the update and we could move to open discussion for 4 minutes 23:56:36 Sounds good 23:56:37 #topic open discussion 23:57:16 Anything? 23:57:47 I think it would be valuable to create a timeline for deliverables to guide our actions 23:57:58 don't see that in the doc that sarob started 23:58:30 There's a small timeline on the wiki page. 23:58:54 I think we have a plan to flesh out the plan. 23:59:06 rolandchan: ++ 23:59:33 Do you think we should try to setup a F2F session on some of this to move it forward? 00:00:07 got to run to my next meeting... 00:00:14 Let's put that on the next agenda? That will also include reports from the Ops meetup 00:00:31 And, it's a wrap. I might not be able to end this. Lemme try. 00:00:34 #endmeeting