Tuesday, 2017-09-05

*** david-lyle has joined #openstack-tc01:20
*** gcb has joined #openstack-tc01:34
*** gcb has quit IRC04:13
*** gcb has joined #openstack-tc04:26
openstackgerritJakub Wachowski proposed openstack/governance master: New project: monasca-events-agent  https://review.openstack.org/50067605:22
*** gcb has quit IRC07:22
*** gcb has joined #openstack-tc07:22
*** jpich has joined #openstack-tc07:47
openstackgerritMerged openstack/governance master: Drop Technical Committee meetings  https://review.openstack.org/45984808:44
*** dtantsur|afk is now known as dtantsur08:46
ttxsmcginnis: agreed, you have to dive deeper, which is why I flagged them all for extra attention08:52
ttxIf anyone is around for the TC office hours, i'm here :)09:10
openstackgerritThierry Carrez proposed openstack/governance master: Update goals status for Monasca  https://review.openstack.org/49145809:22
openstackgerritThierry Carrez proposed openstack/governance master: Update goals status for Monasca  https://review.openstack.org/49145809:26
* johnthetubaguy waves at ttx09:30
ttxjohnthetubaguy: hi!09:32
*** dtantsur is now known as dtantsur|lunch10:06
*** dtantsur|lunch is now known as dtantsur11:57
ttxAll see http://lists.openstack.org/pipermail/openstack-tc/2017-September/001465.html so that I can try to build a schedule for the TC room @ PTG12:25
johnthetubaguyttx: loving the grouping, although honestly I am interested in all those topics12:34
johnthetubaguyttx: +1 for monday morning being empty12:34
ttxjohnthetubaguy: same for me (all topics)12:37
ttxLet's try to free up all Monday morning + end early on Tuesday afternoon so that we can catch up in other rooms12:37
johnthetubaguyttx: sounds like a good plan12:55
*** persia has joined #openstack-tc12:58
smcginnisttx: Sounds like a good plan to me too.13:39
*** marst has joined #openstack-tc13:50
openstackgerritThierry Carrez proposed openstack/governance master: Update team diversity tags  https://review.openstack.org/50083013:51
*** hongbin has joined #openstack-tc14:09
*** lbragstad has joined #openstack-tc15:25
*** marst has quit IRC16:05
*** marst has joined #openstack-tc16:05
*** dtantsur is now known as dtantsur|afk16:07
*** marst_ has joined #openstack-tc16:11
*** marst has quit IRC16:12
*** marst has joined #openstack-tc16:18
*** marst_ has quit IRC16:19
*** marst_ has joined #openstack-tc16:23
*** marst has quit IRC16:23
*** marst has joined #openstack-tc16:31
*** marst_ has quit IRC16:32
openstackgerritLance Bragstad proposed openstack/governance master: Add policy and completion goals for nova  https://review.openstack.org/50091816:34
openstackgerritLance Bragstad proposed openstack/governance master: Add policy and completion goals for nova  https://review.openstack.org/50091816:43
openstackgerritLance Bragstad proposed openstack/governance master: Add policy and completion goals for nova  https://review.openstack.org/50091816:44
*** jpich has quit IRC16:47
openstackgerritChandan Kumar proposed openstack/governance master: Update the process of tempest plugin split goal  https://review.openstack.org/50048916:59
*** david-lyle has quit IRC16:59
openstackgerritChandan Kumar proposed openstack/governance master: Updated the progress on tempest plugin split goal  https://review.openstack.org/50048917:00
*** david-lyle has joined #openstack-tc17:14
*** david-lyle has quit IRC17:30
*** david-lyle has joined #openstack-tc17:46
openstackgerritSean McGinnis proposed openstack/project-team-guide master: Add driverfixes branch information  https://review.openstack.org/50094117:48
*** cdent has joined #openstack-tc17:59
openstackgerritSean McGinnis proposed openstack/project-team-guide master: Add driverfixes branch information  https://review.openstack.org/50094118:15
*** dtroyer has quit IRC19:00
*** rockyg has joined #openstack-tc19:00
*** dtroyer has joined #openstack-tc19:01
*** cdent has quit IRC19:34
*** rockyg has quit IRC19:45
*** cdent has joined #openstack-tc20:28
*** marst has quit IRC20:33
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for openstack-ansible  https://review.openstack.org/50097920:46
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for openstack chef  https://review.openstack.org/50098320:57
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for openstack docs team  https://review.openstack.org/50098421:00
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for horizon team  https://review.openstack.org/50098521:14
*** rockyg has joined #openstack-tc21:15
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for i18n team  https://review.openstack.org/50098621:17
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for kolla team  https://review.openstack.org/50098721:20
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for kuryr team  https://review.openstack.org/50098821:25
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for charms team  https://review.openstack.org/50099121:30
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for openstackclient  https://review.openstack.org/50099221:34
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for oslo team.  https://review.openstack.org/50099321:35
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for debian package team  https://review.openstack.org/50099421:37
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for rpm package team  https://review.openstack.org/50099621:39
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for openstack puppet team  https://review.openstack.org/50099721:42
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for qa team  https://review.openstack.org/50099821:45
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for rally team  https://review.openstack.org/50100021:48
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for refstack team  https://review.openstack.org/50100321:52
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for the release team  https://review.openstack.org/50100421:55
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for requirements team  https://review.openstack.org/50100521:57
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for security team  https://review.openstack.org/50100722:03
*** rockyg has quit IRC22:07
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for shade team  https://review.openstack.org/50101222:08
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for solum team  https://review.openstack.org/50101522:16
dhellmannlbragstad : I wonder if you want to just roll all of those updates into 1 patch22:16
lbragstaddhellmann: i was going to do that originally, but didn't know if i was going to hit snags with some projects needing respins and what-bot22:17
dhellmannmaybe not, I don't know. seems just as easy to review though.22:17
lbragstadnot*22:17
dhellmannah22:17
lbragstaddhellmann: that's true - i apologize for the spam :(22:17
dhellmannnah, I'm not complaining22:17
dhellmannjust trying to figure out what's less work for everyone :-)22:17
lbragstaddhellmann: the burndown chart tool is pretty awesome by the way22:18
dhellmannsdague gets credit for starting that22:18
lbragstadi got that working today, so thank you for that22:18
lbragstadack - i'll be sure to thank him, too22:18
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goals for stable team  https://review.openstack.org/50101622:20
dhellmannit would be really nice to turn that into something easy to use with a config file instead of having to customize22:20
lbragstaddhellmann: yeah - that's what i was thinking22:20
lbragstadit's pretty close22:20
lbragstadthe only thing i had to really replace was the branch i was tracking my work with22:21
dhellmannI put some stuff in the releases repo recently to run gerrit queries and show the results using a yaml file to define the queries22:21
dhellmannbetween that and the dashboard thing we should have some good examples of working with queries22:21
lbragstadyeah22:21
lbragstadthat other thing that would be nice would be to feed in the projects you need to track somehow22:22
lbragstadbut i'm not sure how best to do that yet22:22
dhellmannright, that's the sort of thing I mean22:22
lbragstadi'm not sure if this is the right answer, but i could parse the goal document itself and look for "Goal not applicable." and ignore the project from the expected_repos.txt22:23
dhellmannif we can get that done, then we can use periodic jobs to publish the results22:23
dhellmannor we could use a more parseable format for the goal data and render to html22:23
dhellmannI just did rst to start because it was easy22:23
lbragstadyeah - that's true22:24
dhellmannif we're going to publish burndown charts, we could manage those separately, too22:24
lbragstadi like that idea22:24
dhellmannwe would want a different list for each chart anyway22:24
lbragstadyeah22:25
lbragstadthen when a project updates the documents for a specific goal, they still only have to make a change to a single repository22:25
dhellmanntrue22:25
lbragstadand it's in sync with whoever is maintaining the burndown chart22:25
dhellmanngood point22:25
lbragstadhow did you generated the list for expected_repos.txt?22:26
dhellmannsome of the stuff I did for the doc-migration burndown chart wasn't based on gerrit queries, so we want to leave room for some customization capabilities in there, too22:26
dhellmannand we might not want the charts to be tied only to the goals, since when they become easy to use they may be useful for other projects22:27
dhellmannthe doc migration is another example of that22:27
lbragstadright22:27
dhellmannit wasn't an official goal22:27
dhellmannand individual teams might find them useful, too22:28
lbragstadthat's a good point22:28
dhellmannI wonder if it makes sense to make it so the generator can be pip installed, so teams could put it in their regular doc build22:28
dhellmannor if it's better to just put all of the stuff in one repo and have a small team willing to review those patches to maintain it22:29
dhellmannand let anyone use it for whatever they want to track22:29
lbragstadthen projects can configure it with a config file specific to a chart22:29
dhellmannconfig file, maybe some custom code, yeah22:29
lbragstadthe later sounds like a step to the former22:29
dhellmannmake it really easy to dump json files in the format needed to import them cleanly22:30
dhellmanndefinitely worth exploring, I think22:30
lbragstadi agree22:30
dhellmannmaybe step 1 is set up a repo for tracking goals this time around, and see where that takes us22:30
lbragstadyeah22:30
dhellmanndon't call the repo "goals" just "burndown-dashboards" or something22:30
lbragstadbecause the data files and such need to be reset with each chart22:31
dhellmannexactly22:31
dhellmanneven the javascript needs to be tweaked, until we get something that renders that22:31
lbragstadthat seems like a good idea - maybe a simple doc with what's supported and how to bootstrap a new chart22:31
dhellmannyou know, it's probably worth looking into existing tools, too22:31
dhellmannsomething like bokeh or whatever the newest hotness is22:31
lbragstadyou mean the d3 stuff?22:31
dhellmannyeah22:31
lbragstadi thought that was super interesting22:32
lbragstadi'd never really played with it22:32
lbragstadbut yeah - exploring other things would be worth it too i think22:32
dhellmannhttps://bokeh.pydata.org/en/latest/22:32
lbragstaddhellmann: that looks like it might work22:35
dhellmannI don't know if that's any easier to use or not. Might be overkill. But it's worth looking at.22:35
lbragstad++22:35
dhellmannI could see us building a library of things to populate data sets and then using that to render them instead of also building our own rendering stuff.22:36
dhellmannI guess another way to do this would be to use storyboard22:39
dhellmannautomate adding stories or tasks or whatever and then add the visualization to that22:40
lbragstadinteresting22:40
lbragstadyeah - that wouldn't be a bad idea for adoption22:40
dhellmannI don't really fully understand the data model of storyboard, so I don't know which sorts of objects would be needed or how easy it would be to do things like create a bunch of stories with tags and then show them in a dashboard22:41
lbragstadthat's a good question22:41
lbragstadbut worth asking the storyboard team i'msure22:41
dhellmannyou know, that would give teams a place to report their status directly, too, since they could just change the story status22:41
lbragstadyeah22:42
lbragstadso you can positively assert a project has completed a goal22:42
dhellmannso we wouldn't need the data in the governance repo, if the goal page linked to the dashboard22:42
dhellmannright -- re-distribute the work of updating the status22:42
lbragstadyeah - that's a bit that we're missing in the current burndown because we don't really know how many patches are going to be necessary to implement a goal22:43
dhellmannyeah, that's why I eventually added the part to track published URLs22:43
lbragstadyeah - that makes sense22:44
dhellmannthe more I think about the storyboard part, the more I like that. it abstracts the types of tasks22:44
lbragstadright22:44
dhellmannwhen it's possible to automate closing the story with a patch, or even some other action (like a thing that looks for published URLs) we can22:44
lbragstadbecause it doens't require each dashboard to change in order to assert completion (if that makes sense)22:44
dhellmannwhen we can't, updating the data is distributed to as many people as possible22:44
dhellmannand right, it standardizes the thing being tracked22:44
dhellmannit feels a bit of a shame that we weren't able to find any existing bug tracker that worked the way we wanted22:46
lbragstadyeah22:46
lbragstadi do like that flow22:46
lbragstadwhen a goal is agreed upon, a bunch of tasks get opened for affected projects22:46
lbragstadthe burn down tracks progress/patches and knows when to take a project of the list entirely22:47
dhellmannyep, and that should be easy enough to automate by reading the governance project list22:47
dhellmannI could see teams using the feature for tracking their release cycle work visually, too22:48
lbragstadso - you essentially have a burn down chart with all the states we have in lp for example22:48
lbragstad(approve, started, implemented, etc..)22:49
dhellmannright22:49
lbragstadfor both bugs and blueprint22:49
lbragstads22:49
dhellmannI wonder how hard it would be to track status changes over time22:49
lbragstadit's really just a view at that point22:49
dhellmannvs. just a single stack bar chart22:49
dhellmannyeah, exactly22:49
lbragstadstatus changes over time?22:50
dhellmannwell, yeah. the burndown chart computes the number of items in a given state at regular intervals22:50
dhellmannthat's how you get the nice bands of color22:50
lbragstadyep22:50
dhellmannstoryboard is going to give you the current states, but not their states in the past22:50
lbragstadoh22:51
lbragstadi see what you mean22:51
dhellmannI mean, it probably can tell you when things were edited22:51
lbragstadyeah - for me, i think that would be useful22:51
dhellmannso maybe there's a new data model to go with the chart22:51
lbragstadlooking at the whole burn down of our bug work over a cycle for example22:51
dhellmannand a periodic thing to run and update that data for the chart, so that drawing the chart is pulling the sequence of numbers instead of pulling the raw data and building the sets of numbers22:52
lbragstadthe data model you have in data.csv is what accomplishes that today, right?22:52
dhellmannyeah22:52
lbragstadyeah - the deployment would have to guarantee the periodic bits22:52
dhellmannassuming the number of states of stories/tasks are fixed, and not user-configurable, the table would just be a bunch of ints and a date22:53
lbragstadyeah22:53
lbragstadi would think it would be set22:53
lbragstadunless we're talking about things like tags22:53
lbragstadwere a project can have official and unofficial tags22:53
dhellmannyou'd want to define the query to run generically somehow22:54
dhellmannso a chart would have a name, a query, and a UUID22:54
dhellmannand then the data for all charts could live in one table22:54
dhellmannand maybe we'd have an active/inactive flag so we don't recompute a bunch of old charts that aren't useful22:54
lbragstadyeah22:54
dhellmannagain, it seems like something that is likely to already exist in some other tools22:56
lbragstadright22:56
dhellmannof course our wheel would be much rounder than theirs ;-)22:57
lbragstadwe do love super round wheels22:57
lbragstadi'd be curious to see what the storyboard folks have to say about it22:57
lbragstadi'm not seeing a dedicated etherpad for the storyboard team https://wiki.openstack.org/wiki/PTG/Queens/Etherpads22:58
lbragstadmaybe a ML thread is appropriate?22:59
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for storelets team  https://review.openstack.org/50102923:02
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for tripleo team  https://review.openstack.org/50103123:06
dhellmannlbragstad : yeah, a thread seems good. I don't know if the storyboard folks have a room for the ptg23:09
dhellmannI hate to reopen the "which bug tracker should we use" can of worms, but that may be worth doing, too.23:10
*** hongbin has quit IRC23:12
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for dragonflow team  https://review.openstack.org/50103423:14
openstackgerritLance Bragstad proposed openstack/governance master: Update policy goal for os-win team  https://review.openstack.org/50103523:19
*** hongbin has joined #openstack-tc23:21
lbragstaddhellmann: yeah - fwiw ^ that should be all the reviews23:21
lbragstadfor projects that are not affected by that goal23:21
*** hongbin has quit IRC23:22

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!