Re: FreeBSD ports disabled for bsdforge

On Fri, Jan 12, 2024 at 5:00 PM Jamie Landeg-Jones <jamie@catflap.org> wrote:
>
> I thought it was a bit rash of them to do all that so soon (it was obvious
> that the domain hadn't expired completely, as I could see that you renewed
> it before it was returned to being "unused".)
>
> But I didn't realise it was only 6 days! Jeeze, I have many PR's that haven't
> been looked at it months!

There is a misconception that portmgr@ is in charge of going through
open unassigned PRs and committing them. But this is actually ports
committers' job.

At the same time portmgr@ often performs large infrastructure changes
that require fixing hundreds and thousands of ports before landing
them (no one likes when someone else breaks your port, right?). Each
port added to the tree places a maintainership burden not only on an
actual maintainer but also on portmgr@. This makes portmgr@ strive to
eagerly remove ports that are standing in the way of big changes when
their maintainers are lacking time to fix them. Unfortunately this
makes portmgr@ look evil in the eyes of not only maintainers but also
fellow committers.