On Thu, Jan 3, 2019 at 3:17 PM Eric Raymond <[email protected]> wrote:
> 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. > Thanks. > >> 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. > Thanks for sharing. The rogue py3 port is exactly that, rogue. And something my proposal will address. > > 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. > As far as I'm concerned, asciidoc-py2 is finished. asciidoc-py3 is what will be packaged for Linux distributions and carry on. Seeing them as different would be like seeing different versions of the same software as different. Different only because it's an earlier version. asciidoc-py2 is history. > > >> * 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. > I want to be clear, the issue is not with the hosting (GitHub, Travis, etc). It's the fact that no one can manage to install and run the build (based on A-A-P) locally. If we can do that, the rest is trivial. But this has been a problem for years, so it's nothing new. (Or someone could just rewrite the build to use Hugo, Jekyll, or something we can actually run...since it's not that complex anyway). -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 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.
