IETF Logo Mail Archive

Re: IETF wiki expectations

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 22 November 2022 17:32 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 0FF51C1526F2 for <wgchairs@ietfa.amsl.com>; Tue, 22 Nov 2022 09:32:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 igTEaTcdMecH for <wgchairs@ietfa.amsl.com>; Tue, 22 Nov 2022 09:32:36 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 382EFC1526ED for <wgchairs@ietf.org>; Tue, 22 Nov 2022 09:32:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id E05BF1800D; Tue, 22 Nov 2022 12:58:11 -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 32f6oflbe9Jl; Tue, 22 Nov 2022 12:58:10 -0500 (EST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id D4AEF1800C; Tue, 22 Nov 2022 12:58:10 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1669139890; bh=eyF5aAcTf5H4oXA7WxUbazpGyHGYS52o2Pub5itZ/0A=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=d8/AXppuoycsXRwZBq5kWbeHGUYep+9SMTXzcWYfCV9Z0q8QJ9aAgOygnw2muGdwJ 0iRJlHpJx4nyWK4NqO3QSok8g84V4TepBk7/s31c5WlEzf44rC9yckKIWrmPX0RR22 fM3iZFCGrgbnuX4XK6MAiTbe5eD8StbojjoG2R3KqzMuXxXcDpLRMQ/vfPSLK7CrWG Rwk5BlhGElB6LnCNxk1528WW1l2OZuUc/JgFZ9itnW321IwCWeqrReozhooR27U9eh xiQy1I0er3fROw1TmSQXfiGARRKA3EYA6hgbKhZs/fK2L4IISIf5KLCc5Bf8ZVY3Uk arwX74RG+OE9Q==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 202131FD; Tue, 22 Nov 2022 12:32:34 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christopher Wood <caw@heapingbits.net>
cc: wgchairs@ietf.org
Subject: Re: IETF wiki expectations
In-Reply-To: <B7FD0738-12DB-468B-A6E6-C28E333D2C3E@heapingbits.net>
References: <B7FD0738-12DB-468B-A6E6-C28E333D2C3E@heapingbits.net>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.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: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 22 Nov 2022 12:32:34 -0500
Message-ID: <31617.1669138354@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/X3wAyx1JUMEGSiJF3YPbPy-RN9M>
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 17:32:41 -0000

Christopher Wood <caw@heapingbits.net> wrote:
    > Perhaps this has been discussed here before, but I’m wondering if there
    > are expectations for how WGs should use the IETF wiki:

    >    https://wiki.ietf.org

    > Some WGs have pages filled out here, whereas other groups, like HTTP,
    > maintain a separate site for that information:

    >    https://httpwg.org

    > Are we generally operating under a “do what’s best for your WG" model,
    > or should each WG be using this wiki?

Yes :-)

I think that every WG should have a short page on wiki.ietf.org, even if that page
just points to some external site.
(or, I don't think that WGs should be forced to use the new wiki if they
don't want to.  OTH, I found the old wiki very hard to use as a WG, and I
think others did too.  The ability to maintain your wiki pages via git is a
big boon to me)

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email