From owner-freebsd-ports@FreeBSD.ORG Wed Oct 22 17:46:35 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B0D916A4B3; Wed, 22 Oct 2003 17:46:35 -0700 (PDT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92F0243F85; Wed, 22 Oct 2003 17:46:34 -0700 (PDT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 140E01468A; Wed, 22 Oct 2003 19:46:34 -0500 (CDT) Date: Wed, 22 Oct 2003 19:46:34 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: Sergey Matveychuk In-Reply-To: <3F971F76.90308@ciam.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Mark Linimon cc: freebsd-doc@freebsd.org cc: Eric Anderson cc: ceri@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: a reminder to PR submitters X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Oct 2003 00:46:35 -0000 > It's may be not for cgi-program, but I'd like to have a mechanism to > watch for some PR's. Like bugzilla or freshports.org have. I have the code to scan PRs, but I do not have the subscription- based back end like Dan (=freshports) has. Failing that, I am reluctant to just "send out" PR reminders. The code I am working on is a batch-based reminder list that would only go to a) people who do not have an @FreeBSD.org address (because they can be assigned the PR in GNATS and thus automatically reminded) intersection with b) PRs are that more than "some number of days" old (I think my prototype is set for 60 or 90). The main problem with this is not technical, it's political. I do not wish to unilaterally impose any post-facto burden on maintainers. The secondary problem is that my PR classification algorithm generates false positives. Thus before any run of the notification code, my database must be manually preened to remove them. (I cannot imagine anything more irritating than to get an automated complaint about something that isn't really your problem and thus really can't do anything about). I was actively working on the batch code until I got a commit bit a week or so ago and have been fixing other stuff since then :-) In the meantime you can get an HTML page with your ports at http://lonesome.dyndns.org:4802/bento/errorlogs/portsconcordanceformaintainer.py and bookmark the result once you put in your own email address. mcl