From 0d348801b6ad4bb77a6b765d9c3375f37311a672 Mon Sep 17 00:00:00 2001 From: Lucian Mogosanu Date: Fri, 30 Aug 2019 11:52:56 +0300 Subject: [PATCH] drafts: Add tmsr-work-v draft --- drafts/000-tmsr-work-v.markdown | 101 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 drafts/000-tmsr-work-v.markdown diff --git a/drafts/000-tmsr-work-v.markdown b/drafts/000-tmsr-work-v.markdown new file mode 100644 index 0000000..7675739 --- /dev/null +++ b/drafts/000-tmsr-work-v.markdown @@ -0,0 +1,101 @@ +--- +postid: 000 +title: TMSR work: plan for 2019 M9 +date: September 4, 2019 +author: Lucian Mogoșanu +tags: tmsr +--- + +(By the way, methinks that the "TMSR" bit is somewhat redundant -- +it's not like "meanwhile dead [ex-TMSR][citadel] work", or "TSIE work" +is anywhere on the horizon.) + +This July resulted mostly in Hunchentoot code reviews: +[taskmasters][hunchentoot-v]; [requests and replies][hunchentoot-via]; +and [a continuation][hunchentoot-vib] of that one. So I ate and +documented more than 90% of the thing and I'm ready to use it in the +battlefield with the reasonable certainty that it won't fall apart at +the first prod. + +Before writing down the plan for this month, let's look at the stuff +that burns: + +* this blog needs a [comment mechanism][ttp-comments]; +* all this Hunchentoot review work means nothing without a genesis; +* #trilema and other castles require a [fleet of loggers][logging] to + keep things running; and +* feedbot has some new patches that [need to be merged][feedbot] into + the current working tree. + +And as for the stuff that isn't (yet!) burning but is still important: + +* [file pastebin][pastebin]; +* there's been some recent discussion of [Adalisp][adalisp], which is + still in need of a review and further work to be made usable; +* I want to review [older Lisp works][lispwork], how else to even know + if something better is possible? +* eventually I'll want to steal and review all potential Lisp + infrastructure, to determine once and for all whether this Common + Lisp orchestra is actually worth maintaining or it's to be thrown + out of the window, or what; +* I still haven't genesized The Tar Pit; by the way, is there anyone + else out there interested in using it? +* I still haven't run a [Cuntoo][cuntoo] to this day, y'know; +* there's [a ton of other][work-ii] work there; I'm not sure how much + of this I'm going to finish during this lifetime, so at some point + I'll just sit down and re-prioritize. + +Having said this, the more detailed plan for the short term is: + +* Week **36**: genesize Hunchentoot and [everything + else][sbcl-and-others] required to run it, save for the operating + system. +* Weeks **37**-**38**: implement The Tar Pit comments and publish said + coad[^1]. +* Weeks **39**-**40**: read [Stan's logger][snsabot]; stand up a + [Logbot][botworks]; write a minimal WWW frontend that takes items + from the logotron database and renders them; publish that. + +And I could go on with this list up to week 50 maybe, but let's see +how the current items go first, then we'll get back to it. + +[^1]: I actually have this broken down into pieces, let's look at it. + + First, the posts need to be indexed somehow in some kind of + database, so that the blogotron knows how to retrieve the content + and the comments for it and render everything into a page. I don't + care about the database backend, the code that does this should be + attachable to any type you like with minimal glue. + + Then, I'll need to make some modifications to the blog itself, so + that it knows that such thing as "comments" exist and can be + retrieved from said database and rendered. This includes page + layout modifications as well as backend scaffolding for getting + comments and inserting them below the post. + + Finally, there's supposed to be a way to post comments, à la + Wordpress' wp-comments-post.php. Additionally, this should come + with anti-spam support built-in, but... well, did you see the + "stuff that's burning" list? I'll patch that wound when (yeah, + when, not if) it starts burning. Until then, I guess all comments + are to go to the moderation list, or I'll whitelist IPs or + whatever. + + Oh, and by the way, I should also implement server-side selection + for this thing at some point. + +[citadel]: /posts/y04/068-the-story-of-the-citadel.html +[hunchentoot-v]: /posts/y06/09b-hunchentoot-v.html +[hunchentoot-via]: /posts/y06/09c-hunchentoot-via.html +[hunchentoot-vib]: TODO +[ttp-comments]: /posts/y06/099-tmsr-work-iv.html#selection-176.0-176.3 +[logging]: /posts/y06/099-tmsr-work-iv.html#selection-160.0-160.7 +[feedbot]: http://logs.nosuchlabs.com/log/trilema/2019-08-23#1930279 +[pastebin]: /posts/y06/099-tmsr-work-iv.html#selection-238.0-238.7 +[adalisp]: http://logs.nosuchlabs.com/log/trilema/2019-08-30#1932159 +[lispwork]: /posts/y06/099-tmsr-work-iv.html#selection-208.0-208.13 +[cuntoo]: http://trinque.org/2018/11/27/cuntoo-bootstrapper/ +[work-ii]: /posts/y05/090-tmsr-work-ii.html +[sbcl-and-others]: http://logs.nosuchlabs.com/log/trilema/2019-08-30#1932154 +[snsabot]: http://www.loper-os.org/?p=3452 +[botworks]: /posts/y05/080-botworks-regrind.html -- 1.7.10.4