ports/180387: [MAINTAINER-UPDATE] www/mawstats: set EXPIRATION_DATE to 2014-01-01

[Frank Wall]

>Number:         180387
>Category:       ports
>Synopsis:       [MAINTAINER-UPDATE] www/mawstats: set EXPIRATION_DATE to 2014-01-01
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          maintainer-update
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jul 08 15:00:01 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Frank Wall
>Release:        9.1-RELEASE-p3
>Organization:
>Environment:
FreeBSD XXX 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013     root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:

As the maintainer of www/mawstats I suggest to set this port to expire on 2014-01-01. I'm no longer going to support and maintain this port for the following reason:

This software, mawstats, started as a TEMPORARY fork of jawstats, but neither jawstats nor mawstats received any update since then. In fact, the author of mawstats abandoned his project and started a complete rewrite. The rewritten mawstats is a set of drupal modules and as such a completely different product than the original mawstats, see https://github.com/asafo/MAWStats.

The committer (i.e. YOU) may, of course, decide to not set an expiration date and instead return the port to the pool ports at freebsd.org. Still, my opinion is to let this port expire and advice people to use www/jawstats or good old www/awstats instead.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: