Delivery-Date: Fri, 02 Jan 2015 12:37:32 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id CDCC31E0ADE
	for <archiver@seul.org>; Fri,  2 Jan 2015 12:37:30 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9704E32706;
	Fri,  2 Jan 2015 17:37:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A9DBD324F5
 for <tor-talk@lists.torproject.org>; Fri,  2 Jan 2015 17:37:22 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Oln8yg0nqZlN for <tor-talk@lists.torproject.org>;
 Fri,  2 Jan 2015 17:37:22 +0000 (UTC)
Received: from mail-wi0-x242.google.com (mail-wi0-x242.google.com
 [IPv6:2a00:1450:400c:c05::242])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 5C615324CB
 for <tor-talk@lists.torproject.org>; Fri,  2 Jan 2015 17:37:22 +0000 (UTC)
Received: by mail-wi0-f194.google.com with SMTP id l15so13083299wiw.5
 for <tor-talk@lists.torproject.org>; Fri, 02 Jan 2015 09:37:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=Sxoxu5NRGoSB2G/TI8TGuN7wLaPd5NPZ6rRb0umD4e4=;
 b=qI578On1oU9X9g+eL6zUrVKCMOuESjBtSTrkVZBY7n9wRU160ZxIKOxDS5NQ6X71zM
 hGpQkEZHIycd7LrZ3HEuOvoyXkEDURComHcTGp25ttEzu1Gt+E09Zw3b9wO+/A2CRnVR
 uJvouTP6SaVZApYvFPVwgpDPMCq8lBYnaT4rG4B6IJ5wwykNqSpuLFdo2ZwiccvfmujI
 1Ylf8K12ZEI4NqIuOI73XsBTmJ0mjk9+UbfOfLYMAbsTM91vPl4tE5OYqmFfQBVuDirp
 lq59MUbM1CCk+wJH4zLjjz8UgqSTvAukjWa0wcphxa4lIJKFcVNnjEsXU0ckm+glPr2C
 C5UA==
X-Received: by 10.194.81.1 with SMTP id v1mr153417510wjx.50.1420220239442;
 Fri, 02 Jan 2015 09:37:19 -0800 (PST)
Received: from [192.168.2.129]
 (dslb-188-100-174-120.188.100.pools.vodafone-ip.de. [188.100.174.120])
 by mx.google.com with ESMTPSA id t12sm52363618wju.19.2015.01.02.09.37.18
 for <tor-talk@lists.torproject.org>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Fri, 02 Jan 2015 09:37:18 -0800 (PST)
Message-ID: <54A6D750.904@googlemail.com>
Date: Fri, 02 Jan 2015 18:37:20 +0100
From: "Sebastian G. <bastik.tor>" <bastik.tor@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <CAKDKvuxMyy6e+rzTpu4i5TYvXG8VYgow4jqkbFUea79UftnGCA@mail.gmail.com>
 <54A456A1.7030009@googlemail.com>
 <CAKDKvuyuWMAB-970LSMMeprAkcFuD52y6PPRvH+KycoAYQx=Bw@mail.gmail.com>
In-Reply-To: <CAKDKvuyuWMAB-970LSMMeprAkcFuD52y6PPRvH+KycoAYQx=Bw@mail.gmail.com>
Subject: [tor-talk] Input and Feedback for Tor stuff (was: Re: Tor
 0.2.6.2-alpha is now released!)
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

01.01.2015, 21:56 Nick Mathewson:
> On Dec 31, 2014 3:03 PM, "Sebastian G. &lt;bastik.tor&gt;" <
> bastik.tor@googlemail.com> wrote:
>>
>> 31.12.2014, 19:27 Nick Mathewson:
>>
>> Happy New Year to everyone.
>>
>> Some stuff could have been called "Minor changes" to silence people that
>> grep for "bugfix" and count the occurrences, although there were no bugs
>> fixed, just changes.
> 
> Yeah, it's often a matter of opinion what to call a bug and what to call a
> missing feature.

Sure.

> [...]
> Say,  everybody who is looking for issues in the changelog: would there be
> a good way to involve you earlier next time? It seems that before I put a
> release out is when I need the most feedback, but also when I have to beg
> the most to get it.  Maybe I should get a mail out to tor-talk a day or two
> *before* the next release, to better make use of this help.

I was not looking for issues, specifically. I was interested in what the
changes are, not if there are any mistakes. Reading it because of
interest in it will be my primary concern.

I don't know if I would be good at finding mistakes, but the more people
try the better.

Sending a draft to tor-talk would certainly work for me. I'd prefer if
it is obvious that it is a draft. Before you resurrected tor-announce I
saw a change-log on tor-talk and went to the Tor website to download the
latest binary. So saying it's a draft in the subject helps to avoid
confusion.

Sending to tor-talk would also work, because there are lots of people on it.

How about another list like tor-feedback for general things to review
(e.g no patches, no code, no proposals)? Interested people could
subscribe (I would) and get drafts of the change-log to review for
errors. This could include things like blog entries that have to be
reviewed or the Tor Newsletter in its RC state.

I'm open to other suggestions.

Best Regards,
Sebastian
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

