[openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time
aschultz at redhat.com
Fri May 5 17:43:27 UTC 2017
On Fri, May 5, 2017 at 10:52 AM, Dean Troyer <dtroyer at gmail.com> wrote:
> On Fri, May 5, 2017 at 11:36 AM, Alex Schultz <aschultz at redhat.com> wrote:
>> configuration and usability issues. But those aren't exciting so
>> people don't want to work on them...
> [Not picking on Alex here, but I've seen this repeated again in this
> thread like every other one]
> s/people/corporate project managers/
> Yes, there are individual preferences involved here, but those of us
> who are in a position to CHOOSE which projects we invest in are
> actually in the minority, and shrinking.
Yes I do not want to discount the folks who get paid to do a thing.
That being said, I believe there's a push for some of the initiatives
(or at least specific implementations) that are outside of the 'I'm
getting paid for this' and rather 'I have to do this because I'm paid
to, so let me go do it with this $hotness'. We could point to the
$language conversations as well where it's asked "is that really
necessary? Is this better for the end user?". I know my view is a
bit different because I personally like solving issues for the end
user and I understand that's not everyone's thing. It's just
something that I think the community could benefit from.
> The choices of what contributing companies invest in are largely
> determined by their customers, or where they feel their business needs
> to go. Infrastructure, SDKs, documentation, none of these are on any
> of the public roadmaps that I have seen (I have not seen them all so
> speak up where I am wrong here).
I know I like to push for upstream documentation to make sure when we
write something we actually write the thing that we said we would and
it works as expected. But yea, other items like infrastructure is
probably not high on some companies list.
> Those who are customers of these sponsor/contributor companies also
> need to be bugging them for these things too, and not just "enterprise
> ready" or "telco ready" or "GPU ready" or whatever their particular
> shiny thing is this year.
> Make long term releases important on corporate bottom lines and it
> WILL become a thing.
They already are, but just not in the public. So at that point, they
become a reason why people continue to use older versions and still
diverge from upstream because they don't need to because $vendor is
the person they go to when they need something.
> Dean Troyer
> dtroyer at gmail.com
> Tragedy. Commons. Rinse. Repeat.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev