Open Stack

I meant the administrative overhead of the contributor having to submit
a spec to Gerrit and then everyone having to deal with yet another
review, not the overhead of writing/reviewing the spec itself.

On Tue, Jul 01 2014, Dolph Mathews wrote:

> The argument has been made in the past that small features will require
> correspondingly small specs. If there's a counter-argument to this example
> (a "small" feature requiring a relatively large amount of spec effort), I'd
> love to have links to both the spec and the resulting implementation so we
> can discuss exactly why the spec was an unnecessary additional effort.
>
> On Tue, Jul 1, 2014 at 10:30 AM, Jason Dunsmore <
> jason.dunsmore at rackspace.com> wrote:
>
>> On Mon, Jun 30 2014, Joshua Harlow wrote:
>>
>> > 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.
>>
>> +1 I think specs are too much overhead for small features.  A set of
>> guidelines about when specs are needed would be sufficient.  Leave the
>> option about when to submit a design vs. when to submit code to the
>> contributor.
>>
>> Jason
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev