Remove Portsmon references

It's been a while since it's not working.

The FreeBSD Ports Monitoring System was a good resource for the project;
we thank linimon for creating and maintaining it for many years.

Approved by:	rene (portmgr)
Differential Revision: https://reviews.freebsd.org/D35025

4 files changed, 2 insertions, 51 deletions

diff --git a/documentation/content/en/articles/contributing/_index.adoc b/documentation/content/en/articles/contributing/_index.adoc
index 63ebc42b39..cd889a2361 100644
--- a/documentation/content/en/articles/contributing/_index.adoc
+++ b/documentation/content/en/articles/contributing/_index.adoc
@@ -265,12 +265,10 @@ There are a large number of unmaintained ports.
 It is a good idea to start with adopting a port that you use regularly.
 
 Unmaintained ports have their `MAINTAINER` set to `ports@FreeBSD.org`.
-A list of unmaintained ports and their current errors and problem reports can be seen at the http://portsmon.FreeBSD.org/portsconcordanceformaintainer.py?maintainer=ports%40FreeBSD.org[FreeBSD Ports Monitoring System].
+Many unmaintained ports can have pending updates, this can be seen at the https://portscout.freebsd.org/ports@freebsd.org.html[FreeBSD Ports distfile scanner].
 
 On https://portsfallout.com/fallout?port=&maintainer=ports%40FreeBSD.org[PortsFallout] can be seen a list of unmaintained ports with errors.
 
-Many unmaintained ports can have pending updates, this can be seen at the https://portscout.freebsd.org/ports@freebsd.org.html[FreeBSD Ports distfile scanner].
-
 Some ports affect a large number of others due to dependencies and slave port relationships.
 Generally, we want people to have some experience before they maintain such ports.
 
@@ -278,11 +276,6 @@ You can find out whether or not a port has dependencies or slave ports by lookin
 (The name of the file varies by release of FreeBSD; for instance, [.filename]#INDEX-8#.) Some ports have conditional dependencies that are not included in a default [.filename]#INDEX# build.
 We expect you to be able to recognize such ports by looking through other ports' [.filename]#Makefile#'s.
 
-[NOTE]
-======
-The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates.
-======
-
 ==== How to adopt the port
 
 First make sure you understand your <<maintain-port>>.
@@ -525,9 +518,6 @@ There are some really good places to find a port that needs some attention.
 You can use the https://bugs.freebsd.org/search[web interface] to the Problem Report database to search through and view unresolved PRs.
 The majority of ports PRs are updates, but with a little searching and skimming over synopses you should be able to find something interesting to work on (the `sw-bug` class is a good place to start).
 
-The other place is the http://portsmon.FreeBSD.org/[FreeBSD Ports Monitoring System].
-In particular look for unmaintained ports with build errors and ports that are marked `BROKEN`.
-
 https://portsfallout.com/[PortsFallout] shows port issues gathered from the FreeBSD package building.
 
 It is OK to send changes for a maintained port as well, but remember to ask the maintainer in case they are already working on the problem.
@@ -536,11 +526,6 @@ Once you have found a bug or problem, collect information, investigate and fix!
 Otherwise create a new PR.
 Your changes will be reviewed and, if everything checks out, committed.
 
-[NOTE]
-======
-The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates.
-======
-
 [[mortal-coil]]
 === When to call it quits
 
@@ -563,10 +548,6 @@ In 2005 more than eleven thousand ports PRs were submitted! Following this artic
 
 The https://bugs.freebsd.org/bugzilla/query.cgi[Problem Report database].
 
-The http://portsmon.FreeBSD.org/[FreeBSD Ports Monitoring System (portsmon)] can show you cross-referenced information about ports such as build errors and problem reports.
-If you are a maintainer you can use it to check on the build status of your ports.
-As a contributor you can use it to find broken and unmaintained ports that need to be fixed.
-
 The http://portscout.FreeBSD.org[FreeBSD Ports distfile scanner (portscout)] can show you ports for which the distfiles are not fetchable.
 You can check on your own ports or use it to find ports that need their `MASTER_SITES` updated.
 
diff --git a/documentation/content/en/books/porters-handbook/keeping-up/_index.adoc b/documentation/content/en/books/porters-handbook/keeping-up/_index.adoc
index 2a8cf3e639..9061a38d2b 100644
--- a/documentation/content/en/books/porters-handbook/keeping-up/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/keeping-up/_index.adoc
@@ -110,23 +110,3 @@ A search function on this page allows the user to search for a specific port.
 Clicking on a port name in the list displays the http://freshports.org[FreshPorts] port information.
 
 Additional documentation is available in the https://github.com/freebsd/portscout[Portscout repository].
-
-[[portsmon]]
-== The FreeBSD Ports Monitoring System
-
-Another handy resource is the http://portsmon.FreeBSD.org[FreeBSD Ports Monitoring System] (also known as `portsmon`).
-This system comprises a database that processes information from several sources and allows it to be browsed via a web interface.
-Currently, the ports Problem Reports (PRs), the error logs from the build cluster, and individual files from the ports collection are used.
-In the future, this will be expanded to include the distfile survey, as well as other sources.
-
-To get started, use the http://portsmon.FreeBSD.org/portoverview.py[Overview of One Port] search page to find all the information about a port.
-
-This is the only resource available that maps PR entries to portnames.
-PR submitters do not always include the portname in their Synopsis, although we would prefer that they did.
-So, `portsmon` is a good place to find out whether an existing port has any PRs filed against it, any build errors,
-or if a new port the porter is considering creating has already been submitted.
-
-[NOTE]
-======
-The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates.
-======
diff --git a/documentation/content/en/books/porters-handbook/porting-dads/_index.adoc b/documentation/content/en/books/porters-handbook/porting-dads/_index.adoc
index 9693c0ca93..f04dfbe22f 100644
--- a/documentation/content/en/books/porters-handbook/porting-dads/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/porting-dads/_index.adoc
@@ -315,7 +315,7 @@ In certain cases, users must be prevented from installing a port.
 There are several variables that can be used in a port's [.filename]#Makefile# to tell the user that the port cannot be installed.
 The value of these make variables will be the reason that is shown to users for why the port refuses to install itself.
 Please use the correct make variable.
-Each variable conveys radically different meanings, both to users and to automated systems that depend on [.filename]##Makefile##s, such as crossref:keeping-up[build-cluster,the ports build cluster], crossref:keeping-up[freshports,FreshPorts], and crossref:keeping-up[portsmon,portsmon].
+Each variable conveys radically different meanings, both to users and to automated systems that depend on [.filename]##Makefile##s, such as crossref:keeping-up[build-cluster,the ports build cluster], and crossref:keeping-up[freshports,FreshPorts].
 
 [[dads-noinstall-variables]]
 === Variables
diff --git a/documentation/content/en/books/porters-handbook/upgrading/_index.adoc b/documentation/content/en/books/porters-handbook/upgrading/_index.adoc
index 3cd5e01f68..14ddf24af6 100644
--- a/documentation/content/en/books/porters-handbook/upgrading/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/upgrading/_index.adoc
@@ -59,16 +59,6 @@ To do this, there are two options.
 There is a searchable interface to the https://bugs.freebsd.org/search/[FreeBSD Problem Report (PR) or bug database].
 Select `Ports & Packages` in the `Product` multiple select menu, and enter the name of the port in the `Summary` field.
 
-However, sometimes people forget to put the name of the port into the Summary field in an unambiguous fashion.
-In that case, try searching in the `Comment` field in the `Detailled Bug Information` section, or try the crossref:keeping-up[portsmon,FreeBSD Ports Monitoring System] (also known as `portsmon`).
-This system attempts to classify port PRs by portname.
-To search for PRs about a particular port, use the http://portsmon.FreeBSD.org/portoverview.py[Overview of One Port].
-
-[NOTE]
-======
-The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates.
-======
-
 If there is no pending PR, the next step is to send an email to the port's maintainer, as shown by `make maintainer`.
 That person may already be working on an upgrade, or have a reason to not upgrade the port right now (because of, for example, stability problems of the new version), and there is no need to duplicate their work.
 Note that unmaintained ports are listed with a maintainer of `ports@FreeBSD.org`, which is just the general ports mailing list, so sending mail there probably will not help in this case.