Re: [irsg] An IETF repository for working code in our protocols?

Vijay Gurbani <vijay.gurbani@gmail.com> Fri, 21 August 2020 23:01 UTC

Return-Path: <vijay.gurbani@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA0B3A1420 for <wgchairs@ietfa.amsl.com>; Fri, 21 Aug 2020 16:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDg2j1Mc4yOM for <wgchairs@ietfa.amsl.com>; Fri, 21 Aug 2020 16:01:22 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 829FF3A141A for <wgchairs@ietf.org>; Fri, 21 Aug 2020 16:01:15 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id i26so2913682edv.4 for <wgchairs@ietf.org>; Fri, 21 Aug 2020 16:01:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MqD6nrCUbN+qKsaMjZhHojqy3uu1GokQQor8f52Z5JA=; b=P9f9xHIX3QtBxEIPkz2cC+OPvCCHeRpJR9ERnYYJbbe15DTC4e/7afsduXIvg6EqQ5 Rq77WxJAI8SAbrGetwuyn+oc1qgLYbaMByqzk5YwutXEm/CXz5eU9Q75b2rK1Uo9cz7p nA8kEf7TCzHceFoqDWsOcVN+lta/kubHS+WJBicjBmuteIpned/S5Mwp+lT3yCA/rudR yCAUmrM7uB8tzlw/g6CPmbiHEOj6/il7DtKhXQWQeYGIzajtTerNJf43PlVmBaGZZreM TsRlArfAn7XJBwjAowZvO9Q3WfiQ2oSWOZbTb59pim3dRwIuRC7mUXcsYQikGW4YOaE+ V9sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MqD6nrCUbN+qKsaMjZhHojqy3uu1GokQQor8f52Z5JA=; b=YAOsfaq42W3kudHbxATFEpCjrpTPO0GbGIhOV7RAe7ZiXXCBGezlUUj8X55cpIrmvA mgPUvcJUBkdJD5JGR5PAnt/wTQprsOfUy5h8ArQKVw9rUw9xu8pyfFjP1xhDwbIn5JtK WAZMXmACMYpMFNNijA+UWQCAEZqXNAAWQLi7oVd2B2hiMNnZynJkEkNMBOd4Hnbe79Bw PUptqHqsgRoXIPHHPCyLpZ1a/9E4PcIrzbnxopfSTRhNBdmL9NzeFs8Ne2UItXM+CG0j YomXAYJ9BVGHoxYL5XBngpIcUSWpuRRmrSIf/t2MVMAy5tT/RsUUzphRKd7W81MmxJtc sVgA==
X-Gm-Message-State: AOAM533nghOrPSXv2j8oZr7lCxinpnP07RQBh10rrhbQqGNveba7nr8M Cn6PPhxGEbhV2FGzmrecSfjds5c8C1VubA8cGUs+uX8n
X-Google-Smtp-Source: ABdhPJw93aon/uGWJi9aAKKkFDa5B/t7lazzn07sbknmKhA/xny8ZbzjsRwpNI1v1HivYwDUpGyJo2aWwocAhiVMRTU=
X-Received: by 2002:a50:cbc3:: with SMTP id l3mr5104504edi.58.1598050873762; Fri, 21 Aug 2020 16:01:13 -0700 (PDT)
MIME-Version: 1.0
References: <CAMMTW_+Di=ZBJFLNPaVK6f3w3Yq-V-qau8G_rfGt96SX_aYAAA@mail.gmail.com> <8193D927-DDA8-4C74-BBD3-1AF6C9AFE98B@mnot.net> <CAMMTW_KVRVaz0tUXLaAQH2V0bY2ws+CZDy=XUKC=Jc3aiAU58w@mail.gmail.com> <5569BEF0-1782-4D93-8BB1-276ECD42D6ED@episteme.net> <15396.1598028610@localhost> <152C087A-2ABD-4B53-A375-F692BCDD8681@isoc.org> <1478.1598050327@localhost>
In-Reply-To: <1478.1598050327@localhost>
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Fri, 21 Aug 2020 18:01:01 -0500
Message-ID: <CAMMTW_JcrqPh-Py4-CQ6=fXpHk=dFpH-LjvjbZkdzrqFuaKqeA@mail.gmail.com>
Subject: Re: [irsg] An IETF repository for working code in our protocols?
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Jane Coffin <coffin@isoc.org>, IETF WG Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a9e8b705ad6b36de"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/2ZduAK0zlOLBAi0ncPHgCm0cKoA>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2020 23:01:25 -0000

Dear Michael, No, I am afraid that was not the proposal.  It is not about
educating coders.  My apologies, I am somewhat caught up in in other
matters right now, but I will reply later with more detail.

Thanks.


On Fri, Aug 21, 2020, 5:53 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Jane Coffin <coffin@isoc.org> wrote:
>     > I hope I do not sound too clueless, but is the objective in creating
> a
>     > repository to educate future coders?
>
> That was the proposal.
> Some kind of archive.
> Beyond the license issue and the appearance of endorsement,
> there are many other issues.
>
> It's not just getting a stack of disk space.
> The expensive issue is, in my opinion, figuring out how things would be
> nominated to go in.
>
> I don't think it has value.
>
> The codestand project was about matching WG protocol experts with
> implementors (imagined to be mostly students at various maturity levels)
> who
> are trying to do something reseachy with the protocol.
> More running code.
>
>     > I ask these questions sincerely and with apologies if this is super
> clear and I missed the context.
>
>
>
>
>     > Pete Resnick <resnick@episteme.net> wrote:
>     >>>> I also don't think that it's necessary, once a protocol is
> successful;
>     >>>> after broad deployment, people don't need to go searching for
>     >>>> implementations. It *is* useful when a project is starting, to
> help early
>     >>>> implementers find each other, though.
>     >>>
>     >>> Yes, agreed!  The idea would be light the fire of widespread
> implementation
>     >>> by the kindling (code) that tracked the I-D as it became an RFC.
>
>     >> It might be useful (for you all and for the IAB program) to look at
> the
>     >> codestand (originally codematch) project, both its successes and its
>     >> failures. The email lists are still in the archives. I followed it
> at the
>     >> beginning, but don't know much about it other than it was in part
> trying to
>     >> help match up implementors with standards.
>
>     > It was more a mentee/mentor matching around the code/standard
> situation.
>     > I get the impression that the effort just ran out of oomph.
>
>     > --
>     > Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
>     > -= IPv6 IoT consulting =-
>
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>