If the ported software has a homepage, you should list it in pkg/DESCR.

This is so that k001 things like wosch's script can link to them, making
port-browsing much more meaningful.  Now, if someone will add similar
functionality to pkg_add(1).  ;)

handbook/porting.sgml

@@ -1,4 +1,4 @@
-<!-- $Id: porting.sgml,v 1.97 1998-05-08 16:57:52 obrien Exp $ -->
+<!-- $Id: porting.sgml,v 1.98 1998-05-09 14:59:29 hoek Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect1><heading>Porting an existing piece of free software<label id="porting"></heading>
@@ -246,12 +246,13 @@ A cat chasing a mouse all over the screen.
 
 	  <p>This is a longer description of the port.  One to a few
 	    paragraphs concisely explaining what the port does is
-	    sufficient.  Note: This is <em>not</em> a manual nor an
-	    in-depth description on how to use or compile the port.
+	    sufficient.  This is <em>not</em> a manual or an
+	    in-depth description on how to use or compile the port!
 	    <em>Please be careful if you are copying from the
 	    <tt>README</tt> or manpage</em>; too often they are not a
 	    concise description of the port or are in an awkward format
-	    (e.g. manpages have justified spacing).
+	    (e.g. manpages have justified spacing).  If the ported software
+	    has an official WWW homepage, you should list in here.
 
 	  <p>It is recommended that you sign the name at the end of
 	    this file, as in:
@@ -262,6 +263,8 @@ the screen.
  :
 (etc.)
 
+http://www.oneko.org/
+
 - Satoshi
 asami@cs.berkeley.edu
 </verb></tscreen>