Open Stack

On 2018-01-23 01:40 PM, Chris Dent wrote:
> 
> (Hyperlinkified for your pleasure: 
> https://anticdent.org/tc-report-18-04.html )
> 
> When a person is in early adolescence they get cramps in their legs
> and call it growing pains. Later, in adulthood, there's a different
> kind of pain when the strategies and tactics used to survive
> adolescence are no longer effective and there's a chafing that won't
> subside until there's been a change in behavior and expectations; an
> adaptation to new constraints and realities.
> 

i love this intro. when does your coming-of-age book come out? :)

> 
> ## OpenStack-wide Goals
> 
> These need to be validated by the community, but they are not [getting
> as much
> feedback](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-01-23.log.html#t2018-01-23T09:16:51) 
> 
> as hoped. There are different theories as to why, from "people are
> busy", to "people don't feel empowered to comment", to "people don't
> care". Whatever it is, without input the onus falls on the TC to make
> choices, increasing the risk that the goals will be perceived as a
> diktat. As always, we need to work harder to have high fidelity
> feedback loops. This is especially true in our "mature" phase.
> 

i think this probably links back to the issues with openstack-specs. 
maybe it's because the tasks aren't flashy enough, maybe it's because 
people have too much work. personally, i've never had a user/anyone tell 
me that "goal X would be useful in your project" and considering how 
silo'd the projects are, looking outside my project of focus is not very 
high on priority.

> 
> ## PTL Balance
> 
> In [this morning's office
> hours](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-01-18.log.html#t2018-01-18T15:43:53) 
> 

this link is wrong! you made me read stuff i didn't want to read! :P i'm 
going to guess it roughly starts here: 
http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-01-23.log.html#t2018-01-23T09:48:03

> we had a discussion about ways to help the PTL role (especially of the
> larger and most active projects) be more manageable and balanced. The main
> challenge is that as currently constituted, the person in the PTL role
> often needs to keep the state of the whole project in their head.
> 
> That's not sustainable.
> 

if i were to (potentially) oversimplify it, i would agree with this 
statement: 
http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-01-23.log.html#t2018-01-23T10:12:22

i don't believe a PTL necessarily has to keep the whole state of the 
project in their head (although they could). ultimately, it's up to the 
PTL to decide how much they're willing to defer to others.

cheers,
-- 
gord