To add to that, I am currently in the process of adding the driver docs policy guidelines to the Contributor Guide: https://review.openstack.org/#/c/404785/
From: Anne Gentle <annegen...@justwriteclick.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Wednesday, November 30, 2016 at 3:12 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers On Tue, Nov 29, 2016 at 2:53 PM, Jeremy Stanley <fu...@yuggoth.org<mailto:fu...@yuggoth.org>> wrote: On 2016-11-29 20:19:13 +0000 (+0000), gordon chung wrote: [...] > i don't recall why they were moved to be officially under the Telemetry > umbrella[3] but i remember they weren't allowed to do something if they > weren't part of an 'official' project. if i could remember what it was > this paragraph would be a lot more useful. [...] Perhaps they wanted to publish documentation to the docs.openstack.org<http://docs.openstack.org> site? That's traditionally only been allowed by the Docs team for official project deliverables. This is a false statement for driver docs. We have had a proprietary driver docs policy [1] in place since 2015, which we collaborated on with driver maintainers, wrote it down, and communicated broadly. The summary is "If a vendor wants full documentation in the Configuration Reference, they have to add to the wiki page a contact editor that will take care of the vendor driver documentation. The Documentation team will assign bugs to the contact person, include the contact person in reviews for the vendor driver, and expects timely responses." The way I see it, soft white, understanding that "level playing field" is not exactly the end-goal for OpenStack but that great, tested and functional features are, is a compelling way forward. We need accountability, and I do think drivers are important and teams should find ways to enable that work in meaningful ways while also not overwhelming the common. Believe me the docs team has lived this and empathizes with the concerns. Anne 1. https://specs.openstack.org/openstack/docs-specs/specs/kilo/move-driver-docs.html -- Jeremy Stanley __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Anne Gentle www.justwriteclick.com<http://www.justwriteclick.com>
__________________________________________________________________________ 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
