IETF Logo Mail Archive

Re: [Cellar] github org name

Michael Richardson <mcr@sandelman.ca> Mon, 23 November 2020 20:16 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5D43A0B56 for <cellar@ietfa.amsl.com>; Mon, 23 Nov 2020 12:16:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 bP7t9lze-gCm for <cellar@ietfa.amsl.com>; Mon, 23 Nov 2020 12:16:12 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F3AE3A0AD8 for <cellar@ietf.org>; Mon, 23 Nov 2020 12:16:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 279EB389D2; Mon, 23 Nov 2020 15:17:26 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3khwdUwAlA4A; Mon, 23 Nov 2020 15:17:25 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 998E5389CC; Mon, 23 Nov 2020 15:17:25 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id ECC80F22; Mon, 23 Nov 2020 15:16:09 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Rice <dave@dericed.com>
cc: Jerome Martinez <jerome@mediaarea.net>, Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
In-Reply-To: <C5F62333-7EAB-4DDA-9E73-8FE8B44D689F@dericed.com>
References: <30862.1606093637@localhost> <89bcca5b-b6ba-c8dd-fe7b-eca1e9330843@mediaarea.net> <C5F62333-7EAB-4DDA-9E73-8FE8B44D689F@dericed.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10206.1606162569.1@localhost>
Date: Mon, 23 Nov 2020 15:16:09 -0500
Message-ID: <10207.1606162569@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/AlzVodqj8T2FYB-wG6Rb3XuMuWI>
Subject: Re: [Cellar] github org name
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2020 20:16:14 -0000

Dave Rice <dave@dericed.com> wrote:
    >> On Nov 23, 2020, at 1:46 AM, Jerome Martinez <jerome@mediaarea.net>
    >> wrote:
    >>
    >> On 23/11/2020 02:07, Michael Richardson wrote:
    >>> RFC8875 suggests github organizations be named "ietf-wg-XXXX".  Our
    >>> is named cellar-wg.
    >>>
    >>> Renaming is not required, but it seems like a good idea to me.  All
    >>> of RFC8874/8875 are essentially guidelines, best current practices,
    >>> btw.
    >>
    >> I am in favor of the renaming.

    > +1

it is done: https://github.com/ietf-wg-cellar/
I may re-register the old name with redirects.  Maybe.

    >>> Github says that almost everything will be redirected (repository
    >>> access in particular), but not https://github.com/cellar-wg itself.
    >>> They list that the biggest threat is that old name could get squatted
    >>> on!
    >>
    >> Sad but we mostly link on repositories so better to do it now than
    >> later.
    >>
    >>> In looking at the settings, I noticed that we could upload a logo.
    >>> Does EBML/FFV1/Matroska have a logo?  Some IETF WGs have created a
    >>> logo.
    >>
    >> We could use the Matroska one while waiting for finding a more generic
    >> one.

    > Do logos play any role for documents in the IETF beyond using it in the

None :-)

v2.23.0 | Report a Bug | By Email