Open Stack

Hey Neil, it's entirely possible I missed some folks. Feel free to reply to
this thread.

I'll include some of the preamble and questions from my original note.

-----

The TC has come up with two strategies for clarification: (1) Make sure
external drivers are properly listed and discoverable on OpenStack
websites, and (2) Establish a new "driver team" concept (see
https://review.openstack.org/#/c/403829/).

As maintainers for neutron, cinder and ironic drivers, we’re asking you for
your opinion on this matter. We need to know if we are solving the right
problem here.

Are driver teams looking for recognition? I.e. receiving ATC status, see
their work recognized as an official part of “OpenStack”?
Are driver teams looking for discoverability? I.e. having their drivers
listed together with all the other available drivers on the OpenStack
Marketplace or DriverLog websites ?
Are driver teams looking for documentation visibility? I.e. having an
official place to host configuration guides? On docs.o.org?
Are driver teams looking for independence? I.e. the ability to manage and
nominate their own core members?
Anything else we missed?

On Jan 10, 2017 5:55 AM, "Neil Jerram" <neil at tigera.io> wrote:

> Hi Steve,
>
> On Tue, Jan 10, 2017 at 7:35 AM Steve Martinelli <s.martinelli at gmail.com>
> wrote:
>
>> In preparation for the next TC meeting, a survey was sent out to driver
>> maintainers, here is a summary of the feedback that was gathered.
>>
>
> Did you send that survey to me, for networking-calico?  I'm afraid I don't
> recall it - so worried either that I missed, or that networking-calico was
> missed for some reason.
>
> Thanks,
>      Neil
>
> __________________________________________________________________________
> 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/20170110/e160bae6/attachment.html>