18:00:41 #startmeeting keystone 18:00:42 Meeting started Tue Jun 13 18:00:41 2017 UTC and is due to finish in 60 minutes. The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:45 The meeting name has been set to 'keystone' 18:00:48 ping ayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, notmorgan, rderose, rodrigods, samueldmq, spilla, aselius 18:00:50 o/ 18:00:58 o/ 18:00:58 o/ 18:00:59 #link https://etherpad.openstack.org/p/keystone-weekly-meeting 18:01:01 o/ 18:01:03 o/ 18:01:03 o/ 18:01:07 o/ 18:01:08 o/ 18:01:20 o/ 18:01:25 hey 18:01:31 pretty short agenda today - so we might get some time back :) 18:01:42 #topic announcements 18:01:58 #info focus should be on feature development and large changes 18:02:21 since we past pike-2, we should be focusing on finishing up large changes we want to deliver this release 18:02:29 o/ 18:02:49 if you're struggling or need help delivering something, please reach out 18:03:27 in addition to that - the number of bugs opened against keystone has been growing 18:03:37 at the start of the pike release, we were in the 90s 18:03:45 now we're up to 125 18:03:56 :( 18:04:07 dstanek: was doing a lot of great work to keep the number manageable 18:04:09 o/ 18:04:17 especially with bug day friday's 18:04:33 i want to call attention to it and see if anyone is going to be around this friday and wants to keep doing that work 18:04:55 or if we have someone who'd like to step up into the bug czar role 18:05:14 * knikolla volunteers 18:05:25 knikolla: awesome - that'd be awesome 18:05:43 i won't be here this friday but I can commit to dedicating some time on future fridays 18:05:51 cmurphy: ++ 18:05:57 o/ 18:06:09 we were pretty good about organizing those during the end of ocata going into pike 18:06:27 it would be nice to try and get back into that groove 18:07:03 I can try fixing some, starting tomorrow infact 18:07:06 i'd also love to hear ideas for ways we can make that whole experience easier 18:07:15 nishaYadav: ++ 18:07:33 I would ping regarding the doubts, on the channel :) 18:07:56 for me, I personally find it tough to organize work on fridays 18:08:02 ^ 18:08:10 i think "bug work" is a very nebulous term 18:08:14 and open to interpretation 18:08:20 but we can try to get back into it 18:08:48 i wouldn't be opposed to spending 30 minutes every friday coming up with a list of goals we want to accomplish 18:09:01 then we have something to work towards as a group 18:09:07 * lbragstad shrugs 18:09:12 lbragstad: I can help on Friday 18:09:19 hrybacki: sweet! 18:09:38 does anyone else have that same feeling when participating in bug days? 18:10:03 more organization and communication is good 18:10:17 i think so too, but any feedback is good 18:10:54 i kind of lean towards focusing efforts on a few things instead of a bunch of things 18:11:11 * hrybacki agrees 18:11:16 i'm hoping something like this might result in more breakout work too 18:11:43 if gagehugo and i split off to work on a specific bug, then cmurphy hrybacki and knikolla spin off to work on something else, etc... 18:12:37 either way - it'd be great to try out a couple of things and see how they work, then integrate it into every friday 18:12:52 ++ 18:13:15 I think that'd be a great pattern to establish and smooth out before we hit pike-3, which would be great because we'll be in bug-only mode anyway 18:13:39 ++ 18:13:46 sounds good 18:13:51 if you have ideas, ping me, i'd be happy to listen 18:14:08 knikolla: wanna sync in -keystone after the meeting about bug czar? 18:14:18 lbragstad: just to make it a bit clearer 18:14:29 confirming bugs, triaging, fixing, reviewing 18:14:33 those are all welcome, correct? 18:14:33 samueldmq: ++ 18:14:35 lbragstad: thumbs up 18:15:07 samueldmq: right - any bug work is valuable, so long as we understand what each process is and how to do it 18:15:36 if we end up with two people wanting to be bug czars, then i'd expect those two people to have pretty tight communication in the process 18:15:53 which i think is important for people consuming the bug work (e.g. opening the bugs) 18:16:01 bug czar? 18:16:22 czar of all bugs? 18:16:44 hrybacki: gagehugo yeah - it was a term that was introduced in an attempt to scale the PTL position 18:16:51 in the early days, much of that work fell on the PTL 18:16:56 and it still does 18:17:23 one of the scaling efforts was for the PTL to delegate some of that work to an individual that specialized in bugs for the project 18:17:31 * hrybacki nods 18:17:33 (triaging, reporting, cleaning up, tracking, etc.) 18:17:37 okay, thank you :) 18:17:41 :) 18:17:46 i wouldn't mind more responsibilities 18:17:46 ah 18:18:06 we can sync in -keystone after for folks who are interested 18:18:11 it's a rewarding experience 18:18:17 #topic tempest plugin is split out 18:18:19 cmurphy: o/ 18:18:27 o/ 18:18:41 one of the queens goals was to split tempest plugins into their own repo 18:18:47 and we are already on top of it 18:18:58 #link http://git.openstack.org/cgit/openstack/keystone-tempest-plugin 18:19:02 * lbragstad high-fives cmurphy 18:19:17 the project-config change just merged to make our jobs use the split out plugin 18:19:37 so in a few minutes i'll recheck https://review.openstack.org/#/c/471060/ to make sure everything is good 18:19:38 patch 471060 - keystone - Remove the local tempest plugin 18:19:54 so please propose tempest plugin changes to the new repo and please add the repo to your review watch list 18:19:58 * cmurphy done 18:20:12 cmurphy: thanks for all your work here 18:20:28 np 18:20:49 cmurphy: when that's done, i'll propose a patch to governance updating our artifacts for the change 18:21:06 #topic docs reorganization 18:21:11 samueldmq: sjain_ o/ 18:21:27 o/ 18:21:30 o/ 18:21:38 sjain_: want to explain the ideas? 18:21:59 yup 18:22:12 We are planning to reorganise the keystone documentation into three parts, developer, user and operator docs. Since it directly affects the whole docs directory and is a major change, we would like to discuss the idea. 18:22:39 #link https://docs.openstack.org/developer/keystone/ 18:22:49 the change is mostly based on this doc developed by Alex from doc team, https://review.openstack.org/#/c/472275/3/specs/pike/os-manuals-migration.rst 18:22:50 patch 472275 - docs-specs - Adds spec for migrating the documentation suite to... 18:23:16 sjain_: awesome - i'm happy to see we're ahead of the curve there 18:23:45 thanks lbragstad 18:24:02 what do You think about this change? 18:24:02 sjain_: are all the project action items detailed in that spec covered by the reorg? 18:24:42 currently I have made this list for reorganisation, https://docs.google.com/document/d/1Gh1ai0p4zBbAHI660pwUFvaO7iinUDZAbNmmUmYjS70/edit?usp=sharing 18:24:49 more items need to be added 18:25:27 The spec covers some docs that need to be migrated from openstack-manuals also 18:25:29 oh - cool 18:25:44 I have covered those too in this link ^^ 18:25:53 sjain_: ok - which isn't included in your changes is it? 18:26:19 currently not 18:26:28 actually 18:26:36 sjain_ started that too 18:26:40 #link https://review.openstack.org/#/c/469515/ 18:26:41 patch 469515 - keystone - Added keystone admin guides to documentation 18:26:49 this does the migration for the admin guides 18:27:03 oh - nice 18:27:38 we might want to keep everything in the same topic so it'll be easier to review/keep track of 18:27:44 sjain_: samueldmq ++ 18:27:46 i agree 18:27:48 in total I found 4 subdirectories in openstack-manuals which need to be shifted 18:29:01 sjain_: cool 18:29:21 sjain_: i think this is really good - i couldn't agree more with the direction asettle laid out 18:29:35 lbragstad: ++ 18:29:38 anything we can do to help make that a reality, I'm on board 18:30:04 not to mention, i've always wanted to have more consistency in the docs we keep in tree 18:30:15 yes, I'll try to come up with some initial patches, lets see how it comes up 18:30:31 sjain_: sounds good - keep us posted and let us know if you need anything 18:30:42 sure, thanks :) 18:30:42 looks like there are some reviews up that i need to go look at 18:30:58 sjain_: samueldmq anything else? 18:31:01 lbragstad ++ 18:31:22 sjain_ covered everything :) 18:31:24 thanks 18:31:29 good deal 18:31:32 what about the change in docs theme? 18:31:58 sjain_: ? 18:32:05 sjain_: as in should we do it? 18:32:12 Yeah, here, https://review.openstack.org/#/c/466066/ 18:32:13 patch 466066 - keystone - Updated the keystone docs to follow the docs theme 18:32:28 I updated this theme and this is left in open discussion 18:32:41 yes whether we should do it 18:32:58 and if we do, for now what should be the table of contents 18:33:25 I guess there is a general consensus that we want it, it looks just nice :) 18:33:31 i'm all for the new theme so long as the information is still discoverable 18:33:41 for the toc think I guess people would need to go to the review and look at it, and the comments 18:33:53 lbragstad: ++ 18:33:55 i can do that this week 18:34:02 * lbragstad makes a note 18:34:19 samueldmq, ++ 18:34:45 sounds good samueldmq 18:35:08 taking a quick look through the comments, it doesn't look like any of them are hard NOs to the proposal 18:35:24 we just might need to refactor some of the documentation to fit the new layout 18:35:26 thanks lbragstad, there are some comments which haven't been resolved yet 18:36:04 yes there are toctree related comments which need to be addressed 18:36:17 lbragstad, like there are contrary views, would be great if we could have a decision over them, over the comment section or in a meetting next week 18:36:34 nishaYadav ++ 18:36:57 nishaYadav: yeah - that sounds good, let's make a point to get that on the agenda for next week so we don't forget about it 18:37:08 if we come to consensus early, we can remove it 18:37:23 lbragstad, sure, will do that. 18:37:27 cool 18:37:31 anything else docs-wise? 18:37:49 nopes that would be all :) 18:37:54 #topic open discussion 18:38:01 floor is open 18:38:25 ptg tickets are up for buying 18:38:37 I think an email went out last week 18:38:57 huh - i only have a save the date 18:39:27 #link https://www.eventbrite.com/e/project-teams-gathering-denver-2017-tickets-33219389087 18:39:28 500 tickets on sale 18:40:23 hotel blocks are in the email 18:40:35 looks like the discounted ones from the foundation are the cheapest for that hotel 18:41:33 http://lists.openstack.org/pipermail/openstack-dev/2017-June/118002.html 18:42:17 fyi - there is a channel for all ptg related topic 18:42:19 topics* 18:42:24 #openstack-ptg 18:43:21 too soon to plan an agenda for keystone? 18:43:34 knikolla: nope - we can start doing that 18:44:03 we can start collecting a bunch of topics and organize them into buckets 18:44:03 ++ 18:44:25 but i wouldn't expect to formalize a schedule until August, so we should remain flexible until then 18:44:43 i don't expect cross-project threads for PTG sessions to start popping up for a few weeks 18:45:01 and those topics are typically the ones we plan the rest of everything else around 18:45:12 (or at least that's what i did for atlanta) 18:46:14 i think we're still a little early in the planning phase, but that's ok 18:47:00 anyone have anything else? 18:47:04 * nishaYadav is wondering if she can see the details/summary of the last ptg, something similar to the summit videos for those who missed it(ptg) 18:47:33 nishaYadav: well - we didn't have any video recordings 18:47:44 nishaYadav: but i attempted to put together a summary https://www.lbragstad.com/blog/keystone-pike-ptg-summary 18:48:26 lbragstad, oh, thanks for the article, on it :D 18:48:42 nishaYadav: no problem 18:48:49 anything else? 18:49:33 cool - thanks for coming everyone! 18:49:35 #endmeeting