Open Stack

On 2019-05-08 14:27:54 -0400 (-0400), Zane Bitter wrote:
> On 4/05/19 9:25 AM, Emmet Hikory wrote:
> > Zhipeng Huang wrote:
> > > Then it might fit the purpose to rename the technical
> > > committee to governance committee or other terms. If we have a
> > > technical committee not investing time to lead in technical
> > > evolvement of OpenStack, it just seems odd to me.
> > 
> > OpenStack has a rich governance structure, including at least
> > the Foundation Board, the User Committee, and the Technical
> > Committee.  Within the context of governance, the Technical
> > Committee is responsible for both technical governance of
> > OpenStack and governance of the technical community. It is
> > within that context that "Technical Committee" is the name.
> > 
> > I also agree that it is important that members of the Technical
> > Committee are able to invest time to lead in the technical
> > evolution of OpenStack, and this is a significant reason that I
> > propose that the activities of the TC be restricted, precisely
> > so that being elected does not mean that one no longer is able
> > to invest time for this.
> 
> Could you be more clear about which activities you think should be
> restricted? Presumably you're arguing that there should be
> fewer... let's call it "ex officio" responsibilities to being a TC
> member.
> 
> The suggestion reads as kind of circular, because you appear to be
> saying that aspiring TC members should be doing certain kinds of
> socially useful tasks that are likely to get them elected to the
> TC, where they will be restricted from doing those tasks in order
> to make sure they have free time to do the kinds of socially
> useful things they were doing prior to getting elected to the TC,
> except that those are now restricted for them. Presumably we're
> actually talking about different sets of tasks there, but I don't
> think we can break the loop without being explicit about what they
> are.
[...]

My read was that the community should, each time we assert there's
something we want done and we think the TC should also take care of
for us, step back and consider that those TC members are already
deeply embedded in various parts of our community as well as
adjacent communities getting other things done (likely the same
things which got them elected to seats on the TC to begin with), and
that each new thing we want them to tackle is going to take the
place of yet more of those other things they'll cease having time
for as a result. Taken from another perspective, it's the idea that
the TC as a governing body should limit its focus to governance
tasks and stop feeling pressured to find yet more initiatives and
responsibilities for itself, leaving more time for the folks serving
on the TC to also continue doing all manner of other important tasks
they feel compelled to do in their capacity as members of the
community rather than with their "TC hats" on.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190508/e422b72d/attachment.sig>