<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">
<blockquote
cite="mid:2527DE00-CF9A-46DA-8728-E1FDE49E5F9F@openstack.org"
type="cite">
<div class="moz-text-html" lang="x-unicode"><meta
http-equiv="Content-Type" content="text/html; charset=UTF-8"><br
class=""><div class=""><div style="word-wrap: break-word;" class="">
<pre>Thanks a lot, ttx for starting this thread.
option 1 looks more feasible way but few question/feedback:
- How we will execute the "designate 5 members from TC and select UC chair"?
If by volunteer call from TC?
I think this can lead to the current situation where very few members are interested to
serve as UC. I am afraid that we will get 5 volunteers and a chair.
If by force?
I do not think this is or should be an option :). But if then how we make sure the TC
members are ok/good to handle the UC tasks on the non-technical side for example
ambassador program.</pre>
</div></div></div>
</blockquote>
We have dedicated Foundation Staff that offer support for the Ambassador
Program as well as User Survey. I don't have concerns about this
falling between the cracks during the transition and it's something we
can work with the new UC seats under the TC on. <br>
<br>
Cheers,<br>
Jimmy<br>
<blockquote
cite="mid:2527DE00-CF9A-46DA-8728-E1FDE49E5F9F@openstack.org"
type="cite">
<div class="moz-text-html" lang="x-unicode">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<pre>
- Will there be any change in TC elections, votes weightage and nomination? by this change
of a new subteam under TC?
- I think along with the merging proposal, we should distribute the current tasks handled by UC
among TC, Ops group, foundation etc. For example, the ambassador program, local user group
interaction or any other managerial tasks should be excluded from TC scope.
If we would like to merge all then I think we should rename TC to Steering Committee or
something which is option 3.
- What about merging UC into Ops team, they are more close to users/operators and active
in terms of the meetup and providing feedback etc.
-gmann</pre>
</div>
<br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">Begin
forwarded message:</div><br class="Apple-interchange-newline"><div
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px;" class=""><span style="font-family:
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;
color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span
style="font-family: -webkit-system-font, Helvetica Neue, Helvetica,
sans-serif;" class="">Thierry Carrez <<a moz-do-not-send="true"
href="mailto:thierry@openstack.org" class="">thierry@openstack.org</a>><br
class=""></span></div><div style="margin-top: 0px; margin-right: 0px;
margin-bottom: 0px; margin-left: 0px;" class=""><span
style="font-family: -webkit-system-font, Helvetica Neue, Helvetica,
sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span
style="font-family: -webkit-system-font, Helvetica Neue, Helvetica,
sans-serif;" class=""><b class="">Re: [all][tc][uc] Uniting the TC and
the UC</b><br class=""></span></div><div style="margin-top: 0px;
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span
style="font-family: -webkit-system-font, Helvetica Neue, Helvetica,
sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span
style="font-family: -webkit-system-font, Helvetica Neue, Helvetica,
sans-serif;" class="">February 25, 2020 at 11:36:06 AM CST<br class=""></span></div><div
style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px;
margin-left: 0px;" class=""><span style="font-family:
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;
color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span
style="font-family: -webkit-system-font, Helvetica Neue, Helvetica,
sans-serif;" class=""><a moz-do-not-send="true"
href="mailto:openstack-discuss@lists.openstack.org" class="">openstack-discuss@lists.openstack.org</a><br
class=""></span></div><br class=""><div class=""><div class="">Tim Bell
wrote:<br class=""><blockquote type="cite" class="">Are there some
stats on the active electorate sizes ?<br class="">I
have the impression that the voting AUCs were a smaller number of
people than the contributors so a single election may result in less
total representation compared to today’s UC & TC.<br class=""></blockquote><br
class="">I
don't have the exact numbers around, but yes, there are many more ATCs
(voters in the current TC election) than AUCs (voters in the current UC
election).<br class=""><br class="">So it's a valid concern that people
with more of an operator background would have trouble getting elected
if the electorate contains more people with more of a developer
background.<br class=""><br class="">But I think it's a fallacy. There
is plenty of overlap. Most engaged operators are already ATCs, and more
and more contributors have operational experience. Data points show that
when people with more operational background have nominated themselves
for the TC in recent elections, they got elected. 10 of the 13 TC seats
are currently occupied by people with some decent amount of operational
experience.<br class=""><br class="">So yes, we clearly need to
communicate that people with operational/usage experience are wanted in
that new body. We need to communicate that there is a change, and a
single body will now steward all aspects of the open source projects and
not just the upstream aspects. But I'm not obsessing on the fact that a
single election would somehow suppress operator voices...<br class=""><br
class="">The
problem recently has more been to find enough people willing to step up
and spend extra time stewarding OpenStack, than to actually get
elected.<br class=""><br class="">-- <br class="">Thierry Carrez (ttx)<br
class=""><br class=""></div></div></blockquote></div><br class="">
</div>
</blockquote>
<br>
</body></html>