IETF Logo Mail Archive

Re: IETF wiki expectations

Joel Halpern <jmh@joelhalpern.com> Tue, 22 November 2022 18:03 UTC

Return-Path: <jmh@joelhalpern.com>
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 A41CDC15258A for <wgchairs@ietfa.amsl.com>; Tue, 22 Nov 2022 10:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.099 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 bnAbxbjM0ilO for <wgchairs@ietfa.amsl.com>; Tue, 22 Nov 2022 10:03:38 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 D4B6CC14CE2A for <wgchairs@ietf.org>; Tue, 22 Nov 2022 10:03:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4NGsZL38GCz6Gs2r; Tue, 22 Nov 2022 10:03:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1669140218; bh=ignW4Zk8EFlFbjPVsxUV8HUTvCNypO1/jl6pIx1DAR8=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=mwXizL6Ls2SsYh/f9DUiRLKfVgzYxGRVwYFgtkdK45vMK8eRgK1lrNCd4tFQgneMD +yQjwR7S1xx1/mzGg5JmbdvdzG6u4xcqBvCw3B+JK43bu3NpvnX0O+SFp8a9qM/DvG Rz/iNwFXOR+60Z1iB0KfGEpPLFyUrF0lp9uIf0yc=
X-Quarantine-ID: <AojoR6ygL8hx>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.21.74] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4NGsZK68ZGz6Gs2k; Tue, 22 Nov 2022 10:03:37 -0800 (PST)
Message-ID: <ad7d8c6c-0cbd-8ea8-8fcb-d10913fb8a89@joelhalpern.com>
Date: Tue, 22 Nov 2022 13:03:36 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
Subject: Re: IETF wiki expectations
Content-Language: en-US
To: Carsten Bormann <cabo@tzi.org>
Cc: wgchairs@ietf.org
References: <B7FD0738-12DB-468B-A6E6-C28E333D2C3E@heapingbits.net> <B30BB62E-D652-4FD6-9FF8-D302A22CBFAC@bluepopcorn.net> <0CBE1BDA-91FB-4192-A385-DCDDA15B0979@tzi.org>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <0CBE1BDA-91FB-4192-A385-DCDDA15B0979@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/8PQ4o1DE7okNTBeGqVz0-3-mQ8Q>
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:03:43 -0000

We use the spring wiki for several things.

The newest use is to point to pages where we list WG policies the chairs 
have adopted with WG agreement.

There is also a long section to track request from participants for WG 
adoption / WG last call, because we got way behind on that.

Also, if folks want to have pages to track implementation information 
aboth drafts or RFCs (in addition to what will be in the drafts) we can 
create those.

Yours,

Joel

On 11/22/2022 12:59 PM, Carsten Bormann wrote:
> 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