Open Stack

> -----Original Message-----
> From: Slawek Kaplonski [mailto:skaplons at redhat.com]
> Sent: Monday, January 20, 2020 2:26 PM
> To: OpenStack Discuss ML
> Subject: Re: [all][neutron][neutron-fwaas] FINAL CALL Maintainers needed
> 
> Hi,
> 
> We are getting closer and closer to Ussuri-2 milestone which is our deadline
> to deprecate neutron-fwaas project if there will be no any volunteers to
> maintain this project.
> So if You are interested in this project, please raise Your hand here or ping
> me on IRC about that.
> 
> > On 6 Jan 2020, at 21:05, Slawek Kaplonski <skaplons at redhat.com> wrote:
> >
> > Hi,
> >
> > Just as a reminder, we are still looking for maintainers who want to keep
> neutron-fwaas project alive. As it was written in my previous email, we will
> mark this project as deprecated.
> > So please reply to this email or contact me directly if You are interested in
> maintaining this project.
> >
> >> On 19 Nov 2019, at 11:26, Slawek Kaplonski <skaplons at redhat.com>
> wrote:
> >>
> >> Hi,
> >>
> >> Over the past couple of cycles we have noticed that new contributions
> and
> >> maintenance efforts for neutron-fwaas project 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 neutron-fwaas
> >> 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 project.
> >> This doesn’t mean that the maintainer needs to spend full time working
> on this
> >> project. 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 neutron-fwaas
> >> as deprecated and in “V” cycle we will propose to move the project
> >> 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
> >>
> >> --
> >> Slawek Kaplonski
> >> Senior software engineer
> >> Red Hat
> >
> > —
> > Slawek Kaplonski
> > Senior software engineer
> > Red Hat
> >
> 
> —
> Slawek Kaplonski
> Senior software engineer
> Red Hat
> 
> 

I'm not a developer, rather an operator.  I just thought I'd ask if the OpenStack community had thought about creating a fund for developers that may want to contribute, but can only do it for a fee.  Essentially a donation bucket.  I don't know if the OpenStack Foundation does this or not already.  There may be adequate need for fwaas, for example, but not enough volunteer resources to do it.  However there may be money in multiple operators' budgets that can be used to donate to the support of a project.

Eric