09:00:20 #startmeeting karbor 09:00:21 Meeting started Tue Aug 30 09:00:20 2016 UTC and is due to finish in 60 minutes. The chair is saggi. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:24 The meeting name has been set to 'karbor' 09:00:29 Hi everyone 09:00:32 hello 09:00:43 hey 09:00:47 hello 09:01:37 Are we waiting for anyone? 09:01:41 hi 09:01:48 I haven't seen yinwei in meetings for a while 09:02:52 OK 09:03:05 #topic Delete 'crontab' time format for time trigger, and support RFC2445 (zengchen) 09:03:21 zengchen is not here. 09:03:29 pinged him in channel 09:03:56 sorry i am late 09:04:35 What about $topic? 09:05:03 delete crontab time format and support rfc2445 only. 09:05:15 why remove the existing one. Why not have both? 09:05:55 zengchen ? 09:05:58 from the point of user, he don't care use which format to describe the time. 09:06:32 and from the point of horizon, it use only one time format. 09:06:34 hi 09:06:45 zengchen: can I say crontabl is part of RFC2445? 09:07:34 zhonghua-lee:RFC2445 is enough, and more appropriate than crontab. 09:08:23 zengchen: so, could you please simplly explain the difference "crontab" and RFC 2445, I think some guys confuse this 09:08:54 zhuanghua-lee:ok 09:09:22 zengchen: thanks 09:10:03 delete crontab. I think it is ok. 09:10:08 IMO, crontab can be used in simple use cases, and can not describe more complex time than rfc2445. 09:10:48 xiangxinyong456: What about UI for this ?\ 09:11:02 if crontab is deleted,I guess we need to do some work in horizon 09:12:16 xiangxinyong456:whatever use rfc2445 or crontab or others, horizon should choose one from them. 09:12:47 yeah we have already use crontab. 09:13:10 why not keep the crontab? 09:13:14 xiangxinyong456:if so, we would better choose an appropriate one. 09:13:19 xiangxinyong456: can UI support both of them? 09:13:54 zhonghua-lee: it is not neccerray 09:13:55 It's just a metter of having a format combo box 09:14:10 IMO we should keep support for crontab for now. Later we can decide to change the UI for iCal and maybe remove crontab 09:14:22 chenzeng think crontab format is port of rfc2245 time format. 09:14:50 part 09:14:58 but the user does not care whether we use crontab or rfc 09:15:13 xiangxinyong456: They have different features 09:15:23 yeah 09:15:46 xiangxinyong456: if users do not care, why to change the UI? 09:15:48 chenying__:I don't know whether crontab is part of rfc, I think if we want to support more complex time format, it better to use rfc. 09:15:51 So they need different UIs for the different limitations\features 09:16:04 but we should users evevy day,every week, like this 09:16:25 the ui is the same 09:16:36 zengchen: We are not arguing with that. But since we have the option to specify time format we can have both for now. We just need to make sure we have a proper UI for both. 09:16:56 but we need to do some transform between ui and time format 09:17:18 the ui is same 09:17:36 saggi:but i think we don't need to add a box for user to choose time format, they don't care. 09:17:53 zengchen: +1 09:17:58 zengchen: I understand 09:18:24 OK, than just make sure the UI moves to the new format as well. 09:18:58 yeah 09:19:14 saggi:at present, zhangshuai has submitted a patch to support rfc2445, so the last work is about UI. 09:19:28 great 09:20:12 https://review.openstack.org/#/c/359711 09:20:13 saggi:so we change to rfc some time later? 09:20:25 IMO we should keep support for crontab for now. Later we can decide to change the UI for iCal and maybe remove crontab 09:20:33 zengchen: When the UI changes 09:20:33 i agree yuval 09:20:56 saggi & xiangxinyong456:ok 09:21:04 +1 09:21:32 if the rfc is stable, we could move into it in the ui 09:21:41 OK, than we have both for now and try and migrate the default to be rfc2245 09:22:00 no problem 09:22:03 saggi:great. 09:22:14 #topic Rename window September 2nd (yuvalbr) 09:22:49 Well, infra team has designated September 2nd for the rename window 09:22:57 it means a downtime for gerrit 09:23:14 after that, smaug repositories will be renamed to karbor 09:23:23 We need to be ready with patches to commit so that after the switch we can immediately fix all the paths and make sure everything still works. 09:23:33 good news 09:24:07 the rename window happens on Friday 09:25:10 also, all our communications move to #openstack-karbor 09:25:42 ok 09:25:47 ok 09:26:53 that's it 09:26:55 yuval:all patches should be merged before that. 09:27:06 zengchen: which patches? 09:27:37 not merge now 09:27:53 zengchen: what? 09:29:36 yuval:for example, the patches are reviewing now should be merged before that time. 09:30:18 zengchen: the rename shouldn't affect patches pending review 09:30:35 They will move to the new repo 09:30:40 yuval:ok 09:31:00 That whole point of the downtime is to migrate all of the information 09:31:49 saggi:so we should spend more time to review patches, right? 09:32:09 zengchen: You should always do that :) 09:32:26 saggi:ok, understand. 09:32:28 zengchen: anything specific? 09:32:59 yuval:i have several patches pending review, so i have a little worry. 09:33:59 zengchen: I see most of them had a new version in the latest day. are they stable now? 09:35:15 yuval: most of them is stable, i am trying to submit a patch about updating scheduled operation. 09:35:38 zengchen: if something is not stable, mark with workflow -1, so we'll know to wait with the review 09:36:02 yuval:understand, i will do it. thank you. 09:37:28 OK 09:37:35 #topic open discussion 09:37:39 Anything else? 09:39:20 Just be ready to be on call on Friday in case something goes wrong and the infra guys needs us 09:40:12 hi,i''m a new guy and want to be a contributor,can anyone give some tips on it? 09:40:27 Leon_Wang: Sure 09:40:33 Leon_Wang: welcome! :) 09:40:36 saggi:thanks 09:40:38 What area do you want to contribute to 09:40:44 Leon_Wang:welcome. 09:40:50 welcome leon 09:40:57 welcome 09:41:01 saggi:karbor,of course:) 09:41:23 everyone thank 09:42:34 Leon_Wang:maybe you can see the wiki first. if you have any problem. you can ask in our chanel. 09:42:46 now i'm learning to know something about code review 09:43:00 zengchen:yeah,working on it 09:44:43 Leon_Wang:good. then you can read our codes. karbor have 3 componets, you can choose one to see. 09:45:22 is it nessary for me to get familiar with the concrete code? 09:45:49 Leon_Wang: What do you want to do? Is there any feature you need or bug you want to fix? 09:46:20 saggi:right now i think i only can do code review 09:47:14 Leon_Wang: Go for it! 09:47:19 saggi:but i want to fix bugs or even some feature later 09:47:26 Sure 09:47:46 We are all in #openstack-smaug or #openstack-karbor if you have any questions 09:47:55 Thanks everyone 09:47:58 #endmeeting