Re: Is commoncpp and ucommon still being maintained?

[Jeffrey Walton]

On Wed, Jul 22, 2020 at 9:56 AM Jeffrey Walton <noloader@gmail.com> wrote:
> On Wed, Jul 22, 2020 at 9:45 AM Stefano Canepa <sc@linux.it> wrote:
> > On Wed, 2020-07-22 at 09:25 -0400, Jeffrey Walton wrote:
> > > Hello,
> > >
> > > Is commoncpp and ucommon still being maintained?
> > > ...
> > as far as I know they are not maintained any more. I made commoncpp
> > compiling on latest g++ as someone asked an share the resulting
> > tarball, I was about to publish my changes on gitlab but I don't have
> > intention to maintain it.
>
> Thanks Stefano.
>
> Yeah, I got that impression, too.
>
> I've got some OpenSSL 1.1.x patches here if you need them:
> https://github.com/noloader/Build-Scripts/blob/master/patch/ucommon.patch.
>
> So it looks like there are at least 5 mini-forks going on. It includes
> you, me, Debian, Gentoo and MacPorts. That is bad from a security
> engineering standpoint. The Maven insecurity problem has sprouted
> multiple heads.

Unfortunately I was not able to get access to the source code to
check-in my changes. The changes include fixes for libcommoncpp and
SIP Witch. Aymeric Moizard was very helpful with integration with the
updated libeXosip2.

The FSF just stonewalled me. There does not appear to be genuine
interest in accepting the updates. About all they did was drag the
process due to indecision.

I'm washing my hands of it.

The best I can tell FSF does not have processes in place to account
for an absentee maintainer who has abandoned his/her duties. Or they
don't have a process in place for a temporary maintainer to check-in
updates for an abandoned project.

Jeff