17:00:39 #startmeeting murano 17:00:40 Meeting started Tue Jun 23 17:00:39 2015 UTC and is due to finish in 60 minutes. The chair is sergmelikyan. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:43 The meeting name has been set to 'murano' 17:00:46 o/ 17:00:51 Hi! 17:01:05 Hi folks :) 17:01:22 \0 17:01:47 Hi! 17:01:51 all 17:03:03 heya! 17:03:17 #topic Action Items Review 17:03:34 #1 kztsv_mbp: enable trusts by default, notify everyon via ML about this decision and rationale behind it. 17:03:57 done 17:04:11 yeah, so but had no chance to read it yet :) 17:04:46 #topic Choosing Cross Project Liaisons 17:05:21 Folks, let's choose cwho is going to be responsible for what, and be contact point for other teams 17:05:30 https://wiki.openstack.org/wiki/CrossProjectLiaisons 17:05:49 #1 Oslo 17:06:32 I've started editing this page and added myself, but then decided that we need choose from our members 17:06:46 Anyone would like to step-up for that? 17:07:52 sergmelikyan: looks like we don't have volunteers :( 17:08:07 Yeah... then let's leave it as is... 17:08:24 #2 Release Management 17:08:30 sergmelikyan: I'd like to take some of those, I think =) 17:08:38 I will be happy to continue doing this by myself :) 17:08:44 sorry I'm not a fast typer today =) 17:08:47 #3 QA 17:10:11 So tempting =) 17:10:12 :) 17:10:41 freerunner: what is stopping you? I would prefer someone who is core in the project but you are with-us for a long time already :) 17:10:42 let's put it like this. I want to take #documentation and can probably take #stable branch 17:10:53 sergmelikyan: freerunner he is not eligible 17:11:04 The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project. 17:11:21 kztsv_mbp: yeah... I forgot that we have this rule :( 17:11:46 ok mooving on... 17:11:49 kztsv_mbp: but murano-core is too small isn't it? 17:12:14 Nikolay_St: good point - we have 4-5 members currently 17:12:19 I mean too small to drop core on every liaison 17:12:23 today is not the best meeting to choose those. We do not have slagun and katyafervent and filip 17:12:52 right. Also, there is no rush: we didn't have much cross-project activities recently 17:12:56 kztsv_mbp: we can start and on the next meeting ask if they would like to take something that is assigned to someone with more than 1 17:13:12 assignment 17:13:27 #3 QA - me for now, moving on 17:13:38 #4 Documentation 17:13:46 kztsv_mbp: do you take that? :) 17:14:23 yep, I'm wiling to take that 17:14:45 Nikolay_St: I hope our team will be much bigger given recent contributions :) 17:14:47 and stable/branch looks just like what I was doing with backporting anyway 17:14:49 kztsv_mbp: done 17:15:02 #5 Stable Branch 17:15:07 kztsv_mbp: ? 17:16:04 sergmelikyan: like I said — "looks just like what I was doing with backporting anyway" 17:16:25 kztsv_mbp: I am just confirming :) 17:16:31 done 17:16:37 #6 Vulnerability management 17:17:06 I will take that by myself 17:17:16 #7 API Working Group 17:17:28 for that liaison may not be core :) 17:17:37 sergmelikyan: I can take this 17:17:44 Nikolay_St: done :) 17:17:58 I will update wiki appropriately after the meeting :) 17:18:03 sergmelikyan: and also Log Working Group as far as I have some experience with this guys 17:18:21 Nikolay_St: thank you! 17:18:28 but I'm not sure if they are still 'alive' 17:18:56 Nikolay_St: I not sure either 17:19:19 sergmelikyan: I'll go to tomorrow meeting and take a look 17:19:36 Nikolay_St: you are already in that table for Sahara :) 17:20:11 #topic Open Discussion 17:20:12 sergmelikyan: yeap, I see :D 17:20:26 sure 17:20:30 Folks, we don't have other topics in our agenda, so speak up if you have something to discuss 17:20:46 Hi, I have added a new blueprint 17:20:56 https://blueprints.launchpad.net/murano/+spec/add-support-for-heat-environments-and-files 17:21:20 guys, I submit a spec last week. Now it's mostly done. Please take a look here: https://review.openstack.org/#/c/192250/ 17:21:48 mgershen: your blueprint looks good, except I would go with shorter description :) 17:22:09 mgershen: we also use specs for defining specifications for the features 17:22:42 mgershen: we definitely need more features in our heat-based packages! 17:22:55 +1 for this BP to be approved for Liberty 17:22:55 true, It still needs fixes and some things needs to move to a spec, the idea is adding support for heat environments and additional files. 17:23:12 any objections? 17:23:59 mgershen: most of the review will happen in spec, BP is a way to track work in release scope, but it also not bad to have comprehending description 17:24:03 about my BP, should we discuss it next week or should i send an email to the mailing list? 17:24:41 mgershen: mailing list looks good 17:25:04 +1 for having this in L. Details may be discussed in spec, but overall I am with you on this 17:25:23 mgershen: and also we can discuss it next week if some questions will appear 17:25:49 OK to all :) 17:28:08 Then approved :) Let's wait for the spec :) 17:34:04 Any other topics to discuss? 17:34:51 sergmelikyan: nothing from my side 17:35:30 let's give it few more minutes and finish todays meeting :) 17:36:05 btw, we have new spec for TOSCA support https://review.openstack.org/194422 17:36:09 from Vahid 17:37:50 yep it's going to be my bedtime reading I guess. Since we need to review it ) 17:38:04 kztsv_mbp: as well as spec fron Nikolay_St 17:38:18 though I've seen comments from you already :) 17:38:28 #endmeeting