Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
> can't speak regarding ceilometer-powervm since it's vendor specific. I can confirm that ceilometer-powervm (and nova-powervm and networking-powervm) shouldn't be tracked with this effort, since they publish to readthedocs and not docs.openstack.org. Something something Big Tent something Governance something something Official. efried . __ 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] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
On 11/07/17 10:43 AM, Doug Hellmann wrote: > Excerpts from gordon chung's message of 2017-07-11 14:23:41 +: >> >> On 10/07/17 01:26 PM, Doug Hellmann wrote: >>> openstack/ceilometer-powervm >>> openstack/ceilometermiddleware >> >> i don't believe there are docs for these. ceilometermiddleware is a >> simple wsgi middleware and it's usage is part of ceilometer's install >> docs. ceilometer-powervm contains the powervm driver for ceilometer's >> polling agent. > > I've removed them from the tracking list for now, but it seems like > both are likely to have contributor documentation, at least, and > the driver would likely have installation and configuration docs, > right? can't speak regarding ceilometer-powervm since it's vendor specific. ceilometermiddleware is admittedly purely maintenance mode for last few cycles so i'm going to say realistically, it's very very low priority for anyone to actually follow through with contributor docs for it. > >> >> i missed this but how do we handle smaller add-on type repos like this? >> i imagine we want to keep docs grouped by project so they are not >> scattered across the same level. >> >> cheers, >> > > The new "rule" for docs is "The documentation for something should > live in the same repository as the code." > > Hyperlinks are easy and free, so we can use those to ensure that the > results are easy to find. We're building up a nice set of landing pages > for "all of the admin guides" and "all of the configuration references" > and so on within the openstack-manuals repository. > ok, sounds good to me. -- gord __ 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] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
Excerpts from Akihiro Motoki's message of 2017-07-11 23:56:30 +0900: > Thanks for update the status! > > > openstack/networking-midonet > > The doc-migration work networking-midonet has almost completed. > Unfortunately they do not use 'doc-migration' topic as it seems they > already started > the document overhaul before the doc-migration starts. > https://review.openstack.org/#/q/topic:bug/1692788 > Hopefully midonet folks use 'doc-migration' tag for at least one patch. OK, that's good to know. > > > openstack/networking-vsphere > > This is not a project under the TC governance. I have removed it from the list. Thanks, Doug > > Akihiro > > 2017-07-11 2:26 GMT+09:00 Doug Hellmann: > > According to the dashboard, it looks like we still have almost 100 > > repositories with documentation that have no patches with the > > doc-migration topic, indicating that they have not started moving > > content or updating the theme. I have tried to tag those teams in the > > subject, but I may have missed some. Please check the list below for a > > repo owned by your team. > > > > If you have completed the work and the dasbhoard script didn't pick > > it up, please let me know so I can fix up the data. > > > > Doug > > > > openstack-dev/heat-cfnclient > > openstack/bifrost > > openstack/ceilometer-powervm > > openstack/ceilometermiddleware > > openstack/diskimage-builder > > openstack/dragonflow > > openstack/freezer-api > > openstack/freezer-dr > > openstack/freezer-web-ui > > openstack/fuxi > > openstack/fuxi-kubernetes > > openstack/heat > > openstack/heat-cfntools > > openstack/heat-translator > > openstack/instack > > openstack/ironic-lib > > openstack/karbor-dashboard > > openstack/kolla-kubernetes > > openstack/manila > > openstack/manila-image-elements > > openstack/manila-ui > > openstack/mistral-dashboard > > openstack/mistral-extra > > openstack/mistral-lib > > openstack/molteniron > > openstack/monasca-statsd > > openstack/monasca-transform > > openstack/networking-hyperv > > openstack/networking-midonet > > openstack/networking-vsphere > > openstack/neutron-lbaas > > openstack/neutron-lbaas-dashboard > > openstack/octavia-dashboard > > openstack/openstack-ansible-apt_package_pinning > > openstack/openstack-ansible-ceph_client > > openstack/openstack-ansible-galera_client > > openstack/openstack-ansible-galera_server > > openstack/openstack-ansible-haproxy_server > > openstack/openstack-ansible-lxc_container_create > > openstack/openstack-ansible-lxc_hosts > > openstack/openstack-ansible-memcached_server > > openstack/openstack-ansible-openstack_hosts > > openstack/openstack-ansible-openstack_openrc > > openstack/openstack-ansible-os_aodh > > openstack/openstack-ansible-os_barbican > > openstack/openstack-ansible-os_ceilometer > > openstack/openstack-ansible-os_cinder > > openstack/openstack-ansible-os_designate > > openstack/openstack-ansible-os_glance > > openstack/openstack-ansible-os_gnocchi > > openstack/openstack-ansible-os_heat > > openstack/openstack-ansible-os_horizon > > openstack/openstack-ansible-os_ironic > > openstack/openstack-ansible-os_keystone > > openstack/openstack-ansible-os_magnum > > openstack/openstack-ansible-os_molteniron > > openstack/openstack-ansible-os_neutron > > openstack/openstack-ansible-os_nova > > openstack/openstack-ansible-os_octavia > > openstack/openstack-ansible-os_rally > > openstack/openstack-ansible-os_sahara > > openstack/openstack-ansible-os_swift > > openstack/openstack-ansible-os_tempest > > openstack/openstack-ansible-os_trove > > openstack/openstack-ansible-pip_install > > openstack/openstack-ansible-plugins > > openstack/openstack-ansible-rabbitmq_server > > openstack/openstack-ansible-repo_build > > openstack/openstack-ansible-repo_server > > openstack/openstack-ansible-rsyslog_client > > openstack/openstack-ansible-rsyslog_server > > openstack/openstack-ansible-security > > openstack/os-net-config > > openstack/os-win > > openstack/osc-placement > > openstack/oslosphinx > > openstack/pycadf > > openstack/python-congressclient > > openstack/python-ironic-inspector-client > > openstack/python-manilaclient > > openstack/python-octaviaclient > > openstack/python-saharaclient > > openstack/python-tricircleclient > > openstack/python-tripleoclient > > openstack/python-vitrageclient > > openstack/python-zaqarclient > > openstack/python-zunclient > > openstack/rally > > openstack/searchlight-ui > > openstack/senlin > > openstack/storlets > > openstack/sushy > > openstack/sushy-tools > > openstack/tosca-parser > > openstack/virtualbmc > > openstack/watcher-dashboard > > openstack/yaql > > openstack/zun > > > > __ > > 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] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
On 2017-07-11 23:56:30 +0900 (+0900), Akihiro Motoki wrote: > 2017-07-11 2:26 GMT+09:00 Doug Hellmann: [...] > > openstack/networking-vsphere [...] > This is not a project under the TC governance. And as such, also seems to correctly not be publishing any documentation on docs.openstack.org so should be unaffected. -- Jeremy Stanley signature.asc Description: 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
Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
Thanks for update the status! > openstack/networking-midonet The doc-migration work networking-midonet has almost completed. Unfortunately they do not use 'doc-migration' topic as it seems they already started the document overhaul before the doc-migration starts. https://review.openstack.org/#/q/topic:bug/1692788 Hopefully midonet folks use 'doc-migration' tag for at least one patch. > openstack/networking-vsphere This is not a project under the TC governance. Akihiro 2017-07-11 2:26 GMT+09:00 Doug Hellmann: > According to the dashboard, it looks like we still have almost 100 > repositories with documentation that have no patches with the > doc-migration topic, indicating that they have not started moving > content or updating the theme. I have tried to tag those teams in the > subject, but I may have missed some. Please check the list below for a > repo owned by your team. > > If you have completed the work and the dasbhoard script didn't pick > it up, please let me know so I can fix up the data. > > Doug > > openstack-dev/heat-cfnclient > openstack/bifrost > openstack/ceilometer-powervm > openstack/ceilometermiddleware > openstack/diskimage-builder > openstack/dragonflow > openstack/freezer-api > openstack/freezer-dr > openstack/freezer-web-ui > openstack/fuxi > openstack/fuxi-kubernetes > openstack/heat > openstack/heat-cfntools > openstack/heat-translator > openstack/instack > openstack/ironic-lib > openstack/karbor-dashboard > openstack/kolla-kubernetes > openstack/manila > openstack/manila-image-elements > openstack/manila-ui > openstack/mistral-dashboard > openstack/mistral-extra > openstack/mistral-lib > openstack/molteniron > openstack/monasca-statsd > openstack/monasca-transform > openstack/networking-hyperv > openstack/networking-midonet > openstack/networking-vsphere > openstack/neutron-lbaas > openstack/neutron-lbaas-dashboard > openstack/octavia-dashboard > openstack/openstack-ansible-apt_package_pinning > openstack/openstack-ansible-ceph_client > openstack/openstack-ansible-galera_client > openstack/openstack-ansible-galera_server > openstack/openstack-ansible-haproxy_server > openstack/openstack-ansible-lxc_container_create > openstack/openstack-ansible-lxc_hosts > openstack/openstack-ansible-memcached_server > openstack/openstack-ansible-openstack_hosts > openstack/openstack-ansible-openstack_openrc > openstack/openstack-ansible-os_aodh > openstack/openstack-ansible-os_barbican > openstack/openstack-ansible-os_ceilometer > openstack/openstack-ansible-os_cinder > openstack/openstack-ansible-os_designate > openstack/openstack-ansible-os_glance > openstack/openstack-ansible-os_gnocchi > openstack/openstack-ansible-os_heat > openstack/openstack-ansible-os_horizon > openstack/openstack-ansible-os_ironic > openstack/openstack-ansible-os_keystone > openstack/openstack-ansible-os_magnum > openstack/openstack-ansible-os_molteniron > openstack/openstack-ansible-os_neutron > openstack/openstack-ansible-os_nova > openstack/openstack-ansible-os_octavia > openstack/openstack-ansible-os_rally > openstack/openstack-ansible-os_sahara > openstack/openstack-ansible-os_swift > openstack/openstack-ansible-os_tempest > openstack/openstack-ansible-os_trove > openstack/openstack-ansible-pip_install > openstack/openstack-ansible-plugins > openstack/openstack-ansible-rabbitmq_server > openstack/openstack-ansible-repo_build > openstack/openstack-ansible-repo_server > openstack/openstack-ansible-rsyslog_client > openstack/openstack-ansible-rsyslog_server > openstack/openstack-ansible-security > openstack/os-net-config > openstack/os-win > openstack/osc-placement > openstack/oslosphinx > openstack/pycadf > openstack/python-congressclient > openstack/python-ironic-inspector-client > openstack/python-manilaclient > openstack/python-octaviaclient > openstack/python-saharaclient > openstack/python-tricircleclient > openstack/python-tripleoclient > openstack/python-vitrageclient > openstack/python-zaqarclient > openstack/python-zunclient > openstack/rally > openstack/searchlight-ui > openstack/senlin > openstack/storlets > openstack/sushy > openstack/sushy-tools > openstack/tosca-parser > openstack/virtualbmc > openstack/watcher-dashboard > openstack/yaql > openstack/zun > > __ > 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 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] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
Excerpts from gordon chung's message of 2017-07-11 14:23:41 +: > > On 10/07/17 01:26 PM, Doug Hellmann wrote: > > openstack/ceilometer-powervm > > openstack/ceilometermiddleware > > i don't believe there are docs for these. ceilometermiddleware is a > simple wsgi middleware and it's usage is part of ceilometer's install > docs. ceilometer-powervm contains the powervm driver for ceilometer's > polling agent. I've removed them from the tracking list for now, but it seems like both are likely to have contributor documentation, at least, and the driver would likely have installation and configuration docs, right? > > i missed this but how do we handle smaller add-on type repos like this? > i imagine we want to keep docs grouped by project so they are not > scattered across the same level. > > cheers, > The new "rule" for docs is "The documentation for something should live in the same repository as the code." Hyperlinks are easy and free, so we can use those to ensure that the results are easy to find. We're building up a nice set of landing pages for "all of the admin guides" and "all of the configuration references" and so on within the openstack-manuals repository. Doug __ 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] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
Excerpts from Renat Akhmerov's message of 2017-07-11 12:08:23 +0700: > On 11 Jul 2017, 00:27 +0700, wrote: > > > openstack/mistral-dashboard > > openstack/mistral-extra > > These two are not supposed to have docs at all. We should probably just > remove the “doc” folder and corresponding CI jobs. OK, I removed them from the list of repos we are tracking. > > > openstack/mistral-lib > > This should be taken care of soon. Thanks! __ 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] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
On 10/07/17 01:26 PM, Doug Hellmann wrote: > openstack/ceilometer-powervm > openstack/ceilometermiddleware i don't believe there are docs for these. ceilometermiddleware is a simple wsgi middleware and it's usage is part of ceilometer's install docs. ceilometer-powervm contains the powervm driver for ceilometer's polling agent. i missed this but how do we handle smaller add-on type repos like this? i imagine we want to keep docs grouped by project so they are not scattered across the same level. cheers, -- gord __ 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] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta
On 11 Jul 2017, 00:27 +0700, wrote: > openstack/mistral-dashboard > openstack/mistral-extra These two are not supposed to have docs at all. We should probably just remove the “doc” folder and corresponding CI jobs. > openstack/mistral-lib This should be taken care of soon. Renat Akhmerov @Nokia __ 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