Index: en_US.ISO8859-1/articles/problem-reports/article.xml
===================================================================
--- en_US.ISO8859-1/articles/problem-reports/article.xml
+++ en_US.ISO8859-1/articles/problem-reports/article.xml
@@ -101,30 +101,29 @@
for an answer, consider posing the question to the
&a.questions;.
- Some cases where it may be appropriate to submit a problem
- report about something that is not a bug are:
+ Consider these factors when submitting PRs about ports or
+ other software that is not part of &os; itself:
- Notification of updates to externally maintained
- software (such as ports or software in the contrib/
- directory).
+ Please do not submit problem reports that simply state
+ that a newer version of an application is available. Ports
+ maintainers are automatically notified by
+ portscout when a new version of
+ an application becomes available. Actual patches to update
+ a port to the latest version are welcome.
+
+ For unmaintained ports (MAINTAINER
- contains ports@FreeBSD.org), such update
- notifications might get picked up by an interested
- committer, or you might be asked to provide a patch to
- update the port; providing it upfront will greatly improve
- your chances that the port will get updated in a timely
- manner.
-
- If the port is maintained, PRs announcing new upstream
- releases are usually not very useful since they generate
- supplementary work for the committers, and the maintainer
- likely knows already there is a new version, they have
- probably worked with the developers on it, they are probably
- testing to see there is no regression, etc.
+ is ports@FreeBSD.org),
+ a PR without an included patch is unlikely to get picked up
+ by a committer. To become the maintainer of an
+ unmaintained port, submit a PR with the request (patch
+ preferred but not required).
+
+ In either case, following the process described in Porter's
Handbook will yield the best results. (You might