From nobody Thu Jun 24 09:43:38 2021 Return-Path: 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 F14863A2364 for ; Thu, 24 Jun 2021 09:43:36 -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 jqQxdf1jgo57 for ; Thu, 24 Jun 2021 09:43:32 -0700 (PDT) Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 028783A2363 for ; Thu, 24 Jun 2021 09:43:31 -0700 (PDT) Received: by mail-yb1-xb2f.google.com with SMTP id i4so181444ybe.2 for ; Thu, 24 Jun 2021 09:43:31 -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=nCGiafbVo+4dbPNmbc8aC6ySUPuS3O1MmlcjYE0tpjY=; b=S33VpbmACjlcj4ybDDgXOgr+HZBzeq4psyzWpvA7IfX5NmnBvkh0UDyGD+q6BiDYq6 kv+henCBZdfwLXNizzUazZz3MbYMbnxu6k9XW05fztFnhMSzh3iKErLR3lQ39qHHFQSg u1R1G2S61EQ2lN7GSn22Plf/Tpurtcbxcgxr5DFT3HgnoBuu/bh6Ul1168snTPLrVkeM 3uxagb2kf6/KkNeuydQ6btYVC+KRh9+Uy15oXYB8qYs6PBE+PoQ1q9TjqFAdrE3ahB9q qmXF7PR5qD6/ZTtt9Q/SEgsBYemhsrR9Q/GxmwpqFZjfBi4UC7W9ULUVr6lUrWtYTP0A ol6A== 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=nCGiafbVo+4dbPNmbc8aC6ySUPuS3O1MmlcjYE0tpjY=; b=lBaP/W+JKRVXhGVBmZwwrYATBfGWI+jdY/h9ct+t90AQpGqMdObEWdgFuJqFR3O1QX HJKlSiusERQr4KUjamp80+s0iPjMKouSH2Gdu50W+XT+tBJ7w8/bz04QikLo7g05yyfy L2/IeV+NZwwsb5BZb/WG4aCNvb5OdJR95m3v6tfWuGiQWN6SzkpUHjPL6jT8cN50tAhR xOBFsS8k/2X2wkJvVjyl73voXj5/DQvBTKQTxg0oYiHtw8faKD+hXBjh1fpNFkWJ2otP ogCIMmDIYva8mxpnn7hr2/ra8qIqg1FFxoqQEWGA1csrL3SJ6jvclSqBhZbP132ErJyw koJg== X-Gm-Message-State: AOAM532wVLKwrkcFEGbCTXPVOYyvgI4wcuF7W0bzyDMccBuObcphwT5s Pe0D3+M+6p21s+oig9d6QY37Y3W695RKJm5j4UI= X-Google-Smtp-Source: ABdhPJzktu9CzgC3dTatXyv7z3slstjR8OMXHd0nbu9GJU4OW+wss0tmBdQLXYq1wkz7mPNBAKph2ZGuIZuMuZRTUmQ= X-Received: by 2002:a25:3749:: with SMTP id e70mr6319757yba.53.1624553010507; Thu, 24 Jun 2021 09:43:30 -0700 (PDT) MIME-Version: 1.0 References: <122FF431-7981-4D29-820F-3C16C7F723AB@icann.org> In-Reply-To: From: Spencer Dawkins at IETF Date: Thu, 24 Jun 2021 11:43:04 -0500 Message-ID: To: tjw ietf Cc: "ietf-and-github@ietf.org" Content-Type: multipart/alternative; boundary="0000000000001c30de05c585b9ed" Archived-At: Subject: Re: [Ietf-and-github] [Ext] GIT WG disposition 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2021 16:43:37 -0000 --0000000000001c30de05c585b9ed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Just to follow up on this ... On Mon, Aug 31, 2020 at 10:21 AM tjw ietf wrote: > Ok with closing the wg > > I think we=E2=80=99ll see chairs looking for some initial guidance. > > Reconsider the mailing list in 9 months? > That should be two meeting cycles. I think we may see chairs, and even non-chairs who might someday be chairs, asking for non-initial guidance, too. I opened https://github.com/martinthomson/i-d-template/issues/293 in the very much appreciated i-d-template repo about "interesting" things that were happening to our draft in the MOPS repo with Circle CI, and that discussion (again, much appreciated) morphed into a discussion of whether CircleCI is helpful for continuous integration, or whether we (in this case, MOPS) should be moving to Github Actions. To be clear, I'm not talking about a recommendation that IETF WG-owned repos should all do something, because I don't believe in Santa Claus, either. I'm only asking about where people can be aware of what other WGs are doing, and how they are doing it, so WG chairs don't have to figure out what to do and how to do it, on their own. I can't be the only person who copies repos to set up other repos, rather than investigating how to best set up a repo from scratch each time ... I THINK this mailing list could/would be an appropriate place to have a discussion about that, but wanted to ask what other people think. Best, Spencer > Tim > > Sent from my iPhone > > > On Aug 31, 2020, at 10:35, Paul Hoffman wrote: > > > > =EF=BB=BFOn Aug 31, 2020, at 7:33 AM, Lars Eggert wro= te: > >> > >> Hi, > >> > >>> On 2020-8-31, at 15:52, Alissa Cooper wrote: > >>> The chairs and I would like to close the group while keeping the > mailing list open. Please respond if you have any concerns about this, > otherwise I=E2=80=99ll hit the close button next week. > >> > >> I have a mild general preference to also see mailing lists close when > WGs go away - do we expect significant future discussion here? > > > > Personally, I do expect that there will be bursts of "how do I do $x", > "my WG wants to do $y, is that acceptable", and so on. Not enough for a > chartered WG, but enough for a mailing list. > > > > --Paul Hoffman_______________________________________________ > > Ietf-and-github mailing list > > Ietf-and-github@ietf.org > > https://www.ietf.org/mailman/listinfo/ietf-and-github > > _______________________________________________ > Ietf-and-github mailing list > Ietf-and-github@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-and-github > --0000000000001c30de05c585b9ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just to follow up on this ...

On Mon, Aug = 31, 2020 at 10:21 AM tjw ietf <tjw= .ietf@gmail.com> wrote:
Ok with closing the wg

I think we=E2=80=99ll see chairs looking for some initial guidance.=C2=A0 <= br>
Reconsider the mailing list in 9 months?
That should be two meeting cycles.

I think = we may see chairs, and even non-chairs who might someday be chairs, asking = for non-initial guidance, too.=C2=A0

I opened=C2= =A0htt= ps://github.com/martinthomson/i-d-template/issues/293 in the very much = appreciated i-d-template repo about "interesting" things that wer= e happening to our draft in the MOPS repo with Circle CI, and that discussi= on (again, much appreciated) morphed into a discussion of whether CircleCI = is helpful for continuous integration, or whether we (in this case, MOPS) s= hould be moving to Github Actions.=C2=A0

To be cle= ar, I'm not talking about a recommendation that IETF WG-owned repos sho= uld all do something, because I don't believe in Santa Claus, either. I= 'm only asking about where people can be aware of what other WGs are do= ing, and how they are doing it, so WG chairs don't have to figure out w= hat to do and how to do it, on their own.=C2=A0

I = can't be the only person who copies repos to set up other repos, rather= than investigating how to best set up a repo from scratch each time ...=C2= =A0

I THINK this mailing list could/would be an ap= propriate=C2=A0place to have a discussion about that, but wanted to ask wha= t other people think.

Best,

Spencer
=C2=A0
Tim

Sent from my iPhone

> On Aug 31, 2020, at 10:35, Paul Hoffman <paul.hoffman@icann.org> wrote:
>
> =EF=BB=BFOn Aug 31, 2020, at 7:33 AM, Lars Eggert <lars@eggert.org> wrote:
>>
>> Hi,
>>
>>> On 2020-8-31, at 15:52, Alissa Cooper <alissa@cooperw.in> wrote:
>>> The chairs and I would like to close the group while keeping t= he mailing list open. Please respond if you have any concerns about this, o= therwise I=E2=80=99ll hit the close button next week.
>>
>> I have a mild general preference to also see mailing lists close w= hen WGs go away - do we expect significant future discussion here?
>
> Personally, I do expect that there will be bursts of "how do I do= $x", "my WG wants to do $y, is that acceptable", and so on.= Not enough for a chartered WG, but enough for a mailing list.
>
> --Paul Hoffman_______________________________________________
> Ietf-and-github mailing list
> Ietf-and= -github@ietf.org
> https://www.ietf.org/mailman/listinfo/iet= f-and-github

_______________________________________________
Ietf-and-github mailing list
Ietf-and-gith= ub@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-and-= github
--0000000000001c30de05c585b9ed--