| *** emagana has quit IRC | 00:21 | |
| *** gcb has joined #openstack-tc | 01:36 | |
| *** gcb has quit IRC | 02:12 | |
| *** gcb has joined #openstack-tc | 02:15 | |
| *** gcb has quit IRC | 05:21 | |
| *** gcb has joined #openstack-tc | 05:23 | |
| *** jpich has joined #openstack-tc | 07:34 | |
| *** dtantsur|afk is now known as dtantsur | 08:36 | |
| *** cdent has joined #openstack-tc | 08:36 | |
| cdent | it’s office hours time | 09:00 |
|---|---|---|
| * cdent puts out the sign | 09:00 | |
| cdent | An issue I’d like to get on an agenda somewhere, probably related to the strategic goal of simplification (and perhaps top 5 list and friends): More assertively enabling refactoring and tech debt handing. | 09:02 |
| cdent | This is a story as old as the world, but it’s commonality makes it no less important. | 09:03 |
| cdent | New contributors come along to look at OpenStack and in some cases are confronted with code that is so dense, so complex, so hard to change that they choose to go away. | 09:03 |
| cdent | Some of this is the result of organic growth, some of it is the result of less than great architectural decisions, but some of it is simply that we don’t follow simple rules of thumb when writing code: | 09:04 |
| cdent | things like extracing methods, keeping methods short, avoiding side effects, keeping modules short | 09:05 |
| gcb | cdent: oslo have some deprecated stuff to clean up, does that belong to your plan ? | 09:07 |
| gcb | https://etherpad.openstack.org/p/oslo-queens-tasks | 09:08 |
| cdent | To some extent, yes. That’s the sort of cleaning up that thingee has been trying to drive with his work on the simplification strategic goal. | 09:08 |
| johnthetubaguy | cdent: I like the assumption or architectural decisions | 09:09 |
| johnthetubaguy | cdent: I honestly assumed it was the users/operators that need the simplification more, but agreed the dev side is important | 09:10 |
| cdent | Part of this thinking stems from my own exhaustion with just how incredibly hard it is sometimes to get stuff done. | 09:10 |
| johnthetubaguy | certainly much we want to do hits up against tech debt (in all its many forms) | 09:11 |
| * cdent nods | 09:11 | |
| *** evrardjp has joined #openstack-tc | 09:12 | |
| johnthetubaguy | I see placement work and cells work as tech debt removal efforts, I mean they are more than that, but it unblocks so much future work | 09:12 |
| cdent | yes, except we’re constantly uncovering more as we inch forward. | 09:13 |
| johnthetubaguy | I guess my question is how do we sell the value of the work, and how best to keep track of it so those who are interested / value it can easily pick it up | 09:14 |
| cdent | it is good that we are uncovering it (very good), but the list, oh my | 09:14 |
| cdent | well, that’s part of why I listed the “things like…” above. Those are measurable things which are somewhat agreed upon as ways to inspect code for smelliness | 09:15 |
| cdent | when we have limited review bandwidth we often treat those kinds of fixes with disdain, but I think that’s a bad choice | 09:15 |
| johnthetubaguy | I duno, I quite like those little reviews, my problem is finding them in the big haystack of doom with 17 people screaming for attention | 09:16 |
| johnthetubaguy | for clarity, merging more of that good stuff gets my support, I am just wondering how best to make it happen | 09:17 |
| cdent | we could expose code metrics a bit more globally | 09:17 |
| cdent | unit and functional coverage results, radon results, that sort of thing | 09:18 |
| cdent | rather than advertising lines of code added, we could trumpet about lines of code removed | 09:20 |
| johnthetubaguy | its worth trying, I don't remember why some of those got pulled down | 09:29 |
| johnthetubaguy | who is doing the lines of code added? I can't remember where those stats are now, which feels bad. | 09:30 |
| cdent | I’m not sure it is a regular thing, but it is something that gets talked about at the end of a cycle “In pike there were N commits from X people, adding M lines of code to the total Y million lines of code that make up openstack” or whatever | 09:32 |
| cdent | basically I think we need to do a bit of culture jamming | 09:33 |
| johnthetubaguy | I guess if we get out there first with better stats, they get into the marketing | 09:35 |
| * cdent nods | 09:37 | |
| johnthetubaguy | cdent: been thinking more about users, working much more with users in the new job, as I hoped. | 09:51 |
| cdent | excellent | 09:51 |
| cdent | any surprises so far? | 09:51 |
| johnthetubaguy | apart from seeing "little niggles" turn into massive mountain sized road blocks for new comers I don't have anything that big | 09:51 |
| johnthetubaguy | saw a deploy that moved to keystone v3, but horizon is till only giving our v2 RC files, that was... frustrating | 09:52 |
| johnthetubaguy | but yeah, looking forward to learning a lot more | 09:53 |
| johnthetubaguy | certainly feels like that getting from the point of pressing buttons to getting a good undertanding of how things actually works, and the context around it, so you know what to do | 09:54 |
| johnthetubaguy | seems like a bigger hurdle than you would hope for | 09:55 |
| * cdent nods | 09:55 | |
| johnthetubaguy | oh, I saw someone had deleted an instance created by sahara in an ironic based cloud | 09:59 |
| johnthetubaguy | that left behind the port, and a partial heat stack | 10:00 |
| johnthetubaguy | which stopped some VMs booting, because the port was trying to bind to the same mac as the existing port | 10:00 |
| johnthetubaguy | ...technically correct behaviour in isolation, together, well, <insert you fav nasty word> | 10:02 |
| johnthetubaguy | I think better supporting applications / layering of services is probably the most important missing functionality, like zaneb said I guess | 10:03 |
| * cdent nods | 10:04 | |
| *** dtantsur is now known as dtantsur|bbl | 10:40 | |
| *** alex_xu has quit IRC | 11:02 | |
| *** alex_xu has joined #openstack-tc | 11:06 | |
| fungi | cdent: after the leadership summit in boston the bod, tc and uc members present determined that simplification was one of the top 5 topics we needed to address. unfortunately when it came time for volunteers only thingee raised his hand. he's been making some great progress but i expect he'd appreciate assistance | 11:55 |
| cdent | fungi: I’m aware of that. And I think it’s important, and I want to help, but like many people I’m overtasked. Also, while I applaud the efforts to simplify for users/deployers, the wheel I’m squeaking is complexity for contributors | 11:57 |
| fungi | and i do think from a marketing and publicity standpoint we tend to focus too much on what we added in a given cycle rather than on what we removed. maybe that would help get some more people interested or at least looking at things from that angle | 11:58 |
| cdent | While I think that user experience always trumps developer experience, the mandate I’ve taken on for myself as a tc person is dev experience (at some point I said something akin to “union rep”) | 11:58 |
| fungi | cdent: yeah, on the simplicity for contributors front, i'm glad we were finally able to drop the tie-in to foundation membership | 11:59 |
| cdent | yeah, I think if we can have some kind of blurb (somewhere, i’m not sure where) that is the “here’s what we removed” excitement, that would be fun | 11:59 |
| cdent | yes, that was a _huge_ win | 11:59 |
| fungi | i'm setting my sights on the cla to dco move in the next couple cycles as another major hurdle | 11:59 |
| fungi | and working on condensing down to a single single-sign-on ;) | 12:00 |
| cdent | sssssssssssso | 12:01 |
| fungi | yeah, single-sign-on doesn't help too much if you have more than one | 12:01 |
| cdent | All that stuff will be a great help, thanks for holding that flag. | 12:01 |
| fungi | thingee is collaborating with the foundation's web dev team to revamp the onboarding documentation into more of a prompted webapp which can steer new contributors more effectively to their areas of interest and make sure they set up the tools they need to be prepared for that | 12:02 |
| cdent | That’s like the front door stuff. Once through the door, it’s a bit of a situation of “wow, how do I get to the kitchen from here" | 12:02 |
| fungi | and the openstack upstream institute effort has been picking up steam and the team on that is trying to get the materials/coursework more reconsumable so that volunteers can easily step up to give the courses at user group meetings or within companies | 12:05 |
| fungi | but i agree, that's all front-door | 12:05 |
| cdent | It may be that by simply getting more people through the door the available pool of people will include hardy souls who are invested in cleanup. That will get them to the kitchen. | 12:06 |
| cdent | But then we also need to make sure there is sufficient willingness on the part of reviewers. | 12:06 |
| cdent | (our complexity is complex) | 12:06 |
| fungi | the more people who make it through the front door, the less we'll notice all the ones who get lost on their way to the kitchen, accidentally lock themselves in the basement and starve to death? ;) | 12:07 |
| fungi | yeah, the front-door solutions are (relatively speaking) easier because they apply a lot more globally across the contributor base. most of the intra-project complexity which hampers contribution varies a lot and so is probably harder to address with generalized solutions | 12:08 |
| * cdent nods | 12:09 | |
| fungi | not to say that we shouldn't also work to improve there | 12:09 |
| fungi | but i think it needs already embedded contributors to spot those complexities and address them or at least surface them so others know where to focus | 12:10 |
| cdent | yeah | 12:11 |
| cdent | sometimes, though, I think people who are embedded get used to it. it becomes normal. | 12:12 |
| fungi | it does require to put on newcomer glasses and look around. i agree that's also not easy | 12:13 |
| fungi | and trying to keep track of what issues new contributors raise and ask for help addressing | 12:13 |
| smcginnis | cdent: +1 for tackling technical debt and working on developer simplification. | 12:54 |
| smcginnis | I think developer simplification will naturally lead to some end user simpification. | 12:55 |
| cdent | Yeah, I think (or at least hope) so too | 12:56 |
| *** cdent has quit IRC | 13:30 | |
| *** hongbin has joined #openstack-tc | 13:59 | |
| *** marst has joined #openstack-tc | 14:11 | |
| *** dtantsur|bbl is now known as dtantsur | 15:13 | |
| openstackgerrit | Sean McGinnis proposed openstack/project-team-guide master: Add reno usage for editing stable branch notes https://review.openstack.org/496318 | 17:07 |
| openstackgerrit | Sean McGinnis proposed openstack/project-team-guide master: Add reno usage for editing stable branch notes https://review.openstack.org/496318 | 17:10 |
| openstackgerrit | Andreas Jaeger proposed openstack/governance master: Update docs URLs https://review.openstack.org/496321 | 17:14 |
| openstackgerrit | Andreas Jaeger proposed openstack/governance master: oslo-incubator is retired, mark it as such https://review.openstack.org/496325 | 17:18 |
| *** jpich has quit IRC | 17:28 | |
| *** dtantsur is now known as dtantsur|afk | 18:05 | |
| *** cdent has joined #openstack-tc | 18:47 | |
| cdent | weak tc report his week | 19:09 |
| smcginnis | cdent: Maybe too many other things going on at this point in the cycle? | 19:12 |
| cdent | yeah, I think that’s probably the case | 19:12 |
| cdent | but I know myself well enough that if I skip one because there’s not enough going on that week I’ll end up breaking the habit | 19:13 |
| smcginnis | I know what you mean. :) | 19:17 |
| openstackgerrit | Andreas Jaeger proposed openstack/governance master: oslo-incubator is retired, mark it as such https://review.openstack.org/496325 | 19:43 |
| openstackgerrit | Andreas Jaeger proposed openstack/governance master: Update docs URLs https://review.openstack.org/496321 | 19:44 |
| openstackgerrit | Sean McGinnis proposed openstack/project-team-guide master: Add reno usage for editing stable branch notes https://review.openstack.org/496318 | 20:26 |
| openstackgerrit | Chris Dent proposed openstack/governance master: Add Reduce Development Complexity top-5 https://review.openstack.org/496404 | 20:30 |
| cdent | johnthetubaguy, fungi, smcginnis ^ | 20:31 |
| cdent | very WIPpy | 20:31 |
| cdent | smcginnis: yeah, the packaging of the idea is where I struggled | 20:35 |
| smcginnis | cdent: Yeah, I can't think of a good way. Maybe we need to come up with some semi-arbitrary metrics in order to decide when we've "completed" the work. | 20:38 |
| cdent | as if anyone would be able to agree on that? I mean: I would say no modules > 1000 lines as an easy target | 20:38 |
| cdent | which means most of nova needs a rewrite | 20:38 |
| cdent | :) | 20:38 |
| smcginnis | Or as an alternative for a top-5 goal, have some way to positively reinforce code cleanup work. | 20:38 |
| smcginnis | True. :) | 20:38 |
| smcginnis | Maybe like a stackalytics option that shows a ranking of people that have removed the most lines of code per release. | 20:39 |
| cdent | Yeah, I’m not sure if top5 is the right way to go but I figured it was a reasonable way to concretize the discussion | 20:39 |
| cdent | that’s but one of many metrics, and scarily easy to game to very bad results | 20:40 |
| smcginnis | cdent: Yes, definitely good to get the conversation going. | 20:40 |
| smcginnis | Right, any kind of metric we want to guage off of, someone is going to find a way to get their name higher on the list. | 20:40 |
| smcginnis | *gauge | 20:41 |
| *** cdent has quit IRC | 21:30 | |
| *** marst has quit IRC | 22:22 | |
| *** hongbin has quit IRC | 23:13 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!