# Git representative on AsciiDoc Working Group 4 messages from 2020-02-12 to 2020-02-14. Participants: brian m. carlson, Jeff King, Johannes Schindelin. Thread: https://gitlist.dev/t/52784 ## brian m. carlson, 2020-02-12 00:21 Subject: Git representative on AsciiDoc Working Group Message-ID: <20200212002129.GB6464@camp.crustytoothpaste.net> URL: https://gitlist.dev/e/20200212002129.GB6464%40camp.crustytoothpaste.net ``` 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 ``` ## Jeff King, 2020-02-14 06:23 Subject: Re: Git representative on AsciiDoc Working Group Message-ID: <20200214062335.GB605125@coredump.intra.peff.net> URL: https://gitlist.dev/e/20200214062335.GB605125%40coredump.intra.peff.net 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 ``` ## Johannes Schindelin, 2020-02-14 12:07 Subject: Re: Git representative on AsciiDoc Working Group Message-ID: URL: https://gitlist.dev/e/nycvar.QRO.7.76.6.2002141306350.46%40tvgsbejvaqbjf.bet In-Reply-To: <20200214062335.GB605125@coredump.intra.peff.net> ``` 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. ;-) Ciao, Dscho ``` ## brian m. carlson, 2020-02-14 21:05 Subject: Re: Git representative on AsciiDoc Working Group Message-ID: <20200214210544.GA6664@camp.crustytoothpaste.net> URL: https://gitlist.dev/e/20200214210544.GA6664%40camp.crustytoothpaste.net In-Reply-To: ``` 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 ```