Date: Sat, 26 Nov 2005 11:05:44 +0100 From: Simon Barner <barner@FreeBSD.org> To: Matt Crossley <moose@freebsdfreaks.net> Cc: freebsd-ports@freebsd.org Subject: Re: Question about Port maintainership Message-ID: <20051126100544.GA1599@zi025.glh.mhn.de> In-Reply-To: <438751FD.3000603@freebsdfreaks.net> References: <438751FD.3000603@freebsdfreaks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Matt Crossley wrote: > Hi all, >=20 > A couple of questions regarding port maintainership, etc. >=20 >=20 > There is a port that I recently needed to install that I haven't used in > quite some time (sysutils/autopsy). The port is quite outdated, and > hasn't been updated since March, 2004. The version is at 1.73, whereas > the actual application itself is up to Version 2.06, released in > October, 2005. >=20 > I've sent the current maintainer an email asking if either he'd update > the port, or if I could take over maintainership and do regular updates > on the port. That was about 3 weeks ago, and I have heard no response > from him. What should be my next step? Should I make a patch to update > the Makefile and submit a PR? Or submit a change maintainer PR? I don't > want ot step on anyone's toes, but it's been over a year since an update > by the maintainer, and I'd like to pick up the slack. Please file a PR with the update, then we can track it and update the port via maintainer update (2 weeks) and - if necessary - reset an unresponsive maintainer (3 months). >=20 > My next question has to do with an application that I think would be > useful, but is not in the ports tree. It is a commercial, proprietary > product that is free for download, without having to click and agreement > or accept a EULA. I'd like to add this port, and I've contacted the > company in question (over 1 week ago), but they have not responded yet. > So I'm wondering what the policy is regarding adding ports where the > developer or company has not explicitly approved this addition to the > ports system. In many respects, it would be beneficial for them to have > more exposure, but maybe they wouldn't appreciate it for some reason? > Any guidelines there? If you are unsure, please mark the port as RESTRICTED, so it will not appear on CDROMs or FreeBSD FTP servers. In any case, mention the your concerns in the PR when you submit the port. >=20 > I've started to go through the Porter's Handbook, and I'm looking > forward to being able to make contributions, as minor as they are, to > the growth of FreeBSD. :-) Fine :-) Be sure to follow this list, too! --=20 Best regards / Viele Gr=FC=DFe, barner@FreeBSD.= org Simon Barner barner@gmx.de --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiDN4Ckn+/eutqCoRAk5gAJ0Y1dNOxOdyIM+fGEXKFgtHITRjbACghSof RJCzVWRT2ZmnjeyckrZOvFI= =b76C -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051126100544.GA1599>