Open Stack

OpenSSL is a recent case. Everyone relied upon it in production but it just wasn't getting the support it needed to be healthy, and everyone suffered. An event shone light on the problem and its getting better. But it was an unfortunate event that caused people to look at it. It would be better if it could be done more thoughtfully, which I think the tag is attempting to do. So, it doesn't just happen to fledgling projects, but old, well established ones too.

Thanks,
Kevin
________________________________________
From: Kuvaja, Erno [kuvaja at hpe.com]
Sent: Monday, September 14, 2015 4:54 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all][TC] 'team:danger-not-diverse tag' and my concerns

> -----Original Message-----
> From: Thierry Carrez [mailto:thierry at openstack.org]
> Sent: Monday, September 14, 2015 9:03 AM
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [all][TC] 'team:danger-not-diverse tag' and my
> concerns
>
<CLIP>
>
> Or are you suggesting it is preferable to hide that risk from our
> operators/users, to protect that project team developers ?
>
> --
> Thierry Carrez (ttx)
>
Unfortunately this seems to be the trend, not only in <insert any group here> but in society. Everything needs to be everyone friendly and politically correct, it's not ok to talk about difficult topics with their real names because someone involved might get their feelings hurt, it's not ok to compete as losers might get their feelings hurt.

While being bit double edged sword I think this is exact example of such. One could argue if the project has reason to exist if saying out loud "it does not have diversity in its development community" will kill it. I think there is good amount of examples both ways in open source world where abandoned projects get picked up as there is people thinking they still have use case and value, on the other side maybe promising projects gets forgotten because no-one else really felt the urge to keep 'em alive.

Personally I feel this being bit like stamping feature experimental. "Please feel free to play around with it, but we do discourage you to deploy it in your production unless you're willing to pick up the maintenance of it in the case the team decides to do something else." There is nothing wrong with that.

I don't think these should be hiding behind the valance of the big tent and the consumer expectations should be set at least close to the reality without them needing to do huge amount of detective work. That was the point of the tags in first place, no?

Obviously above is just my blunt self. If someone went and rage killed their project because of that, good for you, now get yourself together and do it again. ;)

- Erno (jokke) Kuvaja

__________________________________________________________________________
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