From owner-freebsd-ports@FreeBSD.ORG Thu Jun 5 02:44:23 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E270B6BB for ; Thu, 5 Jun 2014 02:44:22 +0000 (UTC) Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E2A52101 for ; Thu, 5 Jun 2014 02:44:22 +0000 (UTC) Received: by mail-qg0-f52.google.com with SMTP id a108so630373qge.11 for ; Wed, 04 Jun 2014 19:44:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=aLseDWxX5TLtJm66UaLroUzqMJnbLdF+Jv2rpTM/fEU=; b=LA2vvSjqWWNj+xLDEW04N+nR7g+0nh3X6mh514meVSWRDNyQWSavO9V39TKwoTdmXm JURRWR5iCMByY3iMOsmS7EVJypxpdYowdF6XyW8zSlq98PSyTwsTWLSQZLUvRdD1P9uu 2d/Y8z8Zad/OCs3tWYkWnpH+KkauMOERrOcy8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=aLseDWxX5TLtJm66UaLroUzqMJnbLdF+Jv2rpTM/fEU=; b=Naw61hXo7/+sSB2OFIN/IoJgP7MffKqiP+juoKg3KLbbt3UfbW259OrZfsKoKdkBDG pXnfg+9DQ+wAfwcfTIM6+zW++1EHPD79TzB4nf3o5wspfvdOHPM5G3nfuq0jUOEes5iA CBtTgteTXyL4JceP3HpxOgjlYwsBZ5kVHcFeTAnygOo8HMGhNpqMnJ7HlLp/hChO5q8q wpJX0PMnAcyZSEQpPKbUl1cd/2H3GVsNkmAB5j5tdykNkSSXZiUq2/4UitICbfJm2cxO ADj+RSyFYgzJJx9HoZaokZd1yqNASDd42mS9mvvPpfnWyYALIe4Vp6Isn8sVe6RqcKY8 hwwg== X-Gm-Message-State: ALoCoQnZOOQ0TBiQpS8oaevEh27tZx+5xBK768zsmc9/uqjkLOz7/Y8OBSWE3LMuo/2bFkh+wnpS X-Received: by 10.224.92.75 with SMTP id q11mr76329911qam.15.1401936261747; Wed, 04 Jun 2014 19:44:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.222.131 with HTTP; Wed, 4 Jun 2014 19:43:51 -0700 (PDT) In-Reply-To: <201406040058.s540w17f014287@fire.js.berklix.net> References: <201406040058.s540w17f014287@fire.js.berklix.net> From: Eitan Adler Date: Wed, 4 Jun 2014 19:43:51 -0700 Message-ID: Subject: Re: [FreeBSD-Announce] FreeBSD bug tracking moves from GNATS to Bugzilla To: "Julian H. Stacey" Content-Type: text/plain; charset=UTF-8 Cc: ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 02:44:23 -0000 On 3 June 2014 17:58, Julian H. Stacey wrote: > Hi, > Postmaster@ & webmaster@ are precedents. The orthogonal address > should be bugmaster@, (with an alias from bugmeister for the lost). > A random German Meister appended to Bug invites a French Maitre for next name. bugmeister@ is precedent. > That will discourage response. Some don't have or want net 24/7, > nor want to check a web in case someone might have asked for feedback, They get an email. > nor want heavy browsers rather than a lightweight mail tool. They can use the CLI > Some > will want to edit with font style, size, colour, word wrapping, & > vi keys, preference set by minimal latency localhost. They can use the CLI > Good, I've previously encountered people with patches who couldn't > be bothered to submit a send-pr. Requiring just web follow up will > deter more. Perhaps the reported initial rush may settle down, a > mix of pent up demand post switch over, + the trendy who try new things. lets see On 3 June 2014 18:52, Warren Block wrote: > Still, it acts as a test of the > submitter's determination and indirectly, the quality of the information > they give. This isn't about determination or even initial quality of the PR. Its about the ability to know we have a verified mechanism of talking to the reporter. ........ As to another point: > Yes. It is really frustrating to create a bug-report with a complete patch just to wait for some months and seeing that nothing happens. And even after offering help it is closed with "timeout" and the bug still exists. Before we couldn't track this. Now we can. Lets hope we can solve this problem. We still need more people to go through the bugs and fix things. -- Eitan Adler