linux-kernel - Re: Tracking and crediting bug reporters

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87r6bv4w7o.fsf@saeurebad.de>
Date:	Wed, 21 May 2008 15:34:35 +0200
From:	Johannes Weiner <hannes@...urebad.de>
To:	Pavel Machek <pavel@....cz>
Cc:	Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org
Subject: Re: Tracking and crediting bug reporters

Hi,

Pavel Machek <pavel@....cz> writes:

> Hi!
>
>> So here's what we would like to try instead.  Whenever somebody sends up a
>> patch fixing a reported bug, the name of the person who reported the bug
>> would be immortalized with this tag:
>> 
>> 	Reported-by: A. Bug Reporter <email@...s.here>
>> 
>> In particular, reporters who work with the developers toward the resolution
>> of the bug should be thanked in this way.  If we wanted to take things
>
> I believe we have enough tags already. Plus, if the reporter really
> works with the developer till the end, there's already accepter
> Tested-by: flag, right?

I would more argue to remove Tested-by completely because it does not
tell much.  Code is not bugfree just because someone compiled and ran
it.  And if it breaks on some other systems later on, what does it help
if you know someone tested it?  It still breaks.  And you can not even
blame the tester because of his luck of a working configuration.

While a Reported-by in this case credits a person reporting a bug.  Just
that.  And perhaps that the report was good enough to make a fix.

	Hannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/