I'm not sure what the procedure for this is but here goes. I've noticed that the 'os-api-ref' project seems to have its own group of cores [1], many of whom are no longer working on OpenStack (at least, not full-time), and has a handful of open patches against it [2]. Since the doc team has recently changed its scope from writing documentation to enabling individual projects to maintain their own docs, we've become mainly responsible for projects like 'openstack-doc- theme'. Given that the 'os-api-ref' project is a Sphinx thing required for multiple OpenStack projects, it seems like something that could/should fall into the doc team's remit.
I'd like to move this project into the remit of the 'openstack-doc- core' team, by way of removing the 'os-api-ref-core' group or adding 'openstack-doc-core' to the list of included groups. In both cases, existing active cores will be retained. Do any of the existing 'os-api- ref' cores have any objections to this? Stephen PS: I'm not sure how this affects things from a release management perspective. Are there PTLs for these sorts of projects? [1] https://review.openstack.org/#/admin/groups/1391,members [2] https://review.openstack.org/#/q/project:openstack/os-api-ref+statu s:open __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
