[Rfced-future] What would an "RFC Series Consultant" actually do?

Nevil Brownlee <nevil.brownlee@gmail.com> Fri, 10 July 2020 04:56 UTC

Return-Path: <nevil.brownlee@gmail.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 298023A0CC6 for <rfced-future@ietfa.amsl.com>; Thu, 9 Jul 2020 21:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tLwRnzDsaPNB for <rfced-future@ietfa.amsl.com>; Thu, 9 Jul 2020 21:56:28 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 A949C3A0CC8 for <rfced-future@iab.org>; Thu, 9 Jul 2020 21:56:28 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id j186so2305534vsd.10 for <rfced-future@iab.org>; Thu, 09 Jul 2020 21:56:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=8oylsW+FOSBS6pmTTK2L/+AjbZs4YyLvDr72GRVkwQk=; b=XujrF97Y4aLy0viltNyRC2i+hG1C4/bs0ndMavs9oE/KnYp8YH0M4nPNWxlqs5kboL XSSznT6FIDhFH/6XVG6JlOWstaWGNtjrwH3kFsBzdBu5JSKaLwvHyOQBt49NZvLKKKsZ Omk/mljrf+ro3gI0YYXW2VLkeKfyuUrrkBpyxfckwur+xwyQmvnSkeJe78QYY8xJ/xww bcp1n0SKq+VkTLWpj0aWhz5844urUv0+tznVYIPdZbop2lHfOuKmcDkHFpu5G4pO+RZm vLGewwudg7fIeipIXaEpkLfY+eZQYqNvms+ExJ+5YiCw9E8Qw0/ASMpPcvOxxbts6jhP 1WbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=8oylsW+FOSBS6pmTTK2L/+AjbZs4YyLvDr72GRVkwQk=; b=UDaJ/rDhgUzW02NcVrz574FE/rnFqN46rm5/tu/JBPsVWYHA5GaWFi64ieXyrdcBdB Njzi5gU7uh8eAIXWLK/nq75MZV3XJ5zlaPX4Tne2chzS2P+FHxgTAfQ2i5h+7JQ3dAtR n4oO79gEorhtbIL99hmuGyNb0o+0ZNWWor4KD+3vpZ7m0Z/UKrs2/SdcRN/hf5CsC5g2 85VBxLonz+aEBiK63dQa2OOk3mGJXWEcGQIViNhroPHfacxwNL3yJ9ueyAj+E7fZeB0I +1D0jOqdOXZRa4lCup6Gi0sSTJlnC0nIw4eCRzfVo2jXnaRNrd18feHmGHpzXgk0RpJQ t8ww==
X-Gm-Message-State: AOAM532m25UIwaDOrSef2z/8nWOn7s+s3yw8awKnwQNrcjZET/spbuUs bQYscZDsGnCKCAcI3LDDFWAlafK9bybbm9YWJ//UMHnqZgA=
X-Google-Smtp-Source: ABdhPJyPHzOwuTjRyBlODv8VeXStaQLcwpYv+aJbzgt4gbNdHLVmisByyMwRYt1KFtX5FWhZdG6JwINaCBzlmJYpTwE=
X-Received: by 2002:a67:ed15:: with SMTP id l21mr50432578vsp.175.1594356987446; Thu, 09 Jul 2020 21:56:27 -0700 (PDT)
MIME-Version: 1.0
From: Nevil Brownlee <nevil.brownlee@gmail.com>
Date: Fri, 10 Jul 2020 16:56:01 +1200
Message-ID: <CACOFP=h_eK-nxXqp73X4-YPYKq26cPOZEPH_urGnTDndrM-S3g@mail.gmail.com>
To: rfced-future@iab.org
Cc: Nevil Brownlee <nevil.brownlee@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000e1cc1c05aa0f29ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/b-5RKr1lXIH7ng4-A1mGZVOTx7g>
Subject: [Rfced-future] What would an "RFC Series Consultant" actually do?
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2020 04:56:30 -0000

Hi all:
Watching the list for the last few days, we seem to be proposing an "RFC
Series *Publishing) Consultant" to "handle Strategy Development for the
series."

When thinking about what the consultant (whatever we call her) actually
does, let's start with the things Heather actually did ...

1. The RPC often runs into tricky edge cases that don't quite fit the Style
Guide.  Heather used to have weekly meetings with the RPC editors (which I
sat in on for 8 years or so); as a group we resolved those issues quickly,
and the RPC saved them for updates to the Style Guide.  I suspect that John
Levine is doing that rather well now.

2. Changes to the series.  That's probably what the list sees as "Strategy"
questions, so the Series Editorial Board (whatever form it eventually
takes) is probably the right place for discussions about that.  Such
changes could, for example, have included how best to provide long-term
digital preservation for the series - Heather spent rather a lot of time on
that.

3. Implementing changes.  Heather actually put a lot of time into the
svg2rfc v3 implementation, a fair bit of that work was contracted out and
overseen by the Tools Team; i.e. we have a precedent for contracting such
work.  However, the ongoing part of the v3 changes is to collect feedback
from authors, the RPC, etc, and feed that back into updates of software and
documentation.    That's a long-term task, but presumably one that could
also be contracted out.

Overall the Series Consultant role does indeed comprise quite a range of
tasks, and I believe the long-term development ones really do need someone
with Publishing and Information Management expertise.

As for finding a suitable person for the "Consultant" role, the 2018 RSOC
formed a Search Committee, which was able to find about eight applicants
with publishing or library experience. We brought three of them to IETF 79
in Beijing so that they could find out about the IETF and how it worked,
and we could interview them.  From those three we chose Heather.  In short,
although it's not easy to find people with the right background, we managed
to do it in 2010.

Cheers, Nevil
-----------------------------------
Nevil Brownlee, Taupo, NZ