Date: Thu, 30 Jan 2003 01:19:42 -0800 (PST) From: Doug Barton <DougB@FreeBSD.org> To: La Temperanza <temperanza@softhome.net> Cc: chat@FreeBSD.org Subject: Re: About the ports bureaucracy Message-ID: <20030130011315.U341@12-234-22-23.pyvrag.nggov.pbz> In-Reply-To: <20030129214749.5a71f32b.temperanza@softhome.net> References: <20030129214749.5a71f32b.temperanza@softhome.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Having been in the position you're in now, I can sympathize with what
you're saying, and no, I'm not offended. :)
On Wed, 29 Jan 2003, La Temperanza wrote:
> I've noticed for a while that many PRs in the ports section, particulary
> involving lesser-used applications, seem to sit around for months and
> months. These include maintainer updates and unbreakage patches, so I
> don't think I'm just looking at the incorrectly done or low-priority
> ones in the lot. I figured the most flattering explanation for this
> happening is that the ports committers are simply overwhelmed by the
> number of PRs and concentrate their efforts on the most important ones.
I think you're partially correct. I maintain a small number of ports,
basically ports that I use myself, either at home or work. I used to try
and close ports PR's when time allowed, but recently time has not allowed.
When looking at PR's to close I prioritized those that were easy to
install (not too many dependencies that I don't already have, etc.); and
easy to test. There are therefore a LOT of ports PR's that I won't touch
with a 10' pole. Not because I don't think they are important, but because
it's simply not possible for me to devote time to them.
> I decided I'd like to help out, and sent an e-mail to the team asking
> how I could become a committer. Apparently you submit high-quality PRs
> until someone notices you and invites you to join the club. But if there
> are more PRs being submitted then they can deal with, isn't that just
> sort of silly?
I understand that it doesn't _sound_ rational, but the system works. One
thing that non-committers can do to help is to test ports PR's thoroughly,
then submit a follow-up indicating the results of your tests. This will
help committers who do have time to close random ports PR's to prioritize
those which have a higher probability of success.
Hope this helps,
Doug
--
If it's moving, encrypt it. If it's not moving, encrypt
it till it moves, then encrypt it some more.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030130011315.U341>