14:11:32 #startmeeting publiccloud-wg 14:11:33 Meeting started Wed Mar 1 14:11:32 2017 UTC and is due to finish in 60 minutes. The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:11:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:11:37 The meeting name has been set to 'publiccloud_wg' 14:12:41 We start! Please fill in your name at the participants area for this meeting at the etherpad! 14:13:05 ....and you are all very welcome! =) 14:13:46 #topic Reveiw last weeks agenda items (APs) 14:14:15 We have 2 APs here - first one is on me 14:14:32 Tobias and others to setup an individual repo for the publiccloud-wg 14:14:51 i think i said i was going to help out with that 14:14:58 and then promptly did nothing about it whatsoever 14:15:06 I guess you did! =) 14:15:09 so er, apologies for at least not pinging you an email 14:15:26 Don't know it you saw the discussion in the maling list yesterday? 14:15:31 ah, no 14:15:36 on openstack-operators? 14:15:36 No worries! 14:15:51 i was in a meeting offsite for most of yesterday and so pretty much out of the loop 14:16:15 user-committee 14:16:28 ah, i don't subscribe to that one 14:17:02 Short summary of that... 14:17:32 They question us of why we need a new one for our use cases 14:18:02 Since the openstack-user-stories exist already 14:19:07 I know we used the Product WG template for that as a base, but changed it. Not sure it is a must that they are the same for the stories exist in the same repo 14:19:37 I can agree on the good parts of having the same repo and template 14:20:57 Another reason we had for having our own repo was to have a separate review process within the teams area before "maybe" merge them into "openstack-user-stories" 14:21:51 Which I still believe is a good approach, but maybe not a must 14:22:45 So, with that said...do you get the picture of the feedback from the list vs why we wanted our own repo? 14:23:09 Or am I making a mess of it? =) 14:27:40 Before continue on that one, next AP is for zhipeng and to check deadline dates for the submission of forum topics 14:27:55 sorry tobberydberg, $work beckons - i'll be back asap :( 14:29:44 I can cover for zhipeng here and say that yesterday was the official start for the "brainstorming" about topics. Please follow the user-committee list to what is happening there, all session topics will be announced there 14:30:00 ok :-) 14:30:24 So, deadline will be around the end of the month 14:31:10 I suggest that we call out for a separate brainstorming meeting just to focus on that part. Thought about that? 14:32:05 +1 tobberydberg 14:32:20 a focussed session just for that makes sense 14:32:26 and we're short on time 14:32:38 Yes! 14:33:26 Was hoping to get a good start for that during todays meeting, but since we are so few not much of that will happen 14:33:47 Next week? 14:33:56 early next week? 14:35:46 Monday at the 1400 UTC? 14:36:37 Fine here. 14:36:54 good 14:37:58 #action tobberydberg to find time and meeting room, send out invitation to Forum Brainstorming Session 14:38:11 #topic Report from PTG in Atlanta 14:38:50 That topic was for zhipeng to cover since he was our only representative at the PTG =) 14:39:29 We had an extra meeting with the group - notes here: https://etherpad.openstack.org/p/publiccloud-atlanta-ptg 14:40:19 Nice to see that we did get some response from the Keystone team for a couple of the items in the GAP docusment 14:40:26 *document* 14:40:51 Would love to se more of that! 14:41:47 Added the comments from them to the GAP doc and added 2 columns - one where we can add related links to patches, specs etc etc 14:42:10 #topic Discuss "User story template" 14:42:24 sorry i'm late 14:42:59 I covered your topics for you ... hope I didn't lie to much =) 14:43:17 So, template discussion 14:43:37 we started that earlier in the meeting... 14:44:38 any more input on the template 14:44:45 As I said we got questions about why not using the same template...and, if it doesn't fit our needs, make suggestions of how to change if to fit us better 14:45:47 I agree on your opinion zhipeng, that a separate repo would be nice in the star up phase, with hope of merge later on 14:46:06 ...for the use cases... 14:47:15 But, I think that we should take their suggestion into consideration. 14:47:52 What's the opinions about this? 14:48:00 yes of course that was my first thought as well 14:50:15 Considering the feedback - change back to that? 14:51:56 I will have to be honest and say that I will need read up about the details of the template 14:52:09 no problem :) 14:52:51 I like their suggestion. Don't fit the need for the GAP document though, but I guess that can exist in google docs for now 14:53:45 Suggestion: continue the discussion at the user-committee mailing list (please join in)? 14:53:56 sounds good :) 14:54:28 ok, lets do that! I will look into the template a bit more as well! 14:54:52 #topic Forum sessions Boston in May 14:55:06 We got into the subject earlier... 14:55:44 Decided to have a separate session to brainstorm this... 14:55:45 scientific wg has been working on it, i think we could borrow some ideas from it 14:56:01 sounds good 14:56:14 started to read a little bit of their as well 14:56:36 #link https://etherpad.openstack.org/p/publiccloud-boston-forum-session 14:56:38 #link https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg 14:56:41 haha 14:56:44 same time 14:56:57 thats our start and you posted their =) 14:57:00 Good! =) 14:57:31 Monday 1400 UTC is my current suggestion 14:57:38 since we are short on time 14:58:14 Totally fine for all of you to get in there and start the brainstorming before that! I will! =) 14:58:39 2 minutes left... Other topics? =) 14:59:20 let's discuss more via email 14:59:43 zhipeng: Don't forget to add your name to the etherpad for this meeting 14:59:43 I had a few, bot no time for them now...but one of them was a which from my side to have a more ongoing discussion between meeting at the mailing list 14:59:47 https://etherpad.openstack.org/p/publiccloud-wg 15:00:07 seanhandley good catch ! 15:00:29 So, time is up! I'll end it here! Thanks for today guys! 15:00:35 #endmeeting