On Mon, Aug 31, 2020 at 9:05 pm, Adenilson Cavalcanti
My recommendation today is to just use Chromium's zlib directly
that won't require maintaining patches and you will keep in sync with
future optimizations and security fixes.
I recall watching one of your presentations on your zlib optimizations
at the Web Engines Hackfest three years ago. I was wondering then why
your improvements were not accepted upstream... well, I see now that
upstream has no commits since January 2017 , and that pull requests
there are not receiving any response from upstream, much less a review.
 seems to indicate that you eventually managed to get in touch with
upstream? But I also see at that you attempted to post patches there a
month later, and still didn't receive any response. So it seems clear
that current upstream is gone.
I don't think switching to Chromium's zlib  is a very practical
option, though, since your source repo appears to be the Chromium
source repo, since it uses gn build system, since there do not appear
to be releases independent of Chromium, and since it does not appear to
be maintained with the expectation that it will be installed as an
ABI-stable systemwide shared library.
Do you have any opinion on zlib-ng ? If nothing else, it appears to
be easier to contribute to.
Whatever we choose to do for Fedora, let's coordinate with Debian as
well so that we have a standard solution for all distros, rather than
winding up with different forks of zlib in different distros.