Open Stack

On Thu, Aug 14, 2014 at 4:02 PM, Eoghan Glynn <eglynn at redhat.com> wrote:

>
> > > Additional cross-project resources can be ponied up by the large
> > > contributor companies, and existing cross-project resources are not
> > > necessarily divertable on command.
> >
> > Sure additional cross-project resources can and need to be ponied up,
> but I
> > am doubtful that will be enough.
>
> OK, so what exactly do you suspect wouldn't be enough, for what
> exactly?
>
>
I am not sure what would be enough to get OpenStack back in a position
where more developers/users are happier with the current state of affairs.
Which is why I think we may want to try several things.



> Is it the likely number of such new resources, or the level of domain-
> expertise that they can be realistically be expected bring to the
> table, or the period of time to on-board them, or something else?
>
>
Yes, all of the above.


> And which cross-project concern do you think is most strained by the
> current set of projects in the integrated release? Is it:
>
>  * QA
>  * infra
>  * release management
>  * oslo
>  * documentation
>  * stable-maint
>
> or something else?
>
>
Good question.

IMHO QA, Infra and release management are probably the most strained. But I
also think there is something missing from this list. Many of the projects
are hitting similar issues and end up solving them in different ways, which
just leads to more confusion for the end user. Today we have a decent model
for rolling out cross-project libraries (Oslo) but we don't have a good way
of having broader cross project discussions such as: API standards (such as
discoverability of features), logging standards, aligning on concepts
(different projects have different terms and concepts for scaling and
isolating failure domains), and an overall better user experience. So I
think we have a whole class of cross project issues that we have not even
begun addressing.



> Each of those teams has quite different prerequisite skill-sets, and
> the on-ramp for someone jumping in seeking to make a positive impact
> will vary from team to team.
>
> Different approaches have been tried on different teams, ranging from
> dedicated project-liaisons (Oslo) to shared cores (Sahara/Infra) to
> newly assigned dedicated resources (QA/Infra). Which of these models
> might work in your opinion? Which are doomed to failure, and why?
>
> So can you be more specific here on why you think adding more cross-
> project resources won't be enough to address an identified shortage
> of cross-project resources, while de-integrating projects would be?
>
> And, please, can we put the proverbial strawman back in its box on
> this thread? It's all well and good as a polemic device, but doesn't
> really move the discussion forward in a constructive way, IMO.
>
> Thanks,
> Eoghan
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> 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/20140815/4ded83d4/attachment.html>