Re: How IETF treats contributors
ned.freed@mrochek.com Sat, 04 September 2004 06:11 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 CAA24779; Sat, 4 Sep 2004 02:11:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3Tor-0002Gp-RM; Sat, 04 Sep 2004 02:14:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3Th4-0008Kt-UA; Sat, 04 Sep 2004 02:06:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3Tds-0006Pl-BS for ietf@megatron.ietf.org; Sat, 04 Sep 2004 02:03:18 -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 CAA16091 for <ietf@ietf.org>; Sat, 4 Sep 2004 02:03:14 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from mauve.mrochek.com ([209.55.107.55]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3Tgb-00029O-TG for ietf@ietf.org; Sat, 04 Sep 2004 02:06:07 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01LEG1QVHRBK00005R@mauve.mrochek.com> for ietf@ietf.org; Fri, 03 Sep 2004 23:03:02 -0700 (PDT)
Date: Fri, 03 Sep 2004 22:57:49 -0700
In-reply-to: "Your message dated Fri, 03 Sep 2004 22:37:21 -0400" <5905840A-FE1B-11D8-8364-000A9571873E@guppylake.com>
To: Nathaniel Borenstein <nsb@guppylake.com>
Message-id: <01LEG4NBM0KA00005R@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="us-ascii"; format="flowed"
Content-transfer-encoding: 7bit
References: <20040830090627.GA22982@danisch.de> <v04220806bd5962148387@[10.0.1.13]> <5905840A-FE1B-11D8-8364-000A9571873E@guppylake.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: John Day <day@std.com>, 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.3 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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 completely agree with this assessment. > 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 Being another coauthor of MIME hasn't exactly hurt my prospects either. Ned _______________________________________________ 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