Open Stack

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 :)

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.

-Kendall (diablo_rojo)

On Thu, Jun 22, 2017 at 1:49 PM Lance Bragstad <lbragstad at gmail.com> wrote:

>
>
> On 06/22/2017 12:57 PM, Mike Perez wrote:
>
> Hey all,
>
> 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:
>
> 1) Split Tempest plugins into separate repos/projects [1]
> 2) Move policy and policy docs into code [2]
>
> 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.
>
> 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.
>
> 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]?
>
> 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).
>
> Is the role of a goal "champion" limited to a single person? Can it be
> distributed across multiple people pending actions are well communicated?
>
>
> [1] -
> https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
> [2] -
> https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg106392.html
> [3] -
> http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-06-20-20.01.log.html#l-10
>
> —
> Mike Perez
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170623/432c0514/attachment.html>