Open Stack

Sean,

I think this is exactly what I think we are looking to change.  There is a
lot of work that is captured via etherpad's at each of the Midcycle and
other meetups that is probably not sent up to each of the groups.  The
reason I think this is because I see the some of the same issues that
Operators are discussing over and over again.  Now, there is work that Kris
mentioned that they have submitted and keep on top of, and I know there is
other work from a few others that contribute, but I'm not sure if the rest
of the Operators have the opportunity to get their information over to the
right people.

That last point is what I am looking to help change.  There is a lot that I
think the group can help out with to make sure we capture what we get via
etherpads and turn them into "Blueprints", "Bugs", etc so we can help
follow-up with projects and track them for the entire Operators group.

Maybe I'm wrong about this, maybe all the entries from the etherpads are
read by projects and fed into their pipelines.

--Joe

On Mon, Apr 11, 2016 at 11:11 AM, Sean M. Collins <sean at coreitpro.com>
wrote:

> To be blunt: Are we ensuring that all this work that people are
> capturing in these working groups is actually getting updated and
> communicated to the developers?
>
> As I become more involved with rolling upgrades, I will try and attend
> meetings and be available from the WG side, but I don't believe I've
> ever seen someone from the WG side come over to Neutron and say "We need
> XYZ and here's a link to what we've captured in our repo to explain what
> we mean"
>
> But then again I'm not on the neutron-drivers team or a core.
>
> Anyway, I updated what I've been involved with in the Mitaka cycle, when
> it comes to Neutron and upgrades (https://review.openstack.org/304181)
>
> --
> Sean M. Collins
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160411/df0d9df8/attachment.html>