Greetings.
As noted in https://communityblog.fedoraproject.org/application-service-categories-and-community-handoff/ Fedora infrastructure isn't in a happy place with mailman3/hyperkitty.
However, since mailman3 / hyperkitty is now packaged in Fedora, we would like to look at moving it to a category 2 application, ie We run it, but we don't maintain it. This will require some work to move from the current rhel7 instance to a new fedora instance, but should hopefully be not too much work. At that point we will run the service as we do now, but will push any bugs/enhancements to upstream to work on.
Before we start planning this move, I'd like to check in with the council and make sure we aren't stepping in the middle of other plans (ie, moving everything to discourse, or outsourcing mailing lists, etc).
Ideally I'd like an answer soon so we can move our planning ahead and get our current install retired sooner rather than later.
Happy to provide more info or the like. Thanks.
We don't have any plans to move everything to Discourse. As for outsourcing, I think having CPE run mailing lists is preferable to paying someone else to do it, but I would leave that decision to CPE.
If you're willing to put it in category 2, I am +1 to that.
At one time, aiui, the CPE team contained all of the primary maintainers for hyperkitty and possibly significant ones for mailman3. Are these two upstreams now viable in the absence of support from the CPE team?
It seems like https://gitlab.com/mailman/hyperkitty/commits/master has non-CPE activity. It's not what I might call "bustling" but it doesn't seem dead, either.
@kevin, the Council agrees we won't pull the rug out from underneath you. Proceed with the most appropriate course of action.
Metadata Update from @bcotton: - Issue close_status updated to: resolved - Issue status updated to: Closed (was: Open)
Thanks! Yes, while CPE isn't very active upstream anymore, there are folks working on it.
Login to comment on this ticket.