IETF Logo Mail Archive

Re: [Ietf-and-github] Seeking feedback on draft-ietf-git-using-github and Git tutorial

"Christopher Wood" <caw@heapingbits.net> Sat, 05 October 2019 11:21 UTC

Return-Path: <caw@heapingbits.net>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA2C1201E0 for <ietf-and-github@ietfa.amsl.com>; Sat, 5 Oct 2019 04:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=heapingbits.net header.b=K4yAH7gN; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=LuLW8FHU
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 T6T1bSwCMzu6 for <ietf-and-github@ietfa.amsl.com>; Sat, 5 Oct 2019 04:21:36 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECAD012022E for <ietf-and-github@ietf.org>; Sat, 5 Oct 2019 04:21:35 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 6B75521EAE; Sat, 5 Oct 2019 07:21:34 -0400 (EDT)
Received: from imap4 ([10.202.2.54]) by compute6.internal (MEProxy); Sat, 05 Oct 2019 07:21:34 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm2; bh=z43p2beydadNLyBXL0ZxQRi6Tnkn guywKeMHio3zwNQ=; b=K4yAH7gN6k+mVfxYHuxJLA8Ci8Ski1diOj8O0RsZt1l4 GU3gmYwNodFJplOVzcCPXnHjV0m44tFjc8jbFcLi4mAIC4EKu3cLmU1uzbVCkFYA jCvUQyebQ65v7R/lcIeA1NZYN7TIT7+dGDFKymAIAp+4V9apuN7NHR+cnNplWfu6 Wa6lb6OmZWFrEisitHj2N0udczqx1t+Qq4zz5v6wEzeHET83xOnPPfK1smmWEuFq E0qLDXoUnnTxUX7WbUSfucqysVo1O5DpxC7KG8MzkYbP5n1jQe2KcPgjYNR9qk+Q zSBbBpcKFi+jyGMzsVva+G2zBDgdUAEgfpOzd4foiA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=z43p2b eydadNLyBXL0ZxQRi6TnknguywKeMHio3zwNQ=; b=LuLW8FHURfrzfaPYmCe9Cp T9IKdKSU5w9JjE8CNyMcfbSWWWeqJ7U/wi6wFwUKGlQJ4DLapZ43XX3VaIrxNJfp L7ve5hon3oWxRicPyOF0yo+UBGe6zql8nKVPcqo7SnhhcpwGvdZpHbzoQKlE86mO lQCi37CIdpfv8Goysz0ZsidU65Cc8aUSiz/3AND42NQ5oH09pSTpMtZk1DuTsM+K c6Djel2i/riKIdkhtAA99cKNsufJ1KgxWCNQd9oigSyB6mb4k2k2T/dlXCKKBPte vT69/OtaShAVdydZ4vkUgNAzOhve48RLguJAevHY0cmFQWvKbOStJKxFWIeNcVYw ==
X-ME-Sender: <xms:vnyYXeCa-HDo3i-f0HvBen_2PGRyEygxcH61tM12_W0OmgvFQ3w73Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrheefgdeflecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenog fuuhhsphgvtghtffhomhgrihhnucdlgeelmdenucfjughrpefofgggkfgjfhffhffvufgt sehttdertderreejnecuhfhrohhmpedfvehhrhhishhtohhphhgvrhcuhghoohgufdcuoe gtrgifsehhvggrphhinhhgsghithhsrdhnvghtqeenucffohhmrghinhepghhithhhuhgs rdhiohdpghhithhhuhgsrdgtohhmpdhivghtfhdrohhrghenucfrrghrrghmpehmrghilh hfrhhomheptggrfieshhgvrghpihhnghgsihhtshdrnhgvthenucevlhhushhtvghrufhi iigvpedt
X-ME-Proxy: <xmx:vnyYXTUc4h094Ca3yfXsIePPIfebtNY80YTsVsrem4m_Y7fWUOb2dA> <xmx:vnyYXXNm-2ZMfbXPED56jV2ptux2UZcihsNSPw0P0lHasIKRN1Vkiw> <xmx:vnyYXRiIwYLZYYJno-W5-wVomEyiMW_Q8KYUwRL_1oO9rX9s7I-hmA> <xmx:vnyYXZsQxUJgDMxpgoNWvg-eMCqXTZIWG_RlKZQymIXD14J0vf5yyA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2224E3C00A1; Sat, 5 Oct 2019 07:21:34 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-360-g7dda896-fmstable-20191004v2
Mime-Version: 1.0
Message-Id: <0e19d992-07a5-4765-8c98-7e4e889d9d26@www.fastmail.com>
In-Reply-To: <BBCDB401-F370-419B-824D-74067EAD7F0F@apple.com>
References: <81307dc9-b275-4305-84d8-3a602ab271f5@www.fastmail.com> <BBCDB401-F370-419B-824D-74067EAD7F0F@apple.com>
Date: Sat, 05 Oct 2019 04:21:13 -0700
From: Christopher Wood <caw@heapingbits.net>
To: Tommy Pauly <tpauly@apple.com>
Cc: ietf-and-github@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/rg8qE7EN43waYudzi4v-PSVMwAM>
Subject: Re: [Ietf-and-github] Seeking feedback on draft-ietf-git-using-github and Git tutorial
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Oct 2019 11:21:45 -0000

On Fri, Oct 4, 2019, at 4:56 PM, Tommy Pauly wrote:
> The document looks good and reads well! I think the content all makes sense.
> 
> I did find a few nits in my review, which I've created a PR to fix 
> here: https://github.com/ietf-gitwg/using-github/pull/18

Thanks for taking the time to read and make improvements! The changes look good to me.

> The one content change I propose is to change:
> 
> "All repositories for working group documents MUST be public."
> 
> To:
> 
> "All repositories for Working Group documents within the Working Group
> organization MUST be public."
> 
> The sentence previously seemed to also include a requirement on working 
> group documents for working groups not officially using GitHub; I don't 
> think we can make a requirement for people who happen to use a private 
> GitHub repo to manage a working group document that's not officially 
> using GitHub.

Agreed. Good catch!

Best,
Chris

> 
> Thanks!
> Tommy
> 
> > On Oct 4, 2019, at 1:32 PM, Christopher Wood <caw@heapingbits.net> wrote:
> > 
> > Hi folks,
> > 
> > As we approach Singapore, it would be quite useful to get more feedback on draft-ietf-git-using-github, especially with the changes merged in September. You can view the editor's copy here:
> > 
> >   https://ietf-gitwg.github.io/using-github/draft-ietf-git-using-github.html
> > 
> > (I'm sure an updated version in the datatracker will come shortly.)
> > 
> > To accompany this document, we also put together a tutorial for people new to Git(Hub) and its use for IETF draft development:
> > 
> >   https://ietf-gitwg.github.io
> > 
> > It aims to help IETF contributors get started with the system, Martin's excellent i-d-template toolchain, and GitHub for the purposes of supporting the different Modes of Interaction described in draft-ietf-git-using-github.
> > 
> > Please have a look at this material and provide feedback! We would like to finish draft-ietf-git-using-github in (or before) Singapore.
> > 
> > Thanks,
> > Chris (chair hat on)
> > 
> > _______________________________________________
> > Ietf-and-github mailing list
> > Ietf-and-github@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-and-github
> 
>

v2.23.0 | Report a Bug | By Email