Unfortunately this process does not allow those of us who are individuals to participate, all participation requires membership of Eclipse, which is entirely organisation related, it has no individual membership.
Lex On Fri, 14 Feb 2020 at 07:58, Dan Allen <[email protected]> wrote: > > Fellow AsciiDoc enthusiasts, > > AsciiDoc has gained traction as a preferred choice for technical writing in > IT, and we all want to see it continue to grow. As we've discussed > previously, in order for that to happen at this point, we need a > specification. > > With that said, I'm kicking off the standardization effort for AsciiDoc using > the Eclipse Foundation Specification Process > (https://www.eclipse.org/projects/efsp/). I'm doing so on behalf of > OpenDevise, who will serve as the Lead Organization. With Stuart's blessing, > we've taken the first step of proposing to establish the AsciiDoc Working > Group. > > The AsciiDoc Working Group (WG) administers the overall effort and is > responsible for initiating and steering the technical projects. The AsciiDoc > WG will be governed by its charter > (https://www.eclipse.org/org/workinggroups/asciidoc-charter.php). Note that > the AsciiDoc WG is not officially established until its charter is ratified. > The ones who vote to ratify the charter are the initial members who have > signed the participant agreement for the WG > (https://www.eclipse.org/org/workinggroups/wpga/asciidoc-working-group-participation-agreement.pdf). > There's no fee for a committer member (i.e., individual) to sign this > agreement (though there is an expected time commitment). > > The primary goal the AsciiDoc WG will put forth is to graduate AsciiDoc from > a de facto standard to an official specification with an open TCK and at > least one compatible open source implementation. To achieve this goal, the > AsciiDoc WG will originate the AsciiDoc specification project and ensure the > specification is developed in accordance with the Eclipse Foundation > Specification Process. The specification project will work to define the > AsciiDoc language's terminology, syntax, ASG, document model, extension > points, and so forth. > > 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 standardized and how it evolves. > > Please direct all future discussions about the AsciiDoc standardization > effort to the AsciiDoc WG mailing list. > > Thanks and Best Regards, > > -Dan > > -- > Dan Allen | @mojavelinux | https://twitter.com/mojavelinux > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/asciidoc/CAKeHnO6V3VpRZt%2Bq-CJrzVB6zUtgmyuXMgag%3DP5WJQRaYtAhtw%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/CAKhWKDNdjKveUaTQ%3DMREQDzLpcuY1ujp5KPGBHt5Xfuci35J%2Bg%40mail.gmail.com.
