IETF Logo Mail Archive

Re: [Cellar] github org name

Dave Rice <dave@dericed.com> Mon, 23 November 2020 15:56 UTC

Return-Path: <dave@dericed.com>
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 909803A08BD for <cellar@ietfa.amsl.com>; Mon, 23 Nov 2020 07:56:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.654
X-Spam-Level:
X-Spam-Status: No, score=0.654 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.652, URIBL_BLOCKED=0.001] autolearn=no 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 1mkuMck_8h6Q for <cellar@ietfa.amsl.com>; Mon, 23 Nov 2020 07:56:41 -0800 (PST)
Received: from server172-4.web-hosting.com (server172-4.web-hosting.com [68.65.122.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 557BD3A0880 for <cellar@ietf.org>; Mon, 23 Nov 2020 07:56:41 -0800 (PST)
Received: from pool-100-37-115-144.nycmny.fios.verizon.net ([100.37.115.144]:56148 helo=[192.168.1.152]) by server172.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <dave@dericed.com>) id 1khECi-003ueI-CT; Mon, 23 Nov 2020 10:56:40 -0500
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Dave Rice <dave@dericed.com>
In-Reply-To: <89bcca5b-b6ba-c8dd-fe7b-eca1e9330843@mediaarea.net>
Date: Mon, 23 Nov 2020 10:56:35 -0500
Cc: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5F62333-7EAB-4DDA-9E73-8FE8B44D689F@dericed.com>
References: <30862.1606093637@localhost> <89bcca5b-b6ba-c8dd-fe7b-eca1e9330843@mediaarea.net>
To: Jerome Martinez <jerome@mediaarea.net>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-OutGoing-Spam-Status: No, score=-0.2
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server172.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dericed.com
X-Get-Message-Sender-Via: server172.web-hosting.com: authenticated_id: dave@dericed.com
X-Authenticated-Sender: server172.web-hosting.com: dave@dericed.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/yask159bj38cc9xaCAVIoAPdQus>
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 15:56:43 -0000

Hi,

> 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

>> 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 GitHub repository?
Dave

v2.23.0 | Report a Bug | By Email