Re: [Cacao] [EXT] Re: [EXT] RE: Charter

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 18 June 2019 22:19 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: cacao@ietfa.amsl.com
Delivered-To: cacao@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFBC81202D9 for <cacao@ietfa.amsl.com>; Tue, 18 Jun 2019 15:19:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 rXTYwfb5nBmR for <cacao@ietfa.amsl.com>; Tue, 18 Jun 2019 15:19:21 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CDF912029C for <cacao@ietf.org>; Tue, 18 Jun 2019 15:19:20 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [209.82.62.2]) by relay.sandelman.ca (Postfix) with ESMTPS id 5094D1F450; Tue, 18 Jun 2019 22:19:18 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 1E0341328; Tue, 18 Jun 2019 18:19:23 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Bret Jordan <jordan.ietf@gmail.com>, cacao@ietf.org
In-reply-to: <A7038D6C-C1C3-4B6A-B928-AC87F7A87AFC@gmail.com>
References: <BYAPR16MB30133C3DAF3CF2060CE4B565EDEA0@BYAPR16MB3013.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302EAA890F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <BYAPR16MB30137AC9C00633E80C7C8D65EDEA0@BYAPR16MB3013.namprd16.prod.outlook.com> <779CCF55-FABB-4BA1-9D84-1D9761A32944@tzi.org> <BYAPR16MB30139D44233E0256099264DCEDEA0@BYAPR16MB3013.namprd16.prod.outlook.com> <25088b69-1225-3f3c-b0e2-38e25f1f48fb@article19.org> <A7038D6C-C1C3-4B6A-B928-AC87F7A87AFC@gmail.com>
Comments: In-reply-to Bret Jordan <jordan.ietf@gmail.com> message dated "Tue, 18 Jun 2019 16:30:41 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 18 Jun 2019 18:19:23 -0400
Message-ID: <6130.1560896363@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cacao/fqniXwVIKkfnvj-J_15caP7JTg0>
Subject: Re: [Cacao] [EXT] Re: [EXT] RE: Charter
X-BeenThere: cacao@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Collaborative Automated Course of Action Operations <cacao.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cacao>, <mailto:cacao-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cacao/>
List-Post: <mailto:cacao@ietf.org>
List-Help: <mailto:cacao-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cacao>, <mailto:cacao-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2019 22:19:24 -0000

(why am I top-quoting?)
Bret, Carsten is not objecting to Google Docs.

Carsten is asking you to be explicit in saying that including people who
can't/won't do github is important.
Google Docs suffers from a lack of attribution for the text after the
"suggestion" is accepted.
Github suffers from way too much attribution.

I don't object to using Google Docs, but please make sure you know how to use
it well.  If you are editing an Internet Draft in Markdown format, then some
stuff will look weird, and people will make suggestion that can not be
implemented.

I don't think having it on etherpad is helpful, btw.

Bret Jordan <jordan.ietf@gmail.com> wrote:
    > That is an option. Just so you know, Google Docs does not require
    > anything other than a web browser. If you go this url, just like an
    > ether pad, you will see the document and suggestions and comments.

    > https://docs.google.com/document/d/1fTN0uilpBVx6CwaGxj8SBKG4PqG7DceInU9RgLz9pRo/edit#heading=h.wh8etuclav2g

    > Thanks, Bret PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE
    > 7415 0050 "Without cryptography vihv vivc ce xhrnrw, however, the only
    > thing that can not be unscrambled is an egg."

    >     On Jun 18, 2019, at 4:26 PM, Amelia Andersdotter
    > <amelia@article19.org> wrote:



    >     On 2019-06-18 16:05, Bret Jordan wrote:


    >         Carsten,


    >         I appreciate your comments. However, from our experience, with
    > a large group of people that are in both camps, editing specs in Google
    > docs proves to be the easiest solution for all. So it is not about
    > preferring one group over another. It is about what proves to be the
    > easiest and fastest to enable as many people as possible to get work
    > done quickly and efficiently.




    >     How about making it temporarily available on some form of etherpad?
    > They are normally accessible to everyone and rely only on browser
    > functions.


    >     best regards,

    >     amelia


    >         Bret


    >         ------------------------------------------------------------------------

    >         *From:* Carsten Bormann <cabo@tzi.org> *Sent:* Tuesday, June
    > 18, 2019 7:41:20 AM *To:* Bret Jordan *Cc:*
    > mohamed.boucadair@orange.com; cacao@ietf.org *Subject:* [EXT] Re:
    > [Cacao] [EXT] RE: Charter

    >         On Jun 18, 2019, at 14:24, Bret Jordan
    > <Bret_Jordan=40symantec.com@dmarc.ietf.org> wrote:


    >             Using Github will prevent people from helping, or will
    > limit people


    >         to only those that understand how to use Github and have access
    > to Github. Resolving comments and suggestions via Github is
    > significantly harder than Google Docs.

    >         My comment here is kind of off-topic, but… The statement you
    > are making here is that one group of contributors (those that can stand
    > collaborating on a document with the limited means Google Docs) is more
    > important than another group of contributors (those that are used to
    > software development workflows).  While that may very well be, I think
    > it is important to make decisions like this explicitly.  (I personally
    > believe that this effort could benefit from strong participation by
    > people who write code.)

    >         Grüße, Carsten




    >     --
    >     Amelia Andersdotter Technical Consultant, Digital Programme Chair,
    > RCM TIG, IEEE 802.11

    >     ARTICLE19 www.article19.org

    >     PGP: 3D5D B6CA B852 B988 055A 6A6F FEF1 C294 B4E8 0B55

    >     --
    >     Cacao mailing list Cacao@ietf.org
    > https://www.ietf.org/mailman/listinfo/cacao




    > ----------------------------------------------------
    > Alternatives:

    > ----------------------------------------------------
    > --
    > Cacao mailing list Cacao@ietf.org
    > https://www.ietf.org/mailman/listinfo/cacao

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-