Open Stack

Thanks boris for starting this topic,

There is a balance here that needs to be worked out and I've seen specs start to turn into requirements for every single patch (even if the patch is pretty small). I hope we can rework the 'balance in the force' to avoid being so strict that every little thing requires a spec. This will not end well for us as a community.

How have others thought the spec process has worked out so far? To much overhead, to little…?

I personally am of the opinion that specs should be used for large topics (defining large is of course arbitrary); and I hope we find the right balance to avoid scaring everyone away from working with openstack. Maybe all of this is part of openstack maturing, I'm not sure, but it'd be great if we could have some guidelines around when is a spec needed and when isn't it and take it into consideration when requesting a spec that the person you have requested may get frustrated and just leave the community (and we must not have this happen) if you ask for it without explaining why and how clearly.

From: Boris Pavlovic <bpavlovic at mirantis.com<mailto:bpavlovic at mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Monday, June 30, 2014 at 2:11 PM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [all][specs] Please stop doing specs for any changes in projects

Hi all,

Specs are interesting idea, that may be really useful, when you need to discuss large topics:
1) work on API
2) Large refactoring
3) Large features
4) Performance, scale, ha, security issues that requires big changes

And I really dislike idea of adding spec for every patch. Especially when changes (features) are small, don't affect too much, and they are optional. It really kills OpenStack. And will drastically slow down process of contribution and reduce amount of contributors.

Thanks.


Best regards,
Boris Pavlovic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140630/c5d97052/attachment.html>