IETF Logo Mail Archive

Re: IETF wiki expectations

Carsten Bormann <cabo@tzi.org> Tue, 22 November 2022 18:00 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF9DC1524D8 for <wgchairs@ietfa.amsl.com>; Tue, 22 Nov 2022 10:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ITis3si7Omhg for <wgchairs@ietfa.amsl.com>; Tue, 22 Nov 2022 10:00:00 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8B61C14CE2A for <wgchairs@ietf.org>; Tue, 22 Nov 2022 10:00:00 -0800 (PST)
Received: from client-0188.vpn.uni-bremen.de (client-0188.vpn.uni-bremen.de [134.102.107.188]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4NGsV51Q3qzDCd4; Tue, 22 Nov 2022 18:59:57 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Subject: Re: IETF wiki expectations
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <B30BB62E-D652-4FD6-9FF8-D302A22CBFAC@bluepopcorn.net>
Date: Tue, 22 Nov 2022 18:59:56 +0100
Cc: Christopher Wood <caw@heapingbits.net>, wgchairs@ietf.org
X-Mao-Original-Outgoing-Id: 690832796.65047-2ccb879f832da59948a89181798c5a3f
Content-Transfer-Encoding: quoted-printable
Message-Id: <0CBE1BDA-91FB-4192-A385-DCDDA15B0979@tzi.org>
References: <B7FD0738-12DB-468B-A6E6-C28E333D2C3E@heapingbits.net> <B30BB62E-D652-4FD6-9FF8-D302A22CBFAC@bluepopcorn.net>
To: Jim Fenton <fenton@bluepopcorn.net>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/yPDaWauED8Suu0Udu8q18KZ7VjQ>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2022 18:00:04 -0000

On 2022-11-22, at 18:54, Jim Fenton <fenton@bluepopcorn.net> wrote:
> 
> There are also wikis associated with some GitHub repos. I don’t know if any working groups are using those wikis, but that’s another place that might be used.

I find it weird to have a wiki without a defined purpose.
What purpose do people have in mind for a WG wiki?
(T2TRG and CoRE have a landing page, as well as several task-specific wikis on github.)

https://core-wg.github.io/
https://t2trg.github.io/
e.g., https://github.com/t2trg/wishi/wiki

Grüße, Carsten

v2.23.0 | Report a Bug | By Email