Open Stack

Off-hand, I think there needs to be a few more words agreed upon for each
in terms of what each item practically means.

In other words, does #1 mean each python-clientlibrary's OSC plugin is
ready to rock and roll, or we talking about everyone rewriting all client
interactions in to openstacksdk, and porting existing OSC plugins use that
different python sdk.

In other words, some projects could find it very easy or that they are
already done, where as others could find themselves with a huge lift that
is also dependent upon review bandwidth that is outside of their control or
influence which puts such a goal at risk if we try and push too hard.

-Julia


On Tue, Dec 4, 2018 at 9:43 AM Lance Bragstad <lbragstad at gmail.com> wrote:

> Hi all,
>
> The purpose of this thread is to have a more focused discussion about what
> we'd like to target for Train community goals, bootstrapped with the
> outcomes from the session in Berlin [0].
>
> During the session, we went through each item as a group and let the
> person who added it share why they thought it would be a good community
> goal candidate for the next release. Most goals have feedback captured in
> etherpad describing next steps, but the following stuck out as top
> contenders from the session (rated by upvotes):
>
>    1. Moving legacy clients to python-openstackclient
>    2. Cleaning up resources when deleting a project
>    3. Service-side health checks
>
> I don't think I missed any goals from the session, but if I did, please
> let me know and I'll add it to the list so that we can discuss it here.
>
> Does anyone have strong opinions either way about the goals listed above?
>
> [0] https://etherpad.openstack.org/p/BER-t-series-goals
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181204/cb738ddd/attachment-0001.html>