From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Git representative on AsciiDoc Working Group
Date: Fri, 14 Feb 2020 21:05:44 +0000 [thread overview]
Message-ID: <20200214210544.GA6664@camp.crustytoothpaste.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2002141306350.46@tvgsbejvaqbjf.bet>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
On 2020-02-14 at 12:07:00, Johannes Schindelin wrote:
> Hi,
>
> On Fri, 14 Feb 2020, Jeff King wrote:
>
> > On Wed, Feb 12, 2020 at 12:21:29AM +0000, brian m. carlson wrote:
> >
> > > I've had folks from OpenDevise reach out to me and let me know that they're
> > > launching a standardization initiative for AsciiDoc under the Eclipe
> > > Foundation's open standardization process. The goal is to standardize the
> > > language, ensure compatibility across implementations, and provide a reference
> > > implementation, with input from implementers, users, and others.
> > >
> > > They'd like to extend an invitation for the Git project to send a
> > > representative, since we're a significant user of AsciiDoc. I'm sending out
> > > this email to see what the project thinks and if anyone would be interested in
> > > fulfulling that role.
> >
> > [...]
> > As far as choosing a representative from the project, I'd probably
> > nominate you. ;)
>
> I'd probably second this. ;-)
I'm happy to fill this role if the project would like. The main
interest for me when representing the Git project would be a focus on
compatibility between implementations, which has historically been a
minor pain point for us. That, of course, is the whole point of
standardization.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
prev parent reply other threads:[~2020-02-14 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 0:21 Git representative on AsciiDoc Working Group brian m. carlson
2020-02-14 6:23 ` Jeff King
2020-02-14 12:07 ` Johannes Schindelin
2020-02-14 21:05 ` brian m. carlson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200214210544.GA6664@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).