Date: Fri, 12 Jan 2024 09:39:44 -0800 From: Chris <portmaster@bsdforge.com> To: Gleb Popov <arrowd@freebsd.org> Cc: Jamie Landeg-Jones <jamie@catflap.org>, freebsd-ports@freebsd.org Subject: Re: FreeBSD ports disabled for bsdforge Message-ID: <f88671942977e1773f7b3f8bb2d3b82a@bsdforge.com> In-Reply-To: <CALH631kBiCN2QsvirXq9EOG=osk0x0bwpuhPBQu0fDNxjzQ7Yg@mail.gmail.com> References: <202401111126.40BBQgJ4028906@donotpassgo.dyslexicfish.net> <4ae511b8cf4e21ecfa8b4283ea369f6f@bsdforge.com> <202401121400.40CE04P1085845@donotpassgo.dyslexicfish.net> <CALH631kBiCN2QsvirXq9EOG=osk0x0bwpuhPBQu0fDNxjzQ7Yg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2024-01-12 07:04, Gleb Popov wrote: > 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. That seems a fair theory. But IMHO wouldn't a pending DEPRECIATION have been a better plan? Just a thought. Thanks for the reply, Gleb. :) --Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f88671942977e1773f7b3f8bb2d3b82a>