Date: Tue, 28 Oct 1997 18:55:04 -0500 (EST) From: Tim Vanderhoek <hoek@hwcn.org> To: Ian Vaudrey <i.vaudrey@cableinet.co.uk> Cc: James Raynard <fports@jraynard.demon.co.uk>, "'Tim Vanderhoek'" <hoek@hwcn.org>, "freebsd-ports@hub.freebsd.org" <freebsd-ports@hub.freebsd.org> Subject: RE: ports/4848: New Port to add! NASM Assembler Message-ID: <Pine.GSO.3.96.971028184322.7289B-100000@james.freenet.hamilton.on.ca> In-Reply-To: <01BCE389.F0D2C1E0@nemkoltd.nildram.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Oct 1997, Ian Vaudrey wrote: > I've noticed that some ports take months to be committed, while others are > committed very quickly, sometimes on the same day they are submitted. There > seems to be no pattern to this on the surface. How *does* the system work? There isn't really any system. Someone takes a look through the pr list and sees a port which interests them, or sees one which looks like it has been waiting in line for a while, and then they review & commit. This leads to several suggestions on how to make your port look attractive: 1) If you describe it nicely -- make it sound like something _everyone_ _just_ _has_ to have. 2) The subject line should show that it is a new port that needs to be committed, and be interesting, too (I've never done this, since it's boring, but if you really want your port committed... :) 3) My personal opinion is that new ports are best submitted as an shar archive. This means that people can look over and review them when they're reading their FreeBSD-bugs mail. General agreement says that updates to existing ports should be done using recursive uni-diff. _Please_ be sure to note any new or removed files loudly. 4) If the port isn't being committed, sometimes it may help to gnats-submit an follow-up and update. This is basically an excuse to send mail to FreeBSD-bugs and have more people see that your port is waiting. Word it carefully so that the followup doesn't seem gratitous (even if it is ;) and points-out to people more reasons to commit your port. 5) echo "Hey! You jerks! Will someone review and commit my port" | mail ports@FreeBSD.ORG committers@FreeBSD.ORG. Don't do this unless it really is taking too long, or if there's an important reason to commit the port now, though. In short, the ports team loves to see the submission of new ports, even if it means there is more work for them. You shouldn't take any offence or unwelcome from the long time it takes to review and commit the ports --- that's just the way things are right now. :-( -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.971028184322.7289B-100000>