<div dir="ltr"><div>I think more than one champion is helpful in some cases, but its dangerous when you get more than two that each person thinks the other two will handle things unless they are very communicative with one another :) <br><br>Somewhere else in this thread the idea of a committee and a chair was mentioned which seems like a good way of handling it. One primary point of contact that delegates to the others when they need help. <br><br></div>-Kendall (diablo_rojo) <br><div><div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 22, 2017 at 1:49 PM Lance Bragstad <<a href="mailto:lbragstad@gmail.com">lbragstad@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
<br>
<div class="m_4999128119555836933moz-cite-prefix">On 06/22/2017 12:57 PM, Mike Perez
wrote:<br>
</div>
<blockquote type="cite">
<div>
<div>
<div>
<div>Hey all,</div>
<div><br>
</div>
<div>In the community wide goals, we started as a group
discussing
goals at the OpenStack Forum. Then we brought those ideas
to the
mailing list to continue the discussion and include those
that were
not able to be at the forum. The discussions help the TC
decide on
what goals we will do for the Queens release. The goals
that have
the most support so far are:</div>
<div><br>
</div>
<div>1) Split Tempest plugins into separate repos/projects
[1]</div>
<div>2) Move policy and policy docs into code [2]</div>
<div><br>
<div>In the recent TC meeting [3] it was recognized that
goals in
Pike haven't been going as smoothly and not being
completed. There
will be a follow up thread to cover gathering feedback
in an
etherpad later, but for now the TC has discussed
potential actions
to improve completing goals in Queens.</div>
<div><br>
</div>
<div>An idea that came from the meeting was creating a
role of
"Champions", who are the drum beaters to get a goal done
by helping
projects with tracking status and sometimes doing code
patches.
These would be interested volunteers who have a good
understanding
of their selected goal and its implementation to be a
trusted
person.</div>
<div><br>
</div>
<div>What do people think before we bikeshed on the name?
Would
having a champion volunteer to each goal to help? Are
there ideas
that weren't mentioned in the TC meeting [3]?</div>
</div>
</div>
</div>
</div>
</blockquote></div><div>
I like this idea. Some projects might have existing context about a
particular goal built up before it's even proposed, others might
not. I think this will help share knowledge across the projects that
understand the goal with projects who might not be as familiar with
it (even though the community goal proposal process attempts to fix
that).<br>
<br>
Is the role of a goal "champion" limited to a single person? Can it
be distributed across multiple people pending actions are well
communicated?</div><div><br>
<blockquote type="cite">
<div>
<div>
<div>
<div>
<div><br>
</div>
<div>[1] - <a href="https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html" target="_blank">https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html</a></div>
<div>[2] - <a href="https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg106392.html" target="_blank">https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg106392.html</a></div>
<div>[3] <span style="background-color:rgba(255,255,255,0)">- <a href="http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-06-20-20.01.log.html#l-10" target="_blank">http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-06-20-20.01.log.html#l-10</a></span></div>
<div><br>
<div class="m_4999128119555836933bloop_sign">
<div>—</div>
Mike Perez</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="m_4999128119555836933mimeAttachmentHeader"></fieldset>
<br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="m_4999128119555836933moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="m_4999128119555836933moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div></div>