Interested to know the current status of this effort. Having worked in standards for over 20y, and also 4y ago converted all our specifications (which are used as de facto standards) to Asciidoctor, and having had some passing experience with Eclipse Foundation, I may be able to contribute an idea or two.
- thomas On Monday, 7 January 2019 21:36:20 UTC, Dan Allen wrote: > > I'm excited to share with you some much anticipated news. > > After numerous calls for an AsciiDoc specification over the past year, > it's very clear the community is ready for AsciiDoc to take this step. As > we established in previous threads, Lex and I are in agreement. I also > reached out to Stuart and we have his support as well. So now's the perfect > time to pursue it. > > == A new home at the Eclipse Foundation > > We all want AsciiDoc to have a strong future and the resources it needs to > evolve and grow. To achieve this, I'm planning to submit a proposal for an > AsciiDoc language specification to the Eclipse Foundation. The Eclipse > Foundation provides a home for developing specifications and is committed > to transparency and open source, values that align well with AsciiDoc and > its community. Specifically, the Eclipse Foundation Specification Process > (EFSP) provides a clear, yet customizable structure that reduces the risk > of the process stalling and ensures the outcome will be usable in the real > world. The process is public, vendor neutral, and all source materials and > final artifacts are open source. > > -- 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/7aeea5d4-1dc7-444e-9aab-63a8aacb3cbf%40googlegroups.com.
