From owner-freebsd-ports@FreeBSD.ORG Sat Jul 14 15:28:24 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A722A1065670 for ; Sat, 14 Jul 2012 15:28:24 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 315888FC08 for ; Sat, 14 Jul 2012 15:28:24 +0000 (UTC) Received: by bkcje9 with SMTP id je9so4013620bkc.13 for ; Sat, 14 Jul 2012 08:28:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=CMcuusAC96CvAcOKLsBdxgBxRQfqPEXwJPlywepPvAI=; b=ixuG5aMSNc6La+2cUp60QcM6cAC5KhWG2P4EFzWW4btfKZg9cH0EbBbOqEHz8+XMD3 06mgW5lMiUt/f0GC9CAjVfglOUO8EFWGl6cEED92u1k5Edsz1x9AxzEieRswbBl/baDN eRojYTfrDh/NsdZLV6uqEJNk9RJXRNxHwQeLnAGKA+XRL31nXLCowVlIplv8LnkGXFoX mIf+ua2giAiOSS3/VA/DpM+VaaDs6dL/BQjxqQaI39tDVvn8LJJ9996QvGHe1otYwUQM eqhMoHQJ1DAjcWkaBKyiM/BDfbswIoaUH2vrwtyI3BZo3SeZNg9PuHTVT38yXkFsU/Y1 A2GA== Received: by 10.204.151.81 with SMTP id b17mr2678363bkw.95.1342279703239; Sat, 14 Jul 2012 08:28:23 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.49.87 with HTTP; Sat, 14 Jul 2012 08:27:53 -0700 (PDT) In-Reply-To: References: <50017C97.3050200@filez.com> From: Chris Rees Date: Sat, 14 Jul 2012 16:27:53 +0100 X-Google-Sender-Auth: f7xaJqCcmEhXotpIahvmML4tJL0 Message-ID: To: Vitaly Magerya Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-ports@freebsd.org, Radim Kolar Subject: Re: maintainer timeout for FreeBSD commiters X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jul 2012 15:28:24 -0000 On 14 July 2012 16:24, Vitaly Magerya wrote: > Chris Rees wrote: >> No-one is exempt from timeouts on ports except secteam and portmgr. > > One problem (at least how it appears to me) is that when a PR gets > automatically assigned to a maintainer who is also a committer, it is > not automatically unassigned if the person is missing for a few > months, and other committers ignore the PR because it is already > assigned. > > This only happened once to me, but it took 6 months for another > committer to notice it. And that was pretty fast, comparing to, say > ports/154456 [1], which is open since 2011-02. > > Is automatic unassignment possible? Technically yes, but it's highly undesirable. You can feel free to bring it up here if you think that's happened. Chris