[openstack-dev] [api] Next meeting agenda
rybrown at redhat.com
Thu Jan 29 15:29:25 UTC 2015
On 01/29/2015 10:20 AM, Sean Dague wrote:
> On 01/29/2015 07:17 AM, Anne Gentle wrote:
>> On Thu, Jan 29, 2015 at 4:10 AM, Thierry Carrez <thierry at openstack.org
>> <mailto:thierry at openstack.org>> wrote:
>> Everett Toews wrote:
>> > A couple of important topics came up as a result of attending the
>> > Cross Project Meeting. I’ve added both to the agenda for the next
>> > meeting on Thursday 2015/01/29 at 16:00 UTC.
>> > https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda
>> > The first is the suggestion from ttx to consider using
>> > openstack-specs  for the API guidelines.
>> Precision: my suggestion was to keep the api-wg repository for the
>> various drafting stages, and move to openstack-specs when it's ready to
>> be "recommended" and request wider community comments. Think Draft and
>> RFC stages in the IETF process :)
>> Oh, thanks for clarifying, I hadn't understood it that way.
>> To me, it seems more efficient to get votes and iterate in one repo
>> rather than going through two iterations and two review groups. What do
>> others think?
> Honestly, I'm more a fan of the one repository approach. Jumping
> repositories means the history gets lost, and you have to restart a
> bunch of conversations. That happened in the logging jump from nova ->
> openstack-specs, which probably created 3 - 4 months additional delay in
> the process.
+1 for single repo, commits aren't as important for specs as unifying
discussion around them.
I think a spec being merged/unmerged is a good enough distinction for
the draft status of a spec and wouldn't be improved by having a
draft/final repo split.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Ryan Brown / Software Engineer, Openstack / Red Hat, Inc.
More information about the OpenStack-dev