Re: How IETF treats contributors
"Olaf M. Kolkman" <olaf@ripe.net> Tue, 31 August 2004 09:33 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01496; Tue, 31 Aug 2004 05:33:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C252e-0006gT-If; Tue, 31 Aug 2004 05:35:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C24tC-0001Aa-Nw; Tue, 31 Aug 2004 05:25:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C24rO-0000sT-6H for ietf@megatron.ietf.org; Tue, 31 Aug 2004 05:23:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01170 for <ietf@ietf.org>; Tue, 31 Aug 2004 05:23:24 -0400 (EDT)
Received: from postman.ripe.net ([193.0.0.199]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C24tI-0006Wk-3i for ietf@ietf.org; Tue, 31 Aug 2004 05:25:27 -0400
Received: by postman.ripe.net (Postfix, from userid 8) id A352D51FA8; Tue, 31 Aug 2004 11:22:49 +0200 (CEST)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 37DC14E055 for <ietf@ietf.org>; Tue, 31 Aug 2004 10:40:16 +0200 (CEST)
Received: from x50.ripe.net (x50.ripe.net [193.0.1.50]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id i7V8eGDI019975 for <ietf@ietf.org>; Tue, 31 Aug 2004 10:40:16 +0200
Date: Tue, 31 Aug 2004 10:40:16 +0200
From: "Olaf M. Kolkman" <olaf@ripe.net>
To: ietf@ietf.org
Message-Id: <20040831104016.4bf3d0c6.olaf@ripe.net>
In-Reply-To: <LV-SVRFRaqbC8wSA1Xv0000014e@lv-svr.lumenvox.com>
References: <2D0CA64CDC33E14DA7AB043B8CC4D2BB02340DFC@svr-exc.domain.com> <LV-SVRFRaqbC8wSA1Xv0000014e@lv-svr.lumenvox.com>
Organization: RIPE NCC
X-Mailer: Sylpheed version 0.9.11 (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Status: N 0.000024 / 0.0 / 0.0 / disabled
X-RIPE-Signature: 178840d85979cc625121fc95e9aa3d9f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Subject: Re: How IETF treats contributors
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Thomas Gal: > I agree with: > > "This isn't suppose to be an ego trip. If people really think the documents > are important, they don't need their names on them. If they need their name > on it, they are doing it for the wrong reasons." Me too. Documents should only be written if they are important for the commons. But. If it comes to acknowledging attributions we have to be careful. I do not think it is a good idea to drop authorship of documents. We do not have many means to motivate people. Giving credit is actually one of very few means that the IETF has available as a motivational tool. It is easy to forget folk that where involved in early stages, but as Christian said "bits are cheap" and if there is doubt on where to stop acknowledging people we'd better be safe than sorry. I'd like to expand on what Dean said: "Credit and attribution is about intellectual honesty [ and _courtesy_ ] not about copyright law". -- Olaf _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Ted Hardie
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Marc Blanchet
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Ted Hardie
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors william(at)elan.net
- RE: How IETF treats contributors Christian Huitema
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors John Day
- Re: How IETF treats contributors Clint Chaplin
- RE: How IETF treats contributors Thomas Gal
- RE: How IETF treats contributors Nick Carter
- Re: How IETF treats contributors Olaf M. Kolkman
- RE: How IETF treats contributors Scott Bradner
- Re: How IETF treats contributors Vernon Schryver
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Hadmut Danisch
- RE: How IETF treats contributors ned.freed
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors william(at)elan.net
- Re: How IETF treats contributors Harald Tveit Alvestrand
- Re: How IETF treats contributors Nathaniel Borenstein
- Re: How IETF treats contributors ned.freed
- Re: How IETF treats contributors grenville armitage