From: Jeff King <peff@peff.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: Git representative on AsciiDoc Working Group
Date: Fri, 14 Feb 2020 01:23:35 -0500 [thread overview]
Message-ID: <20200214062335.GB605125@coredump.intra.peff.net> (raw)
In-Reply-To: <20200212002129.GB6464@camp.crustytoothpaste.net>
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.
It certainly would be nice for somebody with Git's interests in mind to
keep an eye on the proceedings, just to make sure nothing too disruptive
is decided on.
But I don't know that we have a particular wishlist of things we'd
_like_ to see. The lack of semantic markup in asciidoc (e.g., being able
to mark a command-line parameter as such, rather than just a literal) is
sometimes a pain, but I think that's also what makes the source
documents so readable and generally non-painful to write.
As far as choosing a representative from the project, I'd probably
nominate you. ;)
-Peff
next prev parent reply other threads:[~2020-02-14 6:23 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 [this message]
2020-02-14 12:07 ` Johannes Schindelin
2020-02-14 21:05 ` brian m. carlson
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=20200214062335.GB605125@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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).