From owner-freebsd-ports@FreeBSD.ORG Tue Apr 10 11:45:46 2012 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC4EE106566B; Tue, 10 Apr 2012 11:45:46 +0000 (UTC) (envelope-from culot@0xd0.org) Received: from 0xd0.org (0xd0.org [91.121.92.146]) by mx1.freebsd.org (Postfix) with ESMTP id 30D5C8FC08; Tue, 10 Apr 2012 11:45:45 +0000 (UTC) Received: from 0xd0.org (doudou.0xd0.org [172.16.0.254]) by 0xd0.org (8.14.4/8.14.4) with ESMTP id q3ABjcPc061314; Tue, 10 Apr 2012 13:45:38 +0200 (CEST) (envelope-from culot@0xd0.org) Received: (from culot@localhost) by 0xd0.org (8.14.4/8.14.4/Submit) id q3ABjcI9061313; Tue, 10 Apr 2012 13:45:38 +0200 (CEST) (envelope-from culot) Date: Tue, 10 Apr 2012 13:45:38 +0200 From: Frederic Culot To: Pietro Cerutti Message-ID: <20120410114537.GL17460@culot.org> References: <201204092351.q39Npi6F025202@repoman.freebsd.org> <20120410091537.GK98668@gahrfit.gahr.ch> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="z6Eq5LdranGa6ru8" Content-Disposition: inline In-Reply-To: <20120410091537.GK98668@gahrfit.gahr.ch> X-PGP-Key: http://culot.org/public/pgp-key.txt User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, cvs-ports@FreeBSD.org, bapt@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-clx-sbcl Makefile ports/palm/coldsync ... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 11:45:46 -0000 --z6Eq5LdranGa6ru8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > I have strong opinions against this, at least for ports with an active > maintainer. I really see these deprecation campaigns as treading on > somebody's toes. >=20 > I really like linimon's periodic emails "FreeBSD ports that you maintain > which are currently marked broken", which I see as a reminder that there > are ports of mine that require action, but going further than that and > deprecate a port that I maintain without even informing me in an > official way is not what I consider collaboration. >=20 > Even more so because I don't see any advantage in moving a port from > BROKEN to DEPRECATED state. If a user has a working version of the port > installed, he will stick to that, otherwise, installation will be frown > upon anyway. >=20 > I and bapt have already exchanged opinions on this subject more than > once, and I would now like to see what other people (other maintainers > in particular) think about it. >=20 > Can we please stop this? >=20 > --=20 > Pietro Cerutti > The FreeBSD Project > gahr@FreeBSD.org >=20 > PGP Public Key: > http://gahr.ch/pgp As you inquire people's opinion, I would say that I find this way of procee= ding a bit pushy and I consider it a good example of closed communication as I f= ind it: - non-caring: such a commit is a detached and impersonal way to give the information to a maintainer that has not unbroken his port for a long time - dogmatic: it looks like an unwillingness to accept the maintainer's point= of view or at least to hear about his work on maintaining the port - superior: deprecating without prior communication with the maintainer str= esses differences in status between portmgr/committer and maintainers Hence I am not surprised when you say you feel someone is treading on your = toes, and more generally I fear this does not do any good to maintainer's motivat= ion and commitment to the project. On the other hand I also believe those deprecation actions are necessary an= d I thank bapt for his work on this. To conciliate such a necessary action without hurting the feelings of those maintainers who despite their work could not update the state of their port= in a timely manner, maybe it would be good to be more verbose in the log of such commits. Inspired by linimon's emails, something like the following could be added: "As part of an ongoing effort to reduce the number of problems in the FreeB= SD ports system, we periodically schedule removal of ports that have been mark= ed as broken for a period of at least six months. As a maintainer of one of those ports, feel free to remove the deprecate status if you need more time to fi= x the breakage and do not hesitate to contact portmgr@ if you need additional information on this policy." I hope this brings something to the discussion. -- Frederic Culot culot@FreeBSD.org --z6Eq5LdranGa6ru8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk+EHVsACgkQtzkaJjSHbFu0TACdEziSdBWtqmxJQEMOjBBJNijL 2pUAoKGsLGWbWpz1ZsAJn66qTreF67fw =0pa5 -----END PGP SIGNATURE----- --z6Eq5LdranGa6ru8--