15:00:55 #startmeeting manila 15:00:56 Meeting started Thu Jun 21 15:00:55 2018 UTC and is due to finish in 60 minutes. The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:00 The meeting name has been set to 'manila' 15:01:02 .o/ 15:01:08 hello 15:01:13 o/ 15:01:18 manila courtesy ping: gouthamr zhongjun xyang markstur toabctl bswartz ganso tpsilva vkmc vgreen erlon 15:01:26 hi 15:01:34 o/ 15:02:00 o/ 15:02:02 Hi all! 15:02:10 hey 15:02:18 #topic announcements 15:02:43 Yesterday gouthamr fixed the project "badges" so that manila's 15:02:57 achievements and status are properly reflected. 15:03:09 #link https://review.openstack.org/#/c/577020/ 15:03:15 Thanks gouthamr !!! 15:03:38 :) 15:03:48 Just a reminder that we are working with an eye towards 15:03:54 Was that the change you intended to link? 15:03:54 M3 on July 26. 15:03:58 Doesn't look manila specific 15:04:09 bswartz: it fixed stuff for us though 15:04:23 bswartz: yeah, everyone had lesser badges than they really did 15:04:23 our badges were getting squashed out 15:04:30 interesting 15:04:38 Thx gouthamr 15:05:05 w.r.t. M3 on July 26 we need to review and merge 15:05:10 Inspur driver 15:05:22 #link https://review.openstack.org/#/c/550454/ 15:05:34 metadta for access rules 15:05:46 #link https://review.openstack.org/#/c/570708/ 15:05:47 #link https://review.openstack.org/#/c/571366/ 15:05:56 priority for access rules 15:06:05 #link https://review.openstack.org/#/c/572283/ 15:06:12 json query validation 15:06:41 #link https://review.openstack.org/#/c/563429/ 15:06:56 Just reminding .... 15:07:07 Will there be a review etherpad this cycle? 15:07:07 Any other announcements? 15:07:46 bswartz: I will put one together since we don't have a storyboard for same yet :) 15:08:21 To help coordinate reviews (mostly to avoid too many people reviewing the same thing while nobody reviews other things) 15:08:34 Will storyboard eventually support that feature? 15:08:36 #action tbarron will create a review etherpad for m3 15:09:00 storyboard is low level tooling on which such a feature could be built 15:09:10 it allows one to do trello-like stuff 15:09:25 * bswartz knows nothing of trello... 15:09:29 and this would I think be a natural application. 15:09:52 bswartz: post-its in columns with annotations 15:09:59 bswartz: trello's like rally's kanban board, a little more flexible 15:10:20 gouthamr: much more simple as well 15:10:27 doesn't necessarily imply kanban methodology though 15:10:31 s/more simple/simpler 15:10:35 true.. 15:10:55 like we can still all work on 15 things at once :D 15:11:08 for better or worse 15:11:23 Any other announcements?? 15:11:35 * bswartz can work on 16 things at once, as long as 15 of them are not important 15:11:44 :) atleast we get to see all the 15 things in a place (channeling ameade) 15:11:46 :D 15:12:13 #topic Beijing bug smash 15:12:21 It was this week. 15:12:34 Thanks to those participating or helping do reviews. 15:12:51 And special thanks to zhongjun__ for coordinating manila aspects. 15:12:52 Thanks all 15:13:03 ++ thanks zhongjun__ 15:13:06 #link https://etherpad.openstack.org/p/OpenSource-Hackathon-Rocky-Beijing-Bugs-List 15:13:23 #link https://etherpad.openstack.org/p/OpenSource-Hackathon-8-beijing 15:13:39 Some bugs are fixed, some are in review, some are still in backlog. 15:13:50 But good progress, thanks again! 15:14:02 In line 162, We don't have separate statistics on manila projects, we only count bug number of storage. 15:14:50 zhongjun__: understood 15:15:18 I was late gettiing bugs into the list for this bug smash but overall I think good progress was made. 15:15:31 Anything else on this topic? 15:16:10 #topic manila meeting time (bswartz) 15:16:17 o_O 15:16:21 Oh yes, I remember this 15:16:25 Ben brought this one up after the meeting last week. 15:16:50 Ben? 15:16:57 Want me to cover it? 15:17:18 You were pretty articulate at the time, let's assume you will be again :D 15:17:31 so yes please 15:18:06 I realized during the meeting last week that we chose the time for this weekly meeting many years ago, when we had a number of core team members in Europe and the east coast of the US, and none in the west coast or pacific region 15:18:34 I think that over time the center of gravity of the team has moved, and it's worth considering a different meeting time 15:19:11 In particular, something more friendly to the pacific region -- so probably 4-5 hours later than currently scheduled 15:19:44 This would cause pain for anyone joining from the EMEA region 15:20:21 But other than toabctl, I don't know who that includes 15:21:00 Thoughts? 15:21:24 zhongjun__: would you prefer this meeting to be 4-5 hours later? 15:21:44 I'm sure that gouthamr/markstur would 15:21:53 toabctl: is on paternity leave which implies that he will soon be awake at odd hours anyways :D 15:21:58 4-5 hours later, It will be at 4:00 15:22:16 4:00 morning 15:22:24 erm 15:22:26 Really? 15:22:32 That's not good 15:22:46 this time is fine for me 15:22:47 Now It's 23:22 in my zone 15:22:51 How much later would it need to be for it to be morning time for you zhongjun__? 15:23:11 So it would need to be 9 hours later? 15:23:32 That would create problems for those of us on the east coast 15:23:33 beijing is 12hr ahead of EST 15:23:47 It's fine, 10 hours later would be more better 15:24:20 Okay I hadn't done the math last week 15:24:27 haha 15:24:50 That would mean that in order to make the situation better in China, those of us on the east coast would have to join in the evening after dinner 15:24:56 tbarron: what do you think? 15:25:27 I'm willing to do it but fear that we'll lose attendance from the current group. 15:25:35 \ 15:26:02 I'm joining from EMEA. 4-5 hours later will be around midnight. 15:26:06 to be fair you could at least try alternating times or something. Unfortunately inconsistent meeting times can also hurt attendance 15:26:06 how about 2 meetings or async meetings? I've heard there are other projects doing that 15:26:32 ganso: we've avoided that in the past -- it means you never have a quorum for important discussions 15:26:46 And it's twice as much work for the meeting chair 15:26:49 (I don't have reception here so I'll probably disappear in a minute or two...) 15:27:04 amito: noted 15:27:53 some meetings (like TC) have gone away altogether in favor of async IRC and "office hours" 15:28:06 So based on the realities of the timezones, I don't know if we can do better than the current time 15:28:16 but I don't know that that would really work for us either. 15:28:29 I don't have a specific proposal, but I wanted to shine light on the fact that the team's center of gravity has moved 15:28:52 I'm not hearing a consensus for a change but bswartz has certainly raised an important issue. 15:29:13 We also don't know who *would* be attending if we had the meeting at another time. 15:29:45 Let's everyone think about this and don't be afraid to make suggestions. 15:29:48 it seems we can't agree to a better meeting time 15:30:00 ganso: at least not today 15:30:10 I has been hoping that moving the meeting a few hours would help china, but I didn't realize how far we would have to move it to make it work 15:30:17 I think so, We almost have a half-day time difference 15:30:52 If we moved it 9 or 10 hours, then it would cause problems for east coast people, including brazil 15:31:10 bswartz: yup 15:32:14 Personally I'm not sure how often I could attend a 9pm or 10pm meeting 15:32:16 well let's table this topic for now; if you get an idea pertaining to $subject then let's talk about it again 15:32:41 #topic Open Discussion 15:32:53 Do we have other things to talk about today? 15:33:41 We could discuss the world cup... 15:33:51 :) 15:33:52 lol 15:34:19 OK, let's go do work or watch TV or whatever, see you all next week! 15:34:24 Thanks for working on manila! 15:34:29 #endmeeting