Re: [openstack-dev] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref
On 2018-01-15 16:11, Stephen Finucane wrote:
> On Thu, 2018-01-04 at 15:39 +, Stephen Finucane wrote:
>> 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?
>
> It's been two weeks with no -1s, so we've gone ahead and done this.
> Thanks, everyone.
Note that the ownership is already in government repo since May 2016
(https://review.openstack.org/317686),
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
__
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] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref
On Thu, 2018-01-04 at 15:39 +, Stephen Finucane wrote: > 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? It's been two weeks with no -1s, so we've gone ahead and done this. Thanks, everyone. Stephen > Stephen > > PS: I'm not sure how this affects things from a release management > perspective. Are there PTLs for these sorts of projects? Turns out this project was already listed as a doc team deliverable. Who knew?! > [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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref
On Thu, 4 Jan 2018 16:06:53 + Graham Hayes wrote: > On 04/01/18 15:39, Stephen Finucane wrote: > > 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? > > No objection from me > > > Stephen > > > > PS: I'm not sure how this affects things from a release management > > perspective. Are there PTLs for these sorts of projects? > > It does seem like a docs tooling thing, so maybe moving it to the docs > project umbrella might be an idea? What we do for other projects under that umbrella (such as contributor-guide) is that we add openstack-doc-core as a group member, as Stephen mentioned. This allows for other contributors to become cores even if they are not interested in other aspects of the docs team's work. But I'm fine with whatever works for the current cores. Thanks, pk __ 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] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref
On 04/01/18 15:39, Stephen Finucane wrote: > 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? No objection from me > Stephen > > PS: I'm not sure how this affects things from a release management > perspective. Are there PTLs for these sorts of projects? It does seem like a docs tooling thing, so maybe moving it to the docs project umbrella might be an idea? > [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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > signature.asc Description: OpenPGP digital signature __ 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] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref
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: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
