Re: [I18nrp] Additional input needed for i18nRP BOF

Adam Roach <adam@nostrum.com> Wed, 06 June 2018 22:56 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 570A9130DE1 for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 15:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 eSrNiqwpkFrJ for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 15:56:54 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DE601277C8 for <i18nrp@ietf.org>; Wed, 6 Jun 2018 15:56:54 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w56MuqeC052358 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 6 Jun 2018 17:56:53 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Peter Saint-Andre <stpeter@mozilla.com>, John C Klensin <john-ietf@jck.com>, i18nrp@ietf.org
References: <f997170c-3062-0241-e58d-7a3415fba983@nostrum.com> <CE6F76BB323F1555D6B217A5@PSB> <9ecf8b7a-d086-1c56-03fb-6773aed332c6@nostrum.com> <4DA478C4C99396556E1B3EF1@PSB> <a31e91ff-c78c-6a7c-fe8c-70b9563312f7@nostrum.com> <8774afa2-4d3f-bc08-69af-f88e229f547a@mozilla.com> <07356789-b93f-b1a2-21d6-bef704b7c0b0@nostrum.com> <a6b7bf5c-3f37-e97b-7e44-c9e648bdbcef@mozilla.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <ba6339f3-eb5f-4d14-51fb-256d6682f37e@nostrum.com>
Date: Wed, 6 Jun 2018 17:56:47 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <a6b7bf5c-3f37-e97b-7e44-c9e648bdbcef@mozilla.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/TkOLFkpYXYCO944hKv4qPHrk6QM>
Subject: Re: [I18nrp] Additional input needed for i18nRP BOF
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2018 22:56:58 -0000

On 6/6/18 5:31 PM, Peter Saint-Andre wrote:
> SECDIR, GENART, and ARTART reviewers seem to check the whole document.
> By contrast, I18N reviews would have a smaller scope (along the lines of
> what the SDPDIR does).

I'm not sure how good a comparison this is. Any document that doesn't 
mention SDP is clearly not a candidate for SDPDIR review. Any document 
that doesn't mention i18n, probably *does* need a check that such 
omission makes sense. In that way, I think the required task is more 
like SECDIR than SDPDIR.

Thanks for mentioning ARTART. Its process is useful as a third point on 
the continuum of rigor exhibited by directorates. ARTART only reviews 
those documents that are flagged as potentially having ART interactions, 
rather than the intended full coverage of SECDIR, OPSDIR, and GENART. It 
is probably more in line with what is appropriate for an 
internationalization directorate, both in function and size. It 
currently has 12 members, although we would ideally like a slightly 
larger pool.

> As a point of comparison, the W3C I18N WG [1] is
> quite busy but is very small: John Klensin and I and a few others help
> out, but most of the work is done by two people.

Taken together with the assumption that any IETF directorate would 
probably involve substantial overlap with that group of people, I'm now 
concerned about scaling. I couldn't quickly find statistics on how many 
documents the W3C finalizes in any given year, but my impression is that 
it's somewhat smaller than the IETF's output. Given that your 
description uses the words "quite busy," do you think that same group of 
individuals could double or triple their i18n review load without losing 
efficacy or burning out?

/a