Return-Path: Delivered-To: apmail-mina-dev-archive@www.apache.org Received: (qmail 16008 invoked from network); 25 Jan 2010 13:48:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jan 2010 13:48:50 -0000 Received: (qmail 63764 invoked by uid 500); 25 Jan 2010 13:48:49 -0000 Delivered-To: apmail-mina-dev-archive@mina.apache.org Received: (qmail 63668 invoked by uid 500); 25 Jan 2010 13:48:49 -0000 Mailing-List: contact dev-help@mina.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mina.apache.org Delivered-To: mailing list dev@mina.apache.org Received: (qmail 63658 invoked by uid 99); 25 Jan 2010 13:48:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 13:48:49 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of apache@bago.org designates 209.85.219.171 as permitted sender) Received: from [209.85.219.171] (HELO mail-ew0-f171.google.com) (209.85.219.171) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 13:48:40 +0000 Received: by ewy19 with SMTP id 19so809978ewy.1 for ; Mon, 25 Jan 2010 05:48:17 -0800 (PST) Received: by 10.213.103.84 with SMTP id j20mr3721847ebo.3.1264427296869; Mon, 25 Jan 2010 05:48:16 -0800 (PST) Received: from mail-ew0-f219.google.com (mail-ew0-f219.google.com [209.85.219.219]) by mx.google.com with ESMTPS id 16sm4463185ewy.14.2010.01.25.05.48.16 (version=SSLv3 cipher=RC4-MD5); Mon, 25 Jan 2010 05:48:16 -0800 (PST) Received: by ewy19 with SMTP id 19so1997949ewy.21 for ; Mon, 25 Jan 2010 05:48:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.90.208 with SMTP id e58mr74679wef.57.1264427295426; Mon, 25 Jan 2010 05:48:15 -0800 (PST) X-Originating-IP: [78.134.13.105] In-Reply-To: References: <4B35582D.40408@gmail.com> <88f6e29a1001200223j7232f25bg19b5a627173d9e47@mail.gmail.com> <9542E526-AD53-4059-8CC3-30DE488F089F@toolazydogs.com> <88f6e29a1001200746o4f3ef563g7bd4e69c00fc29c1@mail.gmail.com> <88f6e29a1001210728y5ee56991i91759cc3aa2bcab9@mail.gmail.com> <5F96003C-93BA-4BAA-B063-ECAFD833B436@toolazydogs.com> <4B5D4287.2010505@gmail.com> <88f6e29a1001250524l26d9f108id784d42e8f0c77c8@mail.gmail.com> Date: Mon, 25 Jan 2010 14:48:15 +0100 Message-ID: <9426afb71001250548t4e9fb1c8mae9c597f892ec402@mail.gmail.com> Subject: Re: Google analytics finally setup and working on MINA sie ! From: Stefano Bagnara To: dev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2010/1/25 Alan D. Cabrera : > > On Jan 25, 2010, at 5:24 AM, Bernd Fondermann wrote: > >> On Mon, Jan 25, 2010 at 08:04, Emmanuel Lecharny >> wrote: >>> >>> Alan D. Cabrera a =E9crit : >>>> >>>> On Jan 21, 2010, at 7:28 AM, Bernd Fondermann wrote: >>>> >>>>> On Wed, Jan 20, 2010 at 18:42, Alan D. Cabrera >>>>> wrote: >>>>>> >>>> >>>> Are these reports published? >>> >>> No but you can have a look at them here : >>> >>> https://www.google.com/analytics/settings/?et=3Dreset&hl=3Den#scid=3D11= 074178 >> >> I cannot see anything following this URL. >> I think the Analytics user must share by adding the person's google >> account to the analytics profile. >> That's the way it worked a few years back with JAMES. > > Would it make sense to have Google Analytics send an email report to the > list? IIRC I read something on the legal-discuss list about possible problems with what are you entitled to do with the report Google sends you (you cannot make it public, IIRC). So, it is probably safe to send the report to the private@ list, not so sure the same is valid for the public mailing lists. Like Bernd said, to avoid issues with google, in JAMES project I simply asked interested committers to tell me their google account and I added privileges to their account so each committer configured the preferred notification for himself. Stefano