[Teas] Re: TEAS wiki

Adrian Farrel <adrian@olddog.co.uk> Fri, 08 November 2024 13:48 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C94EC180B7D; Fri, 8 Nov 2024 05:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=olddog.co.uk
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 z9z8xyQmVEzS; Fri, 8 Nov 2024 05:48:19 -0800 (PST)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C853C1CAF43; Fri, 8 Nov 2024 05:48:16 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta6.iomartmail.com (8.14.7/8.14.7) with ESMTP id 4A8DmEDg016185; Fri, 8 Nov 2024 13:48:14 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 19B014604B; Fri, 8 Nov 2024 13:48:14 +0000 (GMT)
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 03B0D4603D; Fri, 8 Nov 2024 13:48:14 +0000 (GMT)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS; Fri, 8 Nov 2024 13:48:13 +0000 (GMT)
Received: from LAPTOPK7AS653V (dhcp-8d06.meeting.ietf.org [31.133.141.6]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.7/8.14.7) with ESMTP id 4A8DmDPC029250 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 8 Nov 2024 13:48:13 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: chen.ran@zte.com.cn, teas@ietf.org
References: <20240815144630855zjWOqjazyNbO0azQ-H4NI@zte.com.cn>
In-Reply-To: <20240815144630855zjWOqjazyNbO0azQ-H4NI@zte.com.cn>
Date: Fri, 08 Nov 2024 13:48:13 -0000
Organization: Old Dog Consulting
Message-ID: <016701db31e4$db4617b0$91d24710$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0168_01DB31E4.DB4861A0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGgT+kfYRMY1e7iWNURdzsDV2or47MjJ9xw
Content-Language: en-gb
X-Originating-IP: 31.133.141.6
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=sheGauuCRB/V+AeT+mPqV 3Qc/2BnoCYh4G1iOBVrqD8=; b=CPm/Umzc8V5soIfagkY66ERvsiejlOO8EeXDK XuaKKDBqDH9WcbbrmGH+q+ttnjzUOB6VukP+rs9XNJgi6AiYNxFN9Dyo77C8x28r kSckNP73lJbdNLiveLhTVvc4AyfZvFYBJsjAaNtNz5yIwj0N/ax+IYIiUX5zUaTe TvFWuVu6Z78pnuv3TXLKFhuJcOr4bcXf9RNYkpgY4g5qtaVPIAu3bl4gy6jxTxMA KZHf4Uurs3yKwJHnR7Ak5v+clp8oJpvIFqFWOHjpQeBt2YYc9Tg3MTXX3nURDNep tLjcYRF1QYupmc1pQbUP5UL3AywRA8zmu1P7MNOf3i/SbhsDA==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-28352.003
X-TM-AS-Result: No--22.542-10.0-31-10
X-imss-scan-details: No--22.542-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-28352.003
X-TMASE-Result: 10--22.541900-10.000000
X-TMASE-MatchedRID: oCj5caaCQynxIbpQ8BhdbDjNGpWCIvfTkYC3rjkUXRIvfU/riSJXkZEx qXrBFaCAhnLTBKk7jfrXs+NDjbA5UUiaUFcOFAgUTJGEwRbjGGV4ssIDQ8PtqEZCAhWuYEvk4dO sNKuqfaxe8eBSVUihNXq+qg096V49IRvqkRRE3o6XmVAzMqYX0r8pAYpAfWtArSPg4ph0OIKRwU 87+Pa1MAtgZUhtCgQKONMIq6tJjPUeczFVz7DH6KwBF+5NRZ1aZdOg+SGzWLY9lFqHcAo+Rxcl7 F2w4ImDgMBtpml0DCBJpV9rHFX3j7MwnTKgkbsOwbRQ2Bpmlio3l2plwgrtWLmyqTXHGxLI387R OTCkGUPCfvo3UgFFJJpJ/iGeRMFQP7A6mmzUskCA3KVVsj8QDMaGUx2flwhRGHWakJc1ULxzS/2 P0PZNyYYzpybnX3DdFe05s0alViy8++FsU2sQUwA+Y0oNaxbQ0VvRkjCHhK4QS4VCDDktpzoMBA vRIAqsXGE+m8/IbO+J6uGtPJgUD0UuXkWTSi/R3BZE3fQo7k/3rOH/F+TVqJgjZJ0l7MH/QdJ83 XuBKfq5RgwRLQu4pxQed6RwNEOW5WjwAv2UcRDii75UldPq9hwYKZFJ0uuy4hfk+pbP18icOyyg 3Ong9OLzNWBegCW21WdIO+NJS/kEs/H1wMyspis3zPQeiEbe/nnwJ52QYi8hem0kmpPZMQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Message-ID-Hash: GLW6WGX74536MYMSQ5QXUY7PKFQPJK4D
X-Message-ID-Hash: GLW6WGX74536MYMSQ5QXUY7PKFQPJK4D
X-MailFrom: adrian@olddog.co.uk
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: 'TEAS WG Chairs' <teas-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: adrian@olddog.co.uk
Subject: [Teas] Re: TEAS wiki
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/ZabDdMGmgaPItV5Nq8-g5nFN_Wg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

Hi,

 

It’s meeting time, so I opened up the Wiki to look at things.

Thanks for the work you did to clean up the TEAS Wiki, Ran. It made things much better.

 

I see that the chairs have been making some updates to reflect the current status, but I’m not sure that all the recent changes have been caught.

 

What do we think about making the Wiki more useful so that we can easily work out the pipeline and the chances of progress for our documents?

I’d give as an example the Wiki I made for MPLS when I was chair there earlier in the year : https://wiki.ietf.org/en/group/mpls/doc-status

Or you could look at what the PCE chairs do : https://wiki.ietf.org/en/group/pce

The value of those two wikis is:

*	It is easy to see the status of documents
*	It is easy to see the ordering of documents within a state when there is a queue to be processed
*	It is (reasonably) clear what the sequence of future states need to be
*	There is a more detailed note on the actions and opinions of the chairs

 

Of course, a wiki still needs to be kept up-to-date. But a wiki is something we can all edit.

 

What do you think about implementing something like that for TEAS?

 

Cheers,

Adrian

 

From: chen.ran@zte.com.cn <chen.ran@zte.com.cn> 
Sent: 15 August 2024 07:47
To: teas-chairs@ietf.org
Cc: teas@ietf.org
Subject: [Teas] TEAS wiki

 

Hi chairs,

I was looking at the TEAS wiki and I saw some of the document statuses were out of date, so I made some updates to tidy. Also I added a date column to help note when Chair Notes were made. I used dates from recent status reports for IETF-120. 

Hope I have not tread on anyone toes.

 

Best Regards,

Ran