[neutron][docs] networking-onos EOL?
Hi, We (kolla) had a bug report [1] from someone trying to use the neutron onos_ml2 ML2 driver for the ONOS SDN controller. As far as I can tell [2], this project hasn't been released since 2015. However, the 'latest' documentation is still accessible [3], and does not mention that the project is dead. What can we do to help steer people away from projects like this? Cheers, Mark [1] https://bugs.launchpad.net/bugs/1850763 [2] https://pypi.org/project/networking-onos/#history [3] https://docs.openstack.org/networking-onos/latest/
Hi, networking-onos project was under the neutron team governance, but it was retired in Oct 2016 [4][5]. Regarding the 'latest' documentation, there is no clear guideline on cleaning up "docs.o.o/latest/foo" when a repository is retried. I think that is the only reason we can still see docs.o.o/latest/networking-onos. Only projects under TC governance can publish documentation under docs.o.o, so I thnk we need a cleanup when a repository retirement. Thanks, Akihiro Motoki (amotoki) [4] https://review.opendev.org/#/c/383911/ (neutron team decision) [5] https://review.opendev.org/#/c/392010/ (governance change) On Mon, Nov 4, 2019 at 7:12 PM Mark Goddard <mark@stackhpc.com> wrote:
Hi,
We (kolla) had a bug report [1] from someone trying to use the neutron onos_ml2 ML2 driver for the ONOS SDN controller. As far as I can tell [2], this project hasn't been released since 2015. However, the 'latest' documentation is still accessible [3], and does not mention that the project is dead. What can we do to help steer people away from projects like this?
Cheers, Mark
[1] https://bugs.launchpad.net/bugs/1850763 [2] https://pypi.org/project/networking-onos/#history [3] https://docs.openstack.org/networking-onos/latest/
Added [infra]. On Thu, 14 Nov 2019 at 05:59, Akihiro Motoki <amotoki@gmail.com> wrote:
Hi,
networking-onos project was under the neutron team governance, but it was retired in Oct 2016 [4][5].
Regarding the 'latest' documentation, there is no clear guideline on cleaning up "docs.o.o/latest/foo" when a repository is retried. I think that is the only reason we can still see docs.o.o/latest/networking-onos. Only projects under TC governance can publish documentation under docs.o.o, so I thnk we need a cleanup when a repository retirement.
That sounds like a fair argument to me.
Thanks, Akihiro Motoki (amotoki)
[4] https://review.opendev.org/#/c/383911/ (neutron team decision) [5] https://review.opendev.org/#/c/392010/ (governance change)
On Mon, Nov 4, 2019 at 7:12 PM Mark Goddard <mark@stackhpc.com> wrote:
Hi,
We (kolla) had a bug report [1] from someone trying to use the neutron onos_ml2 ML2 driver for the ONOS SDN controller. As far as I can tell [2], this project hasn't been released since 2015. However, the 'latest' documentation is still accessible [3], and does not mention that the project is dead. What can we do to help steer people away from projects like this?
Cheers, Mark
[1] https://bugs.launchpad.net/bugs/1850763 [2] https://pypi.org/project/networking-onos/#history [3] https://docs.openstack.org/networking-onos/latest/
On 2019-11-14 09:24:11 +0000 (+0000), Mark Goddard wrote:
Added [infra]. [...]
Can you clarify why? Reading back through the thread this sounds like you either want a change to the way the main documentation redirects in the openstack-manuals repo are designed, or you want some change merged to networking-onos to replace its documentation with some indication it's retired, or you want a change to the openstackdocstheme Sphinx theme to add a banner/admonishment on docs for retired repos... or are you simply relying on the Infra team to remind people on other teams how their projects are interrelated? A more specific request/question would really help. -- Jeremy Stanley
participants (3)
-
Akihiro Motoki
-
Jeremy Stanley
-
Mark Goddard