Path: csiph.com!aioe.org!news.mb-net.net!open-news-network.org!.POSTED.254.228.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch!not-for-mail From: Thomas 'PointedEars' Lahn Newsgroups: comp.lang.javascript Subject: FAQ (was: Where can I find a summary table of various reqular expressions options?) Date: Sun, 25 Aug 2019 19:47:46 +0200 Organization: PointedEars Software (PES) Lines: 96 Message-ID: <2131035.ElGaqSPkdT@PointedEars.de> References: <9heqkep0qm3psfb06j6916puigl789jk41@4ax.com> <43qvketkc5mdlq8geq9rstqasupdcdnp8b@4ax.com> <81a3le536hc7o2s677gaq2jr7k5pom03ni@4ax.com> <150d6095-121c-433f-9b21-85533e33f33d@googlegroups.com> Reply-To: Thomas 'PointedEars' Lahn Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit Injection-Info: gwaiyur.mb-net.net; posting-host="254.228.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch:178.197.228.254"; logging-data="9596"; mail-complaints-to="abuse@open-news-network.org" User-Agent: KNode/4.14.10 Cancel-Lock: sha1:+GS9fOWoaAWG2NbcgtEgkrHQg8Q= X-User-ID: U2FsdGVkX1+D6j27ZUfayJaARbBUQZ2Pn5BlEFL/QhErBstCIpJkrg== X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. Arno Welzel wrote: >> However - URLs should not become invalid or disappear anyway: >> >> >> >> So if Thomas Lahn mentions as the URL of the >> FAQ for comp.lang.javascript, this URL should not change. It is not going to. >> If Thomas Lahn ever decides not to maintain his FAQ any longer I'm sure >> he will either set up a redirection to the new location or add an >> appropriate note about this in the existing document. Correct. >> It would also be a good idea, if would >> contain a pointer to . I just sent an e-mail >> to Garret - maybe he will add this to his FAQ. Thanks. > Please don't linger on this topic, it's tiring and the history is long. > > Thomas is indeed the groups elected maintainer of the FAQ. Although I appreciate the sentiment, there was no election, so it is incorrect to say that I would be an *elected* maintainer. I was merely the only one who volunteered to do it, *and* actually *did* *something* to (enable us to) *improve* the content (certainly not enough, I am well-aware of that; but also I expected more support from folks in doing it). > The FAQ is located at: It is also located at (as Arno Welzel has said correctly) because the latter redirects to the former. The latter is easier to remember and to write in a Usenet signature or Tweet. Please use it. > Drama caused Garret to give it up as he wanted to be paid by people to > maintain it. Really? I was not aware of the payment part. > So don't bother reaching it out. I would still support and appreciate a link or even *a redirection* from the old outdated to the new updated FAQ. > I think the reality is that no one really cares though. JFTR: *I* still care (otherwise I would not have it still online after 4 years). But if I remain the only one, that will probably not be enough. Especially as I am studying again, too. GitHub Pull Requests (PR) *can* be made. And JFTR, they can be made since 4 years ago; one has been made by Christoph M. Becker in 2016 (ironically, to point out that PRs can be made), and *no* additional one have been made by people so far. However, I also recognize the current markup format of the FAQ (which I inherited from Garrett, too) is not conducive to contributions: Fewer people understand XML than, for example, GitHub Markdown, and ISTM that with JSON, CSON, and YML around, XML as a document(ation) format is going the way of the dinosaurs. Off the top of my hat, I would probably support switching to any other markup format from which a table of contents can be generated *automatically* (I remember vaguely, from several years ago, that GitHub Pages could do that with a plugin, but I might be wrong). On the other hand, at the rate at which the FAQ content is changing (0 edits/hour), maybe it is a mistake to worry about the TOC and the automated section numbering at all. Almost everybody appears to be writing their specifications and documentation in (GitHub) Markdown now (me included); for example: And since (contrary to Garrett, IIRC) I have the FAQ sources on GitHub already, I/we can make sure that no original content is lost in the conversion. > Turning on automated postings again might help. ACK. But: The possibility of automated postings might disappear (at first) with the conversion to a less well-structured but easier editable markup format. For example, I would have to write a program that properly extracts random sections from a Markdown document first (probably doable with sed or awk). -- PointedEars FAQ: | | Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.