From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755857AbYELWAR (ORCPT ); Mon, 12 May 2008 18:00:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753472AbYELWAE (ORCPT ); Mon, 12 May 2008 18:00:04 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:41585 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751464AbYELWAB (ORCPT ); Mon, 12 May 2008 18:00:01 -0400 From: "Rafael J. Wysocki" To: Alan Cox Subject: Re: Tracking and crediting bug reporters Date: Mon, 12 May 2008 23:59:53 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: Jiri Slaby , Jonathan Corbet , linux-kernel@vger.kernel.org References: <4388.1210613272@vena.lwn.net> <4828AE8D.4000209@gmail.com> <20080512221109.4fa51a71@core> In-Reply-To: <20080512221109.4fa51a71@core> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805122359.53883.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, 12 of May 2008, Alan Cox wrote: > > > I cannot add a tag with a third party personal information upon it > > > without their permission nor can anyone else in a part of the world with > > > any vaguely resembling privacy laws. > > > > IANAL. Unless it's a public information, no? (As reports are.) > > If they made it public fine - although building a database of that > requires care. That was my point. You need specific permission of the bug > reporter. Given bug reporters may have personal reasons (including 'works > at Microsoft') and business ones (from 'company policy' to 'three letter > agency') for not wanting the information public. Well, don't the mailing list archives build such data bases already? By posting a report to a mailing list the archives of which are publicly available, and the LKML is one of those, you make your name and email address information publicly available and recorded forever anyway, in the context of the report. Thanks, Rafael