[infra][neutron] Removing networking-calico from OpenStack governance
Hi all, networking-calico is the code that integrates Project Calico [1] with Neutron. It has been an OpenStack project for several years, but we, i.e. its developers [2], would like now to remove it from OpenStack governance and instead manage it like the other Project Calico projects under https://github.com/projectcalico/. In case anyone has any concerns about this, please let me know very soon! Please could infra folk confirm that https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project is the correct procedure for winding up the OpenStack side of this transition? Many thanks, Neil [1] https://www.projectcalico.org/ [2] That means mostly me, with some help from my colleagues here at Tigera. We do have some other contributors but I will take care that they are also on board with this change.
On 2020-02-10 19:16:22 +0000 (+0000), Neil Jerram wrote: [...]
Please could infra folk confirm that https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project is the correct procedure for winding up the OpenStack side of this transition? [...]
Yes, that's our recommended procedure for closing down development on a repository in the OpenDev infrastructure. Make sure your README.rst in step 3 includes a reference to the new location for the benefit of folks who arrive at the old copy. -- Jeremy Stanley
what impact on users of this code do you foresee? What are the reasons to remove it from openstack governance? On Mon, Feb 10, 2020 at 2:24 PM Neil Jerram <neil@tigera.io> wrote:
Hi all,
networking-calico is the code that integrates Project Calico [1] with Neutron. It has been an OpenStack project for several years, but we, i.e. its developers [2], would like now to remove it from OpenStack governance and instead manage it like the other Project Calico projects under https://github.com/projectcalico/.
In case anyone has any concerns about this, please let me know very soon!
Please could infra folk confirm that https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project is the correct procedure for winding up the OpenStack side of this transition?
Many thanks, Neil
[1] https://www.projectcalico.org/ [2] That means mostly me, with some help from my colleagues here at Tigera. We do have some other contributors but I will take care that they are also on board with this change.
-- Chris Morgan <mihalis68@gmail.com>
On Mon, Feb 10, 2020 at 7:54 PM Chris Morgan <mihalis68@gmail.com> wrote:
what impact on users of this code do you foresee? What are the reasons to remove it from openstack governance?
Thanks for asking. I would say somewhat easier maintenance and feature velocity (when needed), as the development processes will be aligned with those of other Calico/Tigera components. But please be assured that networking-calico and Calico for OpenStack will continue to be maintained and developed. Just with a different set of (still open) processes. Best wishes, Neil
Actually, it looks like it's been officially removed from Neutron since Ocata, when https://review.openstack.org/399320 merged (so nearly 3.5 years already). As such it's just the code hosting which needs to be retired, and there doesn't seem to be any governance follow-up needed. -- Jeremy Stanley
On Mon, Feb 10, 2020 at 8:11 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
Actually, it looks like it's been officially removed from Neutron since Ocata, when https://review.openstack.org/399320 merged (so nearly 3.5 years already). As such it's just the code hosting which needs to be retired, and there doesn't seem to be any governance follow-up needed.
Thanks Jeremy, yes, that's correct, networking-calico has been a 'big tent' project but not 'Neutron stadium' for the last few years. I'll take care to leave a good pointer in the README.rst, as you advised. Best wishes, Neil
On Mon, Feb 10, 2020 at 9:32 PM Neil Jerram <neil@tigera.io> wrote:
On Mon, Feb 10, 2020 at 8:11 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
Actually, it looks like it's been officially removed from Neutron since Ocata, when https://review.openstack.org/399320 merged (so nearly 3.5 years already). As such it's just the code hosting which needs to be retired, and there doesn't seem to be any governance follow-up needed.
Thanks Jeremy, yes, that's correct, networking-calico has been a 'big tent' project but not 'Neutron stadium' for the last few years.
I'll take care to leave a good pointer in the README.rst, as you advised.
FYI the project-config change is up at https://review.opendev.org/#/c/707086/. (There isn't any mention of "networking-calico" in the requirements repo, so that step was a no-op.) Neil
participants (3)
-
Chris Morgan
-
Jeremy Stanley
-
Neil Jerram