Dear All, Ok, new rule for this thread, before posting everyone has to go for a walk around the block and/or pat a cute puppy before they post.
That people are passionate and interested in the process is a good thing, and that will have to be managed through the process, telling them to "move on" is not the way to manage the process. Also posting things as a fait accompli is not a good way to encourage engagement, "we will use Eclipse", "the rules will be different", "we will have a funded group" ... I also have seen no public discussion of those "decisions". A great deal more regular communication and consultation is needed for an open process. If "life" is making it hard for you to contribute, say so, the process is going to have to accommodate that if it is to allow contribution by people who are not full time on the project. Lets get the process used to accommodating that from the beginning. Also posting that something is the most important issue as if its a given, only results in negative responses. To my mind both implementations and specifications are needed, implementations test the specifications and identify parts that are difficult or expensive to implement. And wherever possible more than one implementation, things that are wildly inefficient in one language may be a doddle in another. I commend to you the C++ specification process, where a number of items that were formerly thought difficult to parse, were already being done by the compilers so they could provide useful error messages. And so because the compiler makers were also involved in the specification process, these items were added to the specification. For example distinguishing >> shift operator token from two consecutive closing > of a nested template without needing a space between. And I chose that example deliberately because its just the sort of context dependent special case that Asciidoc is likely to have to decide to allow, or not, as the case may be. So much of the language used, by everyone, in this thread (to my ears) has had the tone of a proclamation. Certainly the delay is frustrating, and that contributes to the tone of posts, but it is what it is. I think its great that people are passionate, stick around, be involved, even start the process if you want to. And I think having someone other than the developers write what they see as the Asciidoc language would be a great thing, it would potentially show areas that the developers understand totally differently from users. Write it up in whatever form you understand best, and stick it on github/gitlab/your favourite hosting site and post here asking for contributions. Lets try to channel the passion into positive progress. And remember pat the puppy https://cdn.pixabay.com/photo/2019/05/28/05/47/puppy-4234435__340.jpg awwwww. Cheers Lex -- 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/CAKhWKDOMK3yJmuKFJC%3Dx4CSamu5MzEqThcJyb1Raf_oZWSzAuA%40mail.gmail.com.
