docs/80681: articles/problem-reports: don't tell people they should sumbit a PR each time they see an outdated port

[David Adam]

The following reply was made to PR docs/80681; it has been noted by GNATS.

From: David Adam <zanchey at ucc.gu.uwa.edu.au>
To: Ion-Mihai Tetcu <itetcu at people.tecnik93.com>
Cc: FreeBSD gnats submit <FreeBSD-gnats-submit at FreeBSD.org>,
	freebsd-doc at FreeBSD.org
Subject: Re: docs/80681: articles/problem-reports: don't tell people they
 should sumbit a PR each time they see an outdated port
Date: Sat, 7 May 2005 15:10:12 +0800 (WST)

 > > Why not just "If you are reporting a new version of a port, try to contact
 > > the port's maintainer first."?
 >
 > So that I don't see PR but post on ports@ ? Well, it will be an
 > improvement, at least no one will have to close them.
 
 I have two primary problems with the proposed patch
 - It's poorly written. This can be fixed.
 - The general message that it gives is not one I think is beneficial. We
 should be trying to remove barriers for people to report problems, not
 institute them.
 
 I can understand that you want to reduce the amount of waffle in the PR
 database, but I think your proposed change is too complicated and too
 negative.
 
 Now, I am not a committer nor subscribed to ports@, but surely hitting the
 Delete key once or twice a week more often is not that huge a price to
 pay?
 
 I propose that this patch be shortened to:
 
 --- article.sgml.orig   2005-01-15 10:16:42.000000000 +0800
 +++ article.sgml        2005-05-07 15:07:06.622424000 +0800
 @@ -106,7 +106,8 @@
         <para>Notification of updates to externally maintained
           software (mainly ports, but also externally maintained base
           system components such as BIND or various GNU
 -         utilities).</para>
 +         utilities). If you are reporting a new version of a
 +         port, try contacting the port's maintainer first.</para>
        </listitem>
      </itemizedlist>
 
 David Adam
 zanchey at ucc.gu.uwa.edu.au