Hi, I think a good start would be to import the past amavisd-new releases into Github / Gitlab and start collecting issues and pull requests for bugfixes. Not really merge them or even do a new release (which is a fork needing manpower and coordination to avoid fragmentation), but as a central point for known defects and patches floating around on the mailing list.
If no one steps up I can do this. Bernhard > Am 07.10.2018 um 11:11 schrieb Giovanni Bechis <[email protected]>: > > Ralph Seichter <[email protected]> wrote: >>> On 07.10.18 00:26, Giovanni Bechis wrote: >>> >>> I think that if Mark Martinek is not maintaining any more the >>> community should step up and fork the project. >> >> Are you volunteering? I've made some local modifications over time, but >> amavisd-new with its >35000 lines of monolithic Perl is not something >> I would fork. If there is no more active development (I still hope there >> is), I doubt that reviving amavisd-new, now that two years have gone by, >> would be a good idea. >> > IMHO amavisd installations number make this software too "big" to be killed. > If noone is maintaining this project somebody will have to take it, if > there is no future maybe importing it as an Apache project could be a good > start. > Giovanni >
