Announcing the formation of the AsciiDoc Working Group and invitation to join

Fellow AsciiDoc enthusiasts,

Sarah and I are pleased to announce that we're in a position to launch the standardization effort for AsciiDoc. AsciiDoc has gained traction as a preferred choice for technical writing in IT, and we want to see it continue to grow. We've also heard from those who've asserted that a specification is needed in order for that to happen. We agree that a specification for AsciiDoc will solidify what we have today while making way for new capabilities that adapt the language to the ever-changing technology landscape.

We'll be using the Eclipse Foundation's open specification process (https://www.eclipse.org/projects/efsp/) for this effort. We've taken the first step of initiating the AsciiDoc Working Group (WG), and are now putting out a call for members.

The primary goal of the AsciiDoc WG is to drive the effort that graduates AsciiDoc from a de facto standard to an official specification with an open TCK and a compatible open source implementation. To achieve this goal, the AsciiDoc WG will initiate the AsciiDoc specification project and ensure that the specification is developed according to the Eclipse Foundation's open specification process. The specification project will define the AsciiDoc language's terminology, syntax, document model, extension points, and so forth.

To learn more about the AsciiDoc WG, 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

The AsciiDoc WG and its projects are open to everyone. You can become a member of the AsciiDoc WG, contribute to one of the projects, or just observe. If you're interested, please join the AsciiDoc WG mailing list (https://accounts.eclipse.org/mailing-list/asciidoc-wg). By participating, you can have a voice in how AsciiDoc is defined and how it evolves.

Please note that from this point forward, all discussion about the AsciiDoc standardization process should be directed to the AsciiDoc WG mailing list.

And with that, we're off!

Best Regards,

-Dan

--
Dan Allen | @mojavelinux | https://twitter.com/mojavelinux

Congrats!