Re: [openstack-dev] [cross-project] What are specifications?
On 12:12 Mar 23, Thierry Carrez wrote: > Keeping both using the same template, in the same directories and the same > repositories is what created this grey area that paved the way for specs > without assignees and best practices asking for cross-project consensus that > they will never fully obtain. > > I think it's time to recognize those are different things and separate them. https://review.openstack.org/#/c/296571/ -- Mike Perez __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cross-project] What are specifications?
Mike Perez wrote: [...] A proposal I would like to make: * Clarify what cross-project specifications are [5]. - I do think specifications and best practices need to exist. + Specifications feel like they're required in my opinion. I think some cross-project things like service catalog we want under here. + Best practices can be for rolling upgrades. While it's great if a project can do rolling upgrades and use our existing solutions, according to some experts there is no silver bullet to this problem. This is not the first time in the life of the cross-project efforts that the difference between best practices and specs is biting us. I think those are different things, and so far we have stored them in the same repo, which kind of dilutes the messaging around them. Best practices / guidelines are recommendations for future design. A set of documents to base your future work on. Best practices are living documents that are updated. They should not require full openstack-wide consensus, since they are just a recommendation. They might be removed when no longer relevant, but otherwise they don't expire and are never "finished". Specifications, I think, should be more about a specific implementation plan. A clear goal, a list of affected projects, steps to reach the goal and assignees to make it happen. Once approved by affected projects, they don't really change. Specs should have an end, at some point they should be considered implemented or abandoned. Keeping both using the same template, in the same directories and the same repositories is what created this grey area that paved the way for specs without assignees and best practices asking for cross-project consensus that they will never fully obtain. I think it's time to recognize those are different things and separate them. -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cross-project] What are specifications?
Hey all, Last Cross-Project meeting [1] I feel like there was some confusion around what our specifications should be used for. This mainly came up because of the rolling upgrade specification [2]. I want to clarify that this document exists as an incomplete specification that was contributed by the product working group. The product working group's goal is to capture use cases. Some of the use cases were seen as just a wish list, which is fair. Originally I was hoping what the working group captured would reflect what different projects are already doing today, not new proposals. I think this document needs to be updated to be more accurate of that. My takeaway from the discussion in the meeting of the people that are experts in this area is there is no one magic solution to this problem. However, if we want to capture best practices with things like RPC versioning and other problems a project might want to solve in this area, that's fine. Best practices is nothing new in the cross-project specifications [3] repo. Same goes for guidelines [4]. What's confusing and what fungi has brought to my attention is the word "specification". A proposal I would like to make: * Clarify what cross-project specifications are [5]. - I do think specifications and best practices need to exist. + Specifications feel like they're required in my opinion. I think some cross-project things like service catalog we want under here. + Best practices can be for rolling upgrades. While it's great if a project can do rolling upgrades and use our existing solutions, according to some experts there is no silver bullet to this problem. I'm not sure why we need guidelines as well. What do others think? [1] - http://eavesdrop.openstack.org/meetings/crossproject/2016/crossproject.2016-03-15-21.01.log.html#l-259 [2] - https://review.openstack.org/#/c/290977/ [3] - http://specs.openstack.org/openstack/openstack-specs/specs/eventlet-best-practices.html [4] - http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html [5] - https://review.openstack.org/#/c/295940/ -- Mike Perez __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
