Non email WG participation

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 21 July 2016 05:28 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BD712DA0D for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2016 22:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 x_jnASvIpIHE for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2016 22:28:07 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 758F912D9F1 for <ietf@ietf.org>; Wed, 20 Jul 2016 22:28:07 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id x1so64828668qkb.3 for <ietf@ietf.org>; Wed, 20 Jul 2016 22:28:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to; bh=AReK1cFsqjSGtaG9ogYZNrEK2QbdP2SchxEJugOoqi4=; b=lCQWF2UUrCLZe5PXz9wDqA31vF49oBZDeUfTpbJZ1Ek8PtEJ9TPU2oaw7Kq80ekIgq qlKZDOyODatpePRJE95p6eV5dlP44VvV+/xGpHtf0qLEteg22Q6t2soQ7qyxF1t3XdQR KsuF3RM5LDeOkmPlX93IpN2cYGUiVKUHhxJp/LPIoD6BiYMfSxL0D9zVRMCzDgl1j9K3 q+Vs//hRsfTkkqRoNd1LsAS57nprhP++zSi2da8sKvc3fZG+nFf8kNanS6fhmVTOpb9T DcnYNoqb50NVnxHju0+q1huTUGaXnPNPsaIpf57ozPdmKBAQfYEV2Q4IPbsvQ8/J3XJI gbfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=AReK1cFsqjSGtaG9ogYZNrEK2QbdP2SchxEJugOoqi4=; b=OCTSb3K4tZif5RjsS5BFa7CnRYmuE8Da+u1OWVK89QC36h1AlhNAAdsWWoLrJKVjJP vKeo+4KcudLUt7LAIzLRHq3ruqFUNLMKOTM9vePUnHwenPPmP/FiegGUhmUgWm8KfkEU m+DZ3ffYdfklFOPp3IIgQCp3c+jK3YiDR8/zL9hxwq/vnsVh2AdWKzESlBtCekgt5BOF v+tj/TjeO4HLCYdp4513Nl1+FeS/pgzDTryasy6IKSnUvrvjvrwW85m5HT3eCurZNAhO m7fOUtjjGTRMtiUsGQLpO/8rkNxctuZtNoZqS7fN8OcdE/JWvflWPu2ege4VPKTwemP4 Zlrw==
X-Gm-Message-State: ALyK8tLdF2KIcQ1rBukk3j0QMrxG70Nqs/4AaNCd1duXg+ZVHayC6nZgcnu2GpLImdtVAG3qpoH923ydSPUnEg==
X-Received: by 10.233.232.23 with SMTP id a23mr66214707qkg.25.1469078886407; Wed, 20 Jul 2016 22:28:06 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.55.16.106 with HTTP; Wed, 20 Jul 2016 22:28:05 -0700 (PDT)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 21 Jul 2016 07:28:05 +0200
X-Google-Sender-Auth: jO4ksAfGgE6-G4Q8SEiI738BRIc
Message-ID: <CAMm+LwjnvVG7k2Mk70h5YGtURkK3r2oCYQgTy6a=iVkC-7i3WA@mail.gmail.com>
Subject: Non email WG participation
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0344522be57e05381e950d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1S3dhsdhyY6e5CzlI4hsEoBZgqI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2016 05:28:09 -0000

As I mentioned in the plenary:

* Innovation in collaboration tools is good.

* Excluding people who don't know that the tools are in use or where they
are or what steps are required to gain access and/or use them is bad.

* There is a risk that key parts of the documentary record will be lost.

I therefore suggest that

* The charter pages specify the locations for any data repositories /
collaboration tools / etc being used by a WG and if necessary the contact
information for the administrator.

* If a WG wants to use a collaboration tool other than email, that they
document how to use the tool, obtain credentials, etc. in an Internet Draft
or reference an RFC giving the same information.

No, grovelling through mailing list archives to find the necessary
information is not the same thing, nor is it a reasonable thing to ask.

* The IETF should make sure that all IETF documents are being tracked and
digitally signed on a regular basis as is currently done for RFCs.

Yes there are differences in legal jurisdictions but I am not aware of any
jurisdiction in which it is possible to submit a document that can't be
found. Locating copies of IETF mailing lists from the 1990s takes a non
trivial amount of time and effort. We have Note Well for a good reason and
maintaining records is another good reason.


Over the long term, I would like to see the use of tools hosted by the IETF
to be encouraged. This allows for credentials to be shared across WGs and
reduces the need to learn slightly different sets of commands for slightly
different tools. I was using source code managers in the 1980s, they don't
work like Git.

Similarly, while Wikis are great, not all Wikis use the same markup. And
this gets very tedious when cut and paste is attempted.