[all][neutron][networking-bagpipe][networking-bgpvpn] Maintainers needed

Slawek Kaplonski skaplons at redhat.com
Sun Nov 24 09:49:40 UTC 2019


Thx Thomas for confirmation that You will still be able to spent some time on
this project.
And indeed Lajos offered that he can help with this project also so thanks a lot
for volunteering Lajos!

On Fri, Nov 22, 2019 at 05:45:16PM +0100, thomas.morin at orange.com wrote:
> Hi folks,
> About networking-bgpvpn project and the reference implementation in
> networking-bagpipe: while it's very true that contributors involvment has
> been lower in the past year with no feature added, the projects are I
> believe sane enough. With some help of neutron cores and other contributors
> (actually, new contributors), the project gate has been quite consistenly
> fixed to follow changes in "external factors".
> My plan as a contributor is to keep having some time for networking-bgpvpn
> and networking-bagpipe to ensure they're sane enough to release in Usuri
> with the current feature set, or more if proposals arise and there is energy
> to implement.
> And I welcome the idea of having Lajos Katona join on the project! (Thanks!)
> Best,
> -Thomas
> Slawek Kaplonski :
> > Hi,
> > 
> > Over the past couple of cycles we have noticed that new contributions and
> > maintenance efforts for networking-bagpipe and networking-bgpvpn were
> > almost non existent.
> > This impacts patches for bug fixes, new features and reviews. The Neutron
> > core team is trying to at least keep the CI of this project healthy, but we
> > don’t have enough knowledge about the details of the <stadium project name>
> > code base to review more complex patches.
> > 
> > During the PTG in Shanghai we discussed that with operators and TC members
> > during the forum session [1] and later within the Neutron team during the
> > PTG session [2].
> > 
> > During these discussions, with the help of operators and TC members, we
> > reached the conclusion that we need to have someone responsible for
> > maintaining those projects. This doesn’t mean that the
> > maintainer needs to spend full time working on those projects. Rather, we
> > need someone to be the contact person for the project, who takes care of
> > the project’s CI and review patches. Of course that’s only a minimal
> > requirement. If the new maintainer works on new features for the project,
> > it’s even better :)
> > 
> > If we don’t have any new maintainer(s) before milestone Ussuri-2, which is
> > Feb 10 - Feb 14 according to [3], we will need to mark networking-bgpvpn and
> > networking-bagpipe as deprecated and in “V” cycle we will propose to move the
> > projects from the Neutron stadium, hosted in the “openstack/“ namespace, to the
> > unofficial projects hosted in the “x/“ namespace.
> > 
> > So if You are using this project now, or if You have customers who are
> > using it, please consider the possibility of maintaining it.  Otherwise,
> > please be aware that it is highly possible that the project will be
> > deprecated and moved out from the official OpenStack projects.
> > 
> > [1]
> > https://etherpad.openstack.org/p/PVG-Neutron-stadium-projects-the-path-forward
> > [2] https://etherpad.openstack.org/p/Shanghai-Neutron-Planning-restored -
> > Lines 379-421
> > [3] https://releases.openstack.org/ussuri/schedule.html
> > 
> _________________________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.

Slawek Kaplonski
Senior software engineer
Red Hat

More information about the openstack-discuss mailing list