Return-Path: X-Original-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 81597D6FD for ; Thu, 28 Feb 2013 20:06:42 +0000 (UTC) Received: (qmail 93309 invoked by uid 500); 28 Feb 2013 20:06:42 -0000 Delivered-To: apmail-incubator-mesos-dev-archive@incubator.apache.org Received: (qmail 93284 invoked by uid 500); 28 Feb 2013 20:06:42 -0000 Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mesos-dev@incubator.apache.org Delivered-To: mailing list mesos-dev@incubator.apache.org Received: (qmail 93275 invoked by uid 99); 28 Feb 2013 20:06:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 20:06:42 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=FSL_HAS_TINYURL,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of haircut@gmail.com designates 209.85.220.43 as permitted sender) Received: from [209.85.220.43] (HELO mail-pa0-f43.google.com) (209.85.220.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Feb 2013 20:06:32 +0000 Received: by mail-pa0-f43.google.com with SMTP id bh2so1343206pad.2 for ; Thu, 28 Feb 2013 12:06:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type; bh=wyig9Gn+BVUcNfvnLLWdc+jzqoMlB79IIAHjpCjw5iI=; b=jRUbbuiSLy6+zSdDL5dJgAfHIu2TwuNDuYfFcXK1WVbqRqQjxoeZYKbPuESFqHIO6Z In+SHf0iVmVQdxehwtnFa2O1G2hh6mYdL6DE7vSBXk6+fMNw1iu1ICJjm+lhlzoq+2UD 1H6BdHV2tMxgYVOyuI6q4akmMOL+ygkmbMK5dhioMDSvlyvlewHA5zCpX5B0Y6EZd8Sw SJD/IWMksf1eL79z9boMuVY1XRBrhl4NozWOVfKf0UlZDolh75z7xhKGD0R2X+9qg1jw ZOsPRgCqWCoLMefS2uKAWD9OfXAxcpGKppHDCb4rie9vP9Pa3XToKbNWkNk2klSTUqI9 AD2Q== X-Received: by 10.68.254.69 with SMTP id ag5mr10847479pbd.31.1362081971586; Thu, 28 Feb 2013 12:06:11 -0800 (PST) Received: from [192.168.13.92] (c-174-61-187-243.hsd1.wa.comcast.net. [174.61.187.243]) by mx.google.com with ESMTPS id x2sm10267032paw.8.2013.02.28.12.06.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 12:06:10 -0800 (PST) Message-ID: <512FB8B1.6010401@gmail.com> Date: Thu, 28 Feb 2013 12:06:09 -0800 From: Adam Monsen User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: mesos-dev@incubator.apache.org CC: Benjamin Hindman Subject: Re: PROPOSAL: send notifications to separate mailing list References: <512F9CF7.4070204@gmail.com> In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2XFJVJKXXMKFXTBFHVNRS" X-Virus-Checked: Checked by ClamAV on apache.org ------enig2XFJVJKXXMKFXTBFHVNRS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 02/28/2013 10:57 AM, Benjamin Hindman wrote: > I'm not opposed to the idea, but we do A LOT of communication via JIRA = and > Review Board, and my fear is that relegating these automatically genera= ted > emails to a separate list will cause people to miss the > *actual*conversation that's going on. I don't like the idea of having > the > conversation in too many places, e.g., on the mailing list, and on Revi= ew > Board, and on JIRA! Yes, agreed. Fewer sources of truth/activity are better! Here's some constructive criticism. I've been trying to follow development conversations in JIRA and Review Board, and I'm finding the mailing list useless for this purpose. I end up just using the mailing list, JIRA, and Review Board separately anyway.= For example: I can easily see what's going on in a Review Board review or a JIRA issue because of the handy UI. Here's a review with lots of activity: https://reviews.apache.org/r/9408/ . Looks great there. I can pick out the chronology, participants, and see the commented diffs! That's a pretty cool tool. A notification from review 9408 on the mailing list is much less helpful. Here's one of the actions out of context: http://tinyurl.com/cbpyfwr . That email by itself adds little except an audit trail. It crowds out (IMHO) more important emails. I wouldn't reply directly to it. I really have to go back to Review Board to do anything useful with that notification. Maybe the problem is just that I'm trying to browse the archives, and mod_mbox is not my favorite mailing list archive browser. I'll try email filtering before any more whinging. If you're still feeling thumbs-down after reading the above, I'll probably withdraw my proposal. This may just be me getting used to Mesos development/communication. I also found http://tinyurl.com/ch2njku ... Andrew maybe got put off by the notification emails too. Again, might just be an issue for new Mesos contributors. ------enig2XFJVJKXXMKFXTBFHVNRS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJRL7ixAAoJEJtdmT+DbynAXU8IAMZZjGJQNhMdeharyF8bURFQ 4M3fZjhxott4e1aQQfWdT1vfXRPZtJ9Z7VqCLbmzw2GIDwoFHvbcHEQ00RlSle1G r4w5Q/gXdBYwx4GmLEUzjEwc2K7u5c/7AX0+FJweMDXcNkny/bPMQrRfo3uXSnW3 ronkZsx0Lad76bUmr4cF7ZYvsnreL3GcJ9vHMu2+zzL5FhNCWDn+Kqx89h10n1TW rLgGjBPbUXP7/J8SBJ+wdhmR8l9VCAkE5D5CeMCM7mDX6MblrXPMawlPllp1rYHo BZCEywi7aFnO3skT8lbAogC8Rfvb0tewnABgll7mikJYp4ujthhgf6/11ov093A= =II22 -----END PGP SIGNATURE----- ------enig2XFJVJKXXMKFXTBFHVNRS--