From owner-freebsd-ports@FreeBSD.ORG Sat Jul 14 16:47:42 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E5AE106566C for ; Sat, 14 Jul 2012 16:47:42 +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 9A9F88FC0A for ; Sat, 14 Jul 2012 16:47:41 +0000 (UTC) Received: by bkcje9 with SMTP id je9so4036238bkc.13 for ; Sat, 14 Jul 2012 09:47:40 -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=lC0KBCsmiAx556UcRpsRWc4fVxyn7Rjglr1dm6JZ/kk=; b=tRP8wcsO9TCYlhspWJLkKo9xPahrqBF1Mmi99ZZVc+1DTaGevAA3ft59aPnFB0tL2O q7jPn1Myf6qGiTo8/PtpBQ79EDq2H9977vSzuXSD6CM4UAjJ+hh7dH6nTpm6xgUrVZY0 wYCQDXo007lQHbKtcYwUw+rcf1Ce2WR36VmQCis43QWm9UkS53bLPGwuFk5MC3JsLgaD TBgsxl+M0qF8dbGy0GQlYMrfF1N7rRh/A56VrOhrz4oM4g/I3sBafuf+2IZJ1GcCxQM9 Lmc73qgo4i4ZAz6/DqhA0Z+6VmZX8NEDv6hxwtXk8yZc2lRCbKeujeHPfPD23oNGZqfQ xLUg== Received: by 10.204.152.27 with SMTP id e27mr2674576bkw.56.1342284460688; Sat, 14 Jul 2012 09:47:40 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.49.87 with HTTP; Sat, 14 Jul 2012 09:47:10 -0700 (PDT) In-Reply-To: References: <50017C97.3050200@filez.com> From: Chris Rees Date: Sat, 14 Jul 2012 17:47:10 +0100 X-Google-Sender-Auth: YyfU4sUMX52KKW4C4VD_dqlPCck 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 16:47:42 -0000 On 14 July 2012 17:34, Vitaly Magerya wrote: > Chris Rees wrote: >>> Is automatic unassignment possible? >> >> Technically yes, but it's highly undesirable. > > Why? > >> You can feel free to >> bring it up here if you think that's happened. > > I will, if it'll happen to me. In the mean while here's an > incomplete list of PRs that where (auto)assigned to committers > in June and didn't see any progress in at least 2 weeks: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168564 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168571 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168629 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168667 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168840 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168850 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168870 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168917 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168957 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169076 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169271 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169287 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169305 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169369 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169370 > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169388 > (previous one is misassigned; the submitter *is* the maintainer) > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/169458 Normally a ping to the maintainer reveals the delay-- I've taken ports/169388 because the autoassigner looked at the Synopsis which was written wrongly. If you want to check progress, send a followup to the PR. > > In some of these cases I think that work may continue behind the > scenes, but it's hard to tell. Usually, but people should generally reply to acknowledge the PR. Chris