On Thursday, January 3, 2019 at 4:45:29 PM UTC-5, Dan Allen wrote: > > I am *days away* from submitting a proposal that outlines a new path > forward. Given that doing anything of the sort requires a substantial > volunteer effort on my part, it's something I'm taking my time to prepare > for (and not taking lightly). What I ask is that the community remain > patient for this proposal so we have something concrete to discuss. Given > that AsciiDoc is 10+ years old, I think we can spare a few more days. >
I shall await it with much interest. > there are already four dialects >> > > Can you enumerate which dialects you think there are? (I have an idea, but > I want to know your perspective) > Python 2 asciidoc. The Python 3 port. Asciidoctor, and that rogue py3 port of Berthold Gehrke's. I have to consider the 2 and 3 ports different dialects because I'm as worried about future drift in my risk estimates as about present problems. NTPsec is critical network infrastructure. so my planning horizon is around a decade. Which is one of the reasons I recommend shooting the Python 2 base version through the head sooner and not later. > * The main reason the website has fallen out of date is because it uses an > obscure site builder that no one can seem to run. This makes what should be > a simple update be absurdly complex. If someone can figure out how to get > Travis CI to build the website from scratch, then it would go a long way to > making updates simpler. > That's unfortunate. NTPsec solved that problem for GitLab, we get a build of our website every time we push to its repo, I don't know how to do that for GitHub, alas. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
