15:00:01 #startmeeting climate 15:00:01 Meeting started Fri Feb 7 15:00:01 2014 UTC and is due to finish in 60 minutes. The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:05 The meeting name has been set to 'climate' 15:00:10 o/ 15:00:16 hello folks 15:00:25 who's here? 15:00:47 casanch1, bauzas, swann, f_rossigneux, SergeyLukjanov, pafuent? 15:00:55 hi 15:01:08 hello :) 15:01:27 Nick has some troubles with irc client 15:01:38 but I dunno where are others :) 15:02:01 let's wait then 15:02:48 o/ 15:02:54 :) 15:03:20 we should wait bauzas anyway.. 15:03:33 pafuent is joining 15:03:38 ok, great 15:05:32 hmm :) 15:05:44 Hi 15:05:48 hello 15:05:56 bauzas, you here? 15:06:16 it seems like his meeting lasts longer than he thought 15:06:56 Yeap 15:07:02 ok, I'll post today's agenda anyway 15:07:07 https://wiki.openstack.org/wiki/Meetings/Climate#Next_meetings 15:07:28 let's wait 3 more mins and then start discussion 15:10:24 okay, I'll start, let's see if other guys will join 15:10:29 #topic Action items from the last meeting + reviews queries 15:10:37 #link http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-02-04-15.02.html 15:10:51 last time we had not many action items, really :) 15:11:04 as for me, I've released 0.1 Climate 15:11:19 and I'm proud I did it with u, folks 15:11:47 while releasing several problems were found and I'll cover them later this meeting 15:12:12 also I've created several BPs for 0.2 release 15:12:23 due to #link https://etherpad.openstack.org/p/climate-0.2 15:12:38 still, we may add some more functionality to 0.2 15:12:44 if it'll be needed to 15:13:06 pafuent, casanch1 I want you to take a look on this page 15:13:23 and if you want to add something there - please, feel free 15:13:36 We look at them yesterday 15:13:49 ok, so you're ok with that proposals? 15:14:00 we think we can work on notification 15:14:17 And devstack thing, of course 15:14:33 ok, I saw you've started mailing thread with Joel 15:14:46 I dunno if it was some other letters 15:14:53 did you agreed on meeting time? 15:15:23 to discuss notification BP? 15:15:34 ok, we may discuss them on next topics 15:15:41 #topic Current 0.1.1 status 15:15:51 #link https://launchpad.net/climate/+milestone/0.1.1 15:15:55 We already have it. Joel will send an email with the result of the metting 15:16:05 pafuent, ok, great, thanks 15:16:23 we have already good progress for 0.1.1 release 15:16:44 cause we thought it would have bug fixes and several BPs u see there 15:17:04 I want to define at least draft date for 0.1.1 15:17:18 https://bugs.launchpad.net/bugs/1276638 This one was merged 15:17:21 Launchpad bug 1276638 in climate "Climate client can't handle correctly no-JSON responses" [Medium,Triaged] 15:17:35 pafuent, yep 15:17:40 that's nice :) 15:17:53 lp didn't notice that 15:18:57 it seems like I have to do that manually 15:19:26 #action DinaBelova Fix https://bugs.launchpad.net/bugs/1276638 state 15:19:30 Launchpad bug 1276638 in climate "Climate client can't handle correctly no-JSON responses" [Medium,Triaged] 15:19:47 If 0.1.1 scope will look almost the same 15:19:49 as it's now 15:20:21 I think we may have 0.1.1 somewhen about first week of March or even earlier 15:20:38 anyway, we'll look on further progress 15:20:57 #topic Future plans for 0.2 (https://etherpad.openstack.org/p/climate-0.2) + special attention on notifications BP 15:21:18 as for 0.2, we have almost defined scope now for it 15:21:44 https://blueprints.launchpad.net/climate/0.2.x 15:21:48 #link https://blueprints.launchpad.net/climate/0.2.x 15:22:19 Pablo and Cristian - you'll be working on devstack + notifications? 15:22:55 yes! 15:22:55 Yeap 15:23:07 o/ 15:23:21 bauzas, o/ 15:23:29 casanch1, pafuent great 15:23:39 sorry, was previously in another meeting 15:23:58 casanch1, pafuent I'll wait results of your discussion with Joel 15:24:03 bauzas, never mind 15:24:21 about notifications 15:24:24 bauzas, please take a look on meeting minutes later 15:24:29 bauzas, yes 15:24:33 I did 15:24:44 so, there is a clear consensus with jd__ 15:25:09 notifications have to ben sent to Ceilometer and then must be raised to customers there 15:25:15 s/ben/be 15:25:20 bauzas, yep, sure - but also we have two Intel teams that have real use case for that 15:25:28 DinaBelova: yup, we know 15:25:37 yes, Joel will also send the use cases 15:25:44 and Joel, Pablo and Cristian has discussed that internally 15:25:46 that needs to be discussed on how to do this the right way 15:25:58 bauzas: exactly 15:26:00 so we'll have use cases and then discuss :) 15:26:10 did you already have some discussions about it? 15:26:23 my personal opinion is that we have to leverage Ceilometer capabilities 15:26:36 that were some technical thought, yes 15:26:52 but in case of an operator wanting to deploy Climate only, we could consider some minimal actions 15:27:17 smth like climate -> notification to queue -> ceilometer -> real notification to user 15:27:25 bauzas, am I right? 15:27:27 DinaBelova: +1 15:27:34 that was idea 15:27:53 we have also discussed that the notifications could also trigger some workflows 15:28:04 I believe it's still good one - but we'll review it one more time anyway 15:28:05 additionally to the client notifications 15:28:21 casanch1, yep, I noticed idea about Mistral + Murano 15:28:26 Joel has written that 15:28:30 on BP 15:28:35 ok 15:28:37 https://blueprints.launchpad.net/climate/+spec/notifications 15:29:15 anyway, for Climate it will mostly look like sending notification to queue 15:29:20 would it makes sense to define a meeting for it ? 15:29:30 s/makes/make 15:29:33 the question is who and how will process that 15:29:45 bauzas, I suppose we'll take a look on use cases firstly 15:29:51 and then decide if needed 15:30:03 jd__ was committed on that 15:30:11 bauzas, sure 15:30:33 cyeoh: got a min? 15:30:44 we'll share use cases to all interested people. casanch1, pafuent - will it be ok for you? 15:30:51 +1 15:31:08 +1 15:31:10 +1 15:31:13 ok, nice 15:31:22 let's move on to the next topic then 15:31:32 #topic New name for Climate ('climate' repos already exist on PyPi and rtfd) (https://etherpad.openstack.org/p/climate-new-name) - ideas? 15:31:43 and we still have problems :) 15:31:51 as I said on last meeting 15:32:04 'climate' name is already used almost everywhere 15:32:12 PyPi, readthedocts, ... 15:32:25 I'm not talking about trademarks 15:32:28 so-o-o 15:32:43 if we're thinking about next release and about possible incubation 15:32:46 so, I think we should vote for the renaming 15:32:50 we NEED new name 15:33:05 bauzas, first of all we need candidates :) 15:33:07 Why Climate was choose? 15:33:14 In the first place 15:33:16 hi all 15:33:18 sorry 15:33:21 DinaBelova: we first need to vote if Climate name needs to be changed :) 15:33:22 Nikolay_St, o/ 15:33:35 and if agreed, we need to vote on the process : 15:33:36 :) 15:33:58 Change the name: +1 15:34:10 +1 15:34:24 I'm just saying we should *officially* vote ;) 15:34:27 DinaBelova: ;) 15:34:43 so that it would appear in the minutes ;) 15:34:50 #startvote Change Climate project name? yes, no 15:34:51 Begin voting on: Change Climate project name? Valid vote options are yes, no. 15:34:52 Vote using '#vote OPTION'. Only your last vote counts. 15:34:56 #vote yes 15:34:58 #vote yes 15:35:02 #vote yes 15:35:07 #vote yes 15:35:13 sorry, I was fighting with voting syntax :) 15:35:25 Nikolay_St? 15:35:38 SergeyLukjanov? 15:35:50 #vote yes 15:36:00 just cnange, no options? 15:36:15 SergeyLukjanov: we need to define a process 15:36:17 tobok = ToBook (with one less o) 15:36:19 with timelines 15:36:28 Nick has problems with irc 15:36:32 but he's ok 15:36:34 so 15:36:35 #endvote 15:36:37 Voted on "Change Climate project name?" Results are 15:36:38 yes (5): bauzas, casanch1, DinaBelova, SergeyLukjanov, pafuent 15:36:45 it depends on your plans on sending incubation request 15:37:05 SergeyLukjanov, now we have voted we need that 15:37:33 Now I want to propose the following question: we have to define list of new names next week 15:38:06 and we need these names to be free on PyPi, readthedocs and trademarks 15:38:23 could I suggest two weeks for the proposal ? 15:38:32 bauzas, ok, good idea 15:39:10 and in case of nothing proposed in a 2 week delay, another week for finding at least one other name 15:39:41 you ok ? 15:39:46 Yes 15:39:49 2 weeks + 1 week extra delay 15:40:00 +1 15:40:04 and if none found in 3 weeks, that's duty of PTL for choosing 15:40:04 #startvote Define list of new possible names in 2 weeks starting from Feb 10 (1 extra week if no new names will be proposed)? yes, no 15:40:05 Begin voting on: Define list of new possible names in 2 weeks starting from Feb 10 (1 extra week if no new names will be proposed)? Valid vote options are yes, no. 15:40:06 Vote using '#vote OPTION'. Only your last vote counts. 15:40:14 bauzas, ok :) 15:40:21 #vote yes 15:40:23 #vote yes 15:40:35 #vote yes 15:40:51 #vote yes 15:41:07 SergeyLukjanov, are you ok with that? 15:41:38 I suppose he is :) 15:41:43 close the vote 15:41:45 #vote yes 15:41:46 I'll close voting 15:41:47 #endvote 15:41:48 Voted on "Define list of new possible names in 2 weeks starting from Feb 10 (1 extra week if no new names will be proposed)?" Results are 15:41:49 yes (5): bauzas, casanch1, DinaBelova, SergeyLukjanov, pafuent 15:41:58 SergeyLukjanov, u're quick :) 15:42:01 okay 15:42:09 ok, one last point about PTL responsibility for choosing the name if none proposed in 3 wks 15:42:18 PTL is DinaBelova 15:42:29 ok, I'll set voting for it too :) 15:43:24 #startvote Is PTL responsible for choosing name if no variant will be chosen during first 3 weeks? yes, no 15:43:25 Begin voting on: Is PTL responsible for choosing name if no variant will be chosen during first 3 weeks? Valid vote options are yes, no. 15:43:26 Vote using '#vote OPTION'. Only your last vote counts. 15:43:31 #vote yes 15:43:34 #vote yes 15:43:38 #vote yes 15:43:41 #vote yes 15:43:43 #vote yes 15:43:50 #endvote 15:43:51 Voted on "Is PTL responsible for choosing name if no variant will be chosen during first 3 weeks?" Results are 15:43:52 yes (5): bauzas, casanch1, DinaBelova, SergeyLukjanov, pafuent 15:43:58 ok, great 15:43:59 one last point, about how we elect the names if proposed ? 15:44:03 CIVS ? 15:44:14 bauzas, I'm ok with that 15:44:14 which electors ? 15:44:22 open contributions ? 15:44:32 I would really love having open voting :) 15:44:45 as my team is really concerned about the name change :) 15:44:48 bauzas - all contributors who were taking part in climate/its client/climate-nova 15:44:54 personally I prefer open voting 15:44:57 mmm 15:44:59 okay 15:45:01 that's good idea 15:45:05 we can vote on it 15:45:16 only contributors or open 15:45:17 I mean open to see vote marks 15:45:29 but I'm not sure how should be in electorate 15:45:34 SergeyLukjanov, mm, sorry? 15:45:49 personally 15:45:58 for savanna I'm set the following process - only ATCs votes for the new name 15:46:00 I think that only contributors may take part here 15:46:07 SergeyLukjanov, +1 15:46:09 with two round elections 15:46:24 ATCs? 15:46:24 first round - filter out ~5 name options 15:46:26 I think that's not cool :( 15:46:28 and discuss them 15:46:48 the second round - voting to choose exactly the new name 15:46:49 CIVS? 15:46:54 Sergey: only ATCs for the project or ATCs 15:46:59 ATC = Active Tech Contrib 15:47:05 pafuent, ATC == active tech contributor 15:47:14 Thanks 15:47:15 ATCs for the project 15:47:18 CIVS = Condorcet voting systems 15:47:42 pafuent, CIVS is used in OS, for example, to choose PTLs 15:47:52 Ahh 15:47:52 ok 15:47:59 so variants are 15:47:59 I think you should have all ATCs :) 15:48:19 1/ electorate == all ATCs 15:48:26 2/ ATCs for climate related repos 15:48:31 3/ anyone at all 15:48:41 I believe 1/ is good enough 15:48:49 SergeyLukjanov, your thoughts? 15:49:07 ddutta, so you are more likely to support 1/ too :) 15:49:12 :) 15:49:15 yes 1) 15:49:21 ok for the options, we can go to the vote 15:49:32 enyone to propose the name and collect all folks votes and project's ATCs to vote for the new name 15:49:39 anyone* 15:49:57 that's a 4th option 15:50:05 SergeyLukjanov, sorry, can't get your idea with "name and collect all folks votes and project's ATCs to vote for the new name" 15:50:10 4/ anyone who proposes or is ATC 15:50:11 may you explain? 15:50:19 oh, ok 15:50:31 ok, then we can go to the vote 15:50:57 quite an hard vote to express :D 15:51:03 yeeep 15:51:25 give only figures, not names as choices, and explain the choices 15:51:33 so we could vote either 1, 2, 3 or 4 15:52:03 if you want another name for a lease project it could be charter 15:52:24 ddutta: we are having an etherpad :) 15:52:28 #startvote Who will be electorate? ATCs, climate_ATCs, everyone, ATCs_and_name_declarants 15:52:30 Begin voting on: Who will be electorate? Valid vote options are ATCs, climate_ATCs, everyone, ATCs_and_name_declarants. 15:52:31 Vote using '#vote OPTION'. Only your last vote counts. 15:52:37 #vote ATCs_and_name_declarants 15:52:43 #vote ATCs_and_name_declarants 15:52:50 #vote ATCs_and_name_declarants 15:53:13 I did it :D I created vote! yay :) 15:53:35 #vote ATCs_and_name_declarants 15:53:47 SergeyLukjanov, ddutta? 15:53:51 DinaBelova: well done ;) :D 15:54:24 where is the etherpad 15:54:27 sorry .... 15:54:37 in topic name 15:54:44 but we have no variants now... 15:54:54 SergeyLukjanov? Vote? 15:55:04 #vote ATCs_and_name_declarants 15:55:11 we need to be quick 15:55:21 ok, I'm closinf vote 15:55:23 #endvote 15:55:23 we're close to the end of the meeting :) 15:55:24 Voted on "Who will be electorate?" Results are 15:55:25 ATCs_and_name_declarants (5): bauzas, casanch1, DinaBelova, SergeyLukjanov, pafuent 15:55:27 yep 15:55:31 cool thanks people 15:55:47 we have some more important topic 15:55:51 one last point, about the number of rounds, I like SergeyLukjanov's proposal 15:55:59 yep, me too 15:56:06 I may use #agreed here 15:56:10 not to waiste time 15:56:11 DinaBelova: ether pad link? 15:56:12 ok with ti 15:56:21 ddutta: https://etherpad.openstack.org/p/climate-new-name 15:56:51 #agreed use 2 cycle name changing (leave 5 names after 1st round, 2nd - define name) 15:56:51 ok, agree for a 2nd round vote 15:56:56 ok 15:57:00 last topic ? 15:57:08 a big one 15:57:09 #topic Summit talks 15:57:12 yep 15:57:14 3 mins to discuss it 15:57:17 I only want to meantion 15:57:19 way too short 15:57:31 oh, go ahead 15:57:31 that we'll have mostly like 2 topics there 15:57:47 about Climate itself and it's further steps 15:57:59 a 3rd one needs to be envisaged 15:58:05 and more oriented on physical reservations/thechnical staff 15:58:18 that was 1 :) and 2) 15:58:31 I'll create google drive doc 15:58:34 and share it 15:58:35 DinaBelova: +1 15:58:40 to create proposals 15:58:46 and send them next week 15:58:57 #topic Open discussion 15:59:01 we need to send them by Feb 14 15:59:07 i have nothng to discuss :) 15:59:10 yep 15:59:22 nothing special, I'm nearly done with the first patchset for Pecan :) 15:59:28 I'll promote it 15:59:29 good :) 15:59:31 bye! 15:59:34 bye ! 15:59:37 bye 15:59:38 bye! 15:59:40 #endmeeting