Re: How IETF treats contributors
Nathaniel Borenstein <nsb@guppylake.com> Sat, 04 September 2004 02:51 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 WAA03444; Fri, 3 Sep 2004 22:51:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3QhL-00076g-SL; Fri, 03 Sep 2004 22:54:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3QSH-0006G9-Iz; Fri, 03 Sep 2004 22:39:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3QRf-00062E-MP for ietf@megatron.ietf.org; Fri, 03 Sep 2004 22:38:28 -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 WAA02888 for <ietf@ietf.org>; Fri, 3 Sep 2004 22:38:25 -0400 (EDT)
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196] helo=mail.optistreams.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3QUO-0006sN-Kg for ietf@ietf.org; Fri, 03 Sep 2004 22:41:17 -0400
Received: from [192.168.1.101] [66.82.54.220] by mail.optistreams.net with ESMTP (SMTPD32-8.04) id A44670D600E0; Fri, 03 Sep 2004 19:11:18 -0700
In-Reply-To: <v04220806bd5962148387@[10.0.1.13]>
References: <20040830090627.GA22982@danisch.de> <v04220806bd5962148387@[10.0.1.13]>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <5905840A-FE1B-11D8-8364-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Fri, 03 Sep 2004 22:37:21 -0400
To: John Day <day@std.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
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.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
On Aug 30, 2004, at 7:05 PM, John Day wrote: > The best solution is to remove all authorship from all Internet > standards, then there will be no problems. 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. I would argue against this on the grounds that we want to encourage standards work as an attractive career path. If we want bright young people to put work into standards, it is appropriate to give credit for that work. Writing a good standard, and building a consensus around it, is a challenging set of tasks that requires a combination of technical and political skills that are all too rare, and sometimes hard to recognize. If we want more companies to send their best people to work in IETF groups, we need to provide something for those people to put on their resumes when they succeed, to help build their career path. I'm all for doing things for the good of the community, but a major reason IBM gives me considerable latitude to think about it that way is that I have my name on the MIME standard. It's true that I would have done the MIME work whether I was going to get credit for it or not, but I can tell you that having my name associated with it has made a big difference in my career. I'd like future standards writers to be able to aspire to a similar outcome. -- Nathaniel _______________________________________________ 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