Re: [I18ndir] I-D on filesystem I18N

Patrik Fältström <patrik@frobbit.se> Wed, 08 July 2020 05:14 UTC

Return-Path: <patrik@frobbit.se>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A13513A0831 for <i18ndir@ietfa.amsl.com>; Tue, 7 Jul 2020 22:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se
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 KnKpLrqE_eSH for <i18ndir@ietfa.amsl.com>; Tue, 7 Jul 2020 22:14:34 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) (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 013573A082D for <i18ndir@ietf.org>; Tue, 7 Jul 2020 22:14:33 -0700 (PDT)
Received: from [192.168.10.128] (c-abd9524e.028-114-73746f27.bbcust.telenor.se [78.82.217.171]) by mail.frobbit.se (Postfix) with ESMTPSA id D0D8B2433C; Wed, 8 Jul 2020 07:14:28 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1594185268; bh=rZttQMznVEM+SxBNX5VpjCUicaWrt5m7aqG5nXa6fBo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=aM2nDMk5sKBEcFOKrn6vR/Q388t7GBot2kKHqFHPx9tvwSMCo2sKijwyi5qQJHp1u bZZUq6H+ZBVYYdgyzXrkuRF4ZPh8Tq8mrCJu4kVZmIL5MxgOXLD8HTo9jcH2Pqo+2B alKCASbSSFtw85lQPEKFpz4dVjBP5xGLBNmNgblI=
From: Patrik Fältström <patrik@frobbit.se>
To: John C Klensin <john-ietf@jck.com>
Cc: Nico Williams <nico@cryptonector.com>, i18ndir@ietf.org
Date: Wed, 08 Jul 2020 07:14:27 +0200
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <16A25137-55D8-4A03-8C81-9A39B85CA0C1@frobbit.se>
In-Reply-To: <5956450816F54A60A5C9C5D1@PSB>
References: <20200706225139.GJ3100@localhost> <B8BC0F0A-94AB-4BEF-8A5F-449049E28D8F@frobbit.se> <20200707070456.GK3100@localhost> <B0FAFBAF9EA570CCFB2575CF@PSB> <5F12E7F0-75AC-42A0-8138-771071A86F68@frobbit.se> <5956450816F54A60A5C9C5D1@PSB>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_F4B6B46A-9E29-40BC-A97E-CD60B77619CF_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/uhmYml1xKpZ03YWZE0Uo4qZHbTg>
Subject: Re: [I18ndir] I-D on filesystem I18N
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2020 05:14:36 -0000


On 7 Jul 2020, at 21:16, John C Klensin wrote:

> However, with regard to doing that sort of collaboration
> (independent of a few reviews of documents from assorted IETF WGs), the directorate seems to be both disfunctional and lacking any form of leadership or guidance.   And, if we can't get
> enough collaboration (or some form of aggressive push-back), I think the experience with RFC 8753 and with 5891bis strongly suggests that more work on any of those documents may be a waste of effort.

I agree with this, but I think we also agree one of the problems is a combination of lack of time and competence.

I think we because of this have a few different (!) problems to work with:

- How do people that have competence get more time?

- How do we grow the number of people that do have competence?

- What do we do in the meantime?

Unfortunately I think this list/ad-hoc-group (I do not want to call it directorate really because of the "low quality review process we have", because although we have a somewhat dysfunctional process, we do have a process, we do have a group of people on this list, and sometimes some of us do have a few cycles to spare.

With these few cycles, we get documents and statements and review to some level of quality.

Meta questions are then:

- Is this review enough?

- How do we know the answer to the previous question is correct?

But in the mean time, we just have to work with what we have :-(

I do not like it, but...not as many people are interested in I18N as we want, and definitely not as many as IETF needs.

   Patrik