[openpgp] Using Git for RFC 4880bis

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Sat, 25 June 2016 15:41 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F41C912B074 for <openpgp@ietfa.amsl.com>; Sat, 25 Jun 2016 08:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 S4hYfA6jyxiY for <openpgp@ietfa.amsl.com>; Sat, 25 Jun 2016 08:41:23 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by ietfa.amsl.com (Postfix) with ESMTP id 5319012B01D for <openpgp@ietf.org>; Sat, 25 Jun 2016 08:41:23 -0700 (PDT)
Received: from fifthhorseman.net (pool-100-35-130-80.nwrknj.fios.verizon.net [100.35.130.80]) by che.mayfirst.org (Postfix) with ESMTPSA id 01356F98B for <openpgp@ietf.org>; Sat, 25 Jun 2016 11:41:22 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id A175A203DC; Sat, 25 Jun 2016 11:41:22 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: IETF OpenPGP <openpgp@ietf.org>
User-Agent: Notmuch/0.22+69~gd812194 (https://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu)
Date: Sat, 25 Jun 2016 11:41:19 -0400
Message-ID: <877fddjmxs.fsf@alice.fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/3A4k5RSCydggxegBA274mGWF-CQ>
Subject: [openpgp] Using Git for RFC 4880bis
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jun 2016 15:41:25 -0000

Hi OpenPGP folks--

As i understand it, Werner is currently working on his draft of 4880bis
using a pandoc2rfc toolchain.  If we choose to adopt this draft (see my
previous e-mail to the list), the underlying source of the document will
actually be markdown.

The work is being kept under revision control using git.

We appreciate (and encourage!) any changes people want to suggest the
usual way: via an e-mail to this mailing list explaining what text you
think needs to be changed and why.

However, some people may find it more convenient to propose specific
machine-readable changes that can be applied directly to the source; if
you want to do that, making them in the form of patches against the
markdown is probably best.

A public-facing copy of the git repo is hosted at gitlab for anyone who
wants to make edits against the source:

  https://gitlab.com/openpgp-wg/rfc4880bis

If you want to submit patches to the markdown in the draft's working
copy, you can send them directly to this mailing list.  I'm happy to
help folks sort out using "git send-email" if they want guidance on
making this toolchain work.  In my own local copy, i've done:

    git config sendemail.to 'IETF OpenPGP WG <openpgp@ietf.org>';

I find the documentation presented by "git help send-email" to be useful
if you're unfamiliar with this workflow.  Also, feel free to ask me for
help if you have any questions with the tooling.

While it's ok to submit pull requests or open issues (as placeholders
for things that need to be addressed) via the gitlab repository, all
IETF discussion should end up taking place on this mailing list.  See
CONTRIBUTING.md in the git repo if you're considering gitlab as a place
to report issues.

Whenever substantial changes to the document have been made and
stabilized by WG consensus, we'll tag the git repo and submit another
revision of the draft to the IETF datatracker so that changes and
progress are visible to everyone, including the folks who are not using
git.

Please speak up if you have any concerns or questions about this
mechanism.

        --dkg