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