Paul Menzel:
> [Moving to postfix-devel]
>
> Dear Postfix folks,
>
>
> On 2017-11-01 12:08, Wietse Venema wrote:
> > Paul Menzel:
>
> >> Looking at the Postfix Web site [1], I couldn?t find any
> >> information if Postfix needs financial support to ensure the
> >> maintenance and improvement of the code.
> >
> > All that requires a non-profit that can accept funds, which just
> > takes a bit of time and money to set up (I have some experience with
> > US-based ones). Finding the time is the main thing. But yeah, it
> > needs to be done. In the mean time, an organization can donate code
> > by paying a contractor (for example, CNNIC paid for SMTPUTF8
> > support).
>
> [?]
>
> This topic came up again, and I am wondering, if the WISHLIST [1]
> could be taken as tasks for a request for quote of contractors.
The WISHLIST contains an unprioritized dump, ranging from small
items that could be implemented, tested and documented in a day,
to structural changes that might take days to weeks (replacing
hard-coded search order like {user@domain, user, @domain} with
configurable order, adding support for event-driven policies in
postscreen, finishing BURL, adding HaProxy2 and Memcache2 protocol
support, and so on). And then there is porting Postfix over to the
Google Test framework. We're talking months but something like this
is really needed to ensure that future changes will not break
existing functionality.
> Code audit/review (fuzzing, ?) could also be contracted I guess.
Setting up such scans takes real time, as does the review of their
results. But this work is safe in the sense that there is no risk
of breaking Postfix.
> I?d love to hear your ideas especially with time/cost estimates.
The sample may give you an idea. It would take a bit more time to
work out a full spec. Also, the above does not include the time
that I would spend with quality control from design to tests and
documentation.
Wietse
