at does everyone think?
From: Malini Kamalambal mailto:malini.kamalam...@rackspace.com>>
Reply-To: OpenStack Dev mailto:openstack-dev@lists.openstack.org>>
Date: Monday, June 2, 2014 at 2:45 PM
To: OpenStack Dev mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [M
: Kurt Griffiths
mailto:kurt.griffi...@rackspace.com>>
Date: Tuesday, June 3, 2014 at 9:34 AM
To: OpenStack Dev
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Marconi] Adopt Spec
I think it becomes more useful the larger your team. With a smaller team it is
ea
: Malini Kamalambal
mailto:malini.kamalam...@rackspace.com>>
Reply-To: OpenStack Dev
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, June 2, 2014 at 2:45 PM
To: OpenStack Dev
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Marconi] Adopt Sp
(not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, June 2, 2014 1:33 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Marconi] Adopt Spec
I’ve been in roles
I’ve been in roles where enormous amounts of time were spent on writing specs,
and in roles where specs where non-existent. Like most things, I’ve become
convinced that success lies in moderation between the two extremes.
I think it would make sense for big specs, but I want to be careful we use
