Date: Thu, 26 May 2016 08:01:02 +0200 From: John Marino <freebsdml@marino.st> To: Kurt Jaeger <pi@FreeBSD.org>, neel@neelc.org, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: security/tor-devel and Maintainer Timeout Message-ID: <91959a4e-fe66-e979-b2b0-30e62a1de0f2@marino.st>
next in thread | raw e-mail | index | archive | help
> Hi! > > > I have posted patches for updated versions of security/tor-devel, but > > the maintainer,bf at freebsd.org > <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>; does not seem to be looking at the > > Bugzilla requests, nor are the ports being updated. > > > > A URL:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208594 > > I'll have a look at it in the next few days. Sorry for the delay. > > -- > pi at opsec.eu <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>; +49 171 3101372 4 years to go ! That doesn't address the core issue though. As long as I have been an active committer, this has been the situation with bf@ and his ports. I think one can make a good argument that many of the ports for which he is listed as maintainer have suffered by this and would have been better off to be "unmaintained" and the more useful one would have been adopted anyway. Life happens. bf@ used to be very active but he hasn't been in years, and frankly I think he should consider releasing all his ports. He can still commit to the ports tree, but just without the obligation (and the point is that he's not meeting those obligations). Port manager should approach bf@ about this because in my humble opinion, the situation has been not good for years now. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91959a4e-fe66-e979-b2b0-30e62a1de0f2>