From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: git@vger.kernel.org
Subject: Git representative on AsciiDoc Working Group
Date: Wed, 12 Feb 2020 00:21:29 +0000 [thread overview]
Message-ID: <20200212002129.GB6464@camp.crustytoothpaste.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
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.
Here's a bit of a summary on what will be involved:
As a Working Group member, the Git project will have the opportunity to:
- Influence the scope and roadmap of the AsciiDoc standardization effort
- Help define the AsciiDoc specification, including terminology, syntax,
document model, behavior, and extension points
- Establish compatibility rules that ensure portability and
interoperability of content and language extensions
To learn more about the AsciiDoc Working Group and how it works, please
refer to the welcome messages on the mailing list:
- https://www.eclipse.org/lists/asciidoc-wg/msg00001.html
- https://www.eclipse.org/lists/asciidoc-wg/msg00002.html
If anyone has any questions, I'll do my best to answer them, or to pull in folks
who can if I can't.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next reply other threads:[~2020-02-12 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 0:21 brian m. carlson [this message]
2020-02-14 6:23 ` Git representative on AsciiDoc Working Group Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200212002129.GB6464@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).