# HG changeset patch
# User ellis <ellis@rwest.io>
# Date 1698200617 14400
# Node ID d2774f9deb9d251ed2df3f646ddf7c242ceaa8a9
# Parent  5ff09e9ac26d2e60a5b85fc49990648680400223
refactor repos

diff -r 5ff09e9ac26d -r d2774f9deb9d .hgsub
--- a/.hgsub	Fri Oct 20 20:21:26 2023 -0400
+++ b/.hgsub	Tue Oct 24 22:23:37 2023 -0400
@@ -1,5 +1,2 @@
 blog=https://lab.rwest.io/comp/blog
-docs=https://lab.rwest.io/comp/docs
-notes=ssh://git@lab.rwest.io/comp/notes
-pitch=ssh://git@lab.rwest.io/comp/pitch
-roadmap=ssh://git@lab.rwest.io/comp/roadmap
\ No newline at end of file
+docs=https://lab.rwest.io/comp/docs
\ No newline at end of file
diff -r 5ff09e9ac26d -r d2774f9deb9d .hgsubstate
--- a/.hgsubstate	Fri Oct 20 20:21:26 2023 -0400
+++ b/.hgsubstate	Tue Oct 24 22:23:37 2023 -0400
@@ -1,5 +1,2 @@
-0000000000000000000000000000000000000000 blog
-0000000000000000000000000000000000000000 docs
-92ed9071dbc374962d1aad574c73a48de6ab40b5 notes
-66df5a8b13ca8988eb959de3dbca2a2fe411e0a8 pitch
-5a40ce874037097279aac0023f0212f39ac02ad4 roadmap
+281364f7d1106b16f12d1ca1b2ee16901fe6ecae blog
+b154f8be21c8c89c2c04ecf6b4230842b15115b1 docs
diff -r 5ff09e9ac26d -r d2774f9deb9d ideas.org
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ideas.org	Tue Oct 24 22:23:37 2023 -0400
@@ -0,0 +1,86 @@
+#+TITLE: ideas
+#+TODO: TODO WIP RFC | DONE
+This is a running list of ideas. Most of these are tools, libraries,
+projects, etc but anything is fair game.
+
+* TODO shed
+:PROPERTIES:
+:ID:       fc9a94e1-91c5-4915-90b8-73218fa3b8bc
+:END:
+:LOGBOOK:
+- State "TODO"       from              [2023-04-07 Fri 23:24]
+:END:
+rlib
+> ulib
+> ulib
+> ulib
+> ulib
+
+** TODO sh* tools
+:PROPERTIES:
+:ID:       c0613a13-7ccb-4af9-b47e-e14a41c782c2
+:END:
+:LOGBOOK:
+- State "TODO"       from "TODO"       [2023-04-07 Fri 23:22]
+:END:
+shc,shx,etc
+* WIP packy
+:LOGBOOK:
+- State "TODO"       from              [2023-04-07 Fri 23:33]
+:END:
+** WIP rust
+** WIP common-lisp
+** WIP emacs-lisp
+** python
+** julia
+** C
+** C++
+* TODO tenex
+:LOGBOOK:
+- State "TODO"       from              [2023-04-07 Fri 23:52]
+:END:
+* TODO mpk
+:LOGBOOK:
+- State "TODO"       from              [2023-04-07 Fri 23:52]
+:END:
+* TODO cfg
+:LOGBOOK:
+- State "TODO"       from              [2023-04-07 Fri 23:34]
+:END:
+* TODO obj
+:LOGBOOK:
+- State "TODO"       from              [2023-04-07 Fri 23:51]
+:END:
+split out from rlib to separate package
+- a purely OOP class library
+* TODO lab
+:LOGBOOK:
+- State "TODO"       from              [2023-04-07 Fri 23:34]
+:END:
+* TODO source categories
+- need a way of extracting metadata from a repo
+- need ability to search and query libs/packages
+- separate modules based on where they belong in our stack?
+  - app
+  - lib
+  - script?
+  - dist
+    - software distros
+* TODO generic query language
+from obj protocol?
+sql compatibility?
+
+/check out kdb/
+* TODO bbdb
+:LOGBOOK:
+- Note taken on [2023-10-24 Tue 22:16] \\
+  graph database, build on rocksdb
+:END:
+insidious Big Brother database.
+- an application built with obj
+- sql
+
+* TODO NAS-TV                                                         :nas:t:
+- media streaming
+- gstreamer backend
+- audio/video
diff -r 5ff09e9ac26d -r d2774f9deb9d pitch.org
diff -r 5ff09e9ac26d -r d2774f9deb9d readme.org
--- a/readme.org	Fri Oct 20 20:21:26 2023 -0400
+++ b/readme.org	Tue Oct 24 22:23:37 2023 -0400
@@ -0,0 +1,11 @@
+#+TITLE: comp/org
+
+* blog
+
+* docs
+
+* notes
+
+* pitch
+
+* roadmap
diff -r 5ff09e9ac26d -r d2774f9deb9d roadmap.org
diff -r 5ff09e9ac26d -r d2774f9deb9d scratch/20230730.org
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/scratch/20230730.org	Tue Oct 24 22:23:37 2023 -0400
@@ -0,0 +1,36 @@
+* VC infrastructure
+In heptapod we have a root group named =comp=, containg a variety of
+subgroups. Some of these groups should be public, while others are
+internal to comp members exclusively. Within each subgroup, we should
+have the root group members automatically granted privileged access to
+projects. This is relevant for the =startup= subgroup in particular,
+where each project is potentially maintained by multiple non-root
+contributors.
+
+We also need to consider how we will manage subrepos across the
+organization. It is about time we start integrating HG bundles and
+potentially mirrors. For our core VC pipeline we should have no
+reliance on Git, but this may be difficult. It depends on the behavior
+of HG bundles.
+
+Bookmarks/tags should be used for milestones in the root group and are
+infrequent. They are more frequent in projects with a regular release
+life-cycle.
+* Approaching Webapps
+I started poking around in the webapp space again so that I can launch
+a landing page for NAS-T quickly. The Rust situation has improved
+somewhat on the frontend side, and the axum backend stack is nice.
+
+This might seem like a lot of Rust and not a lot of Lisp, which it is,
+but there's still room for Lisp wherever we need it. It mostly plays a
+role in the backend, servicing the database and responding to requests
+from the Rust edges. All of the important tests for the web APIs are
+also written in Lisp. We will almost certainly use Lisp for all static
+processing and HTML generation at compile-time.
+
+This I believe, is the appropriate way to integrate Lisp into a
+cutting-edge web-app. You get the good parts of Lisp where you need
+them (interactive debugging, dynamic language, REPL) and avoid the bad
+parts (OOB optimization, RPS performance) in areas where the customer
+would be impacted. In this domain, Lisp takes the form of a glue
+rather than the bricks and mortar it sometimes appears to us as.
diff -r 5ff09e9ac26d -r d2774f9deb9d scratch/20231024.org
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/scratch/20231024.org	Tue Oct 24 22:23:37 2023 -0400
@@ -0,0 +1,59 @@
+* virt
+** QEMU
+** KVM
+** Hyper-V
+** Firecracker
+** Docker
+** Vagrant
+** LXC
+** LXD
+** containerd
+** systemd-nspawn
+** VirtualBox
+
+* Concatenative
+** Factor                                                           :factor:
+- [2023-07-04 Tue]
+  Factor is a cool concatenative lang but unfortunately the C interface
+  (vm/master.h) no longer exists on the master branch.
+** Joy                                                                 :joy:
+
+*** https://hypercubed.github.io/joy/html/j02maf.html
+
+*** [[https://builds.openlogicproject.org/content/incompleteness/arithmetization-syntax/arithmetization-syntax.pdf][arithmetization of syntax]]
+* Lisp                                                                 :lisp:
+These notes pertain to Lisp. More specifically, ANSI Common Lisp in
+most places.
+
+- https://github.com/lispnik/iup/ - doesn't support MacOS yet, looks
+  cool though
+  - what we really need is wasm compiler.. TBD
+* Rust
+** Serde
+- [2023-07-05 Wed] \\
+  important part of the Rust ecosystem, another dtolnay
+  contribution. If you want to program a /data/ format in the Rust
+  ecosystem, this is how you do it.
+
+  The way it works is that you define some special structs, a
+  Serializer and a Deserializer which implement the Serialize and
+  Deserialize traits provided by serde, respectively.
+
+  You can use these structs to provide your public API. The
+  conventional choice is public top-level functions like from-str
+  and to-string. That's it, your serialization library can now read and
+  write your data format as Rust data types.
+
+  [[https://serde.rs/enum-representations.html][enum-representations]]
+  - the default behavior is an externally tagged representation (verbose)
+
+  The docs use strings as core IO when implementing a custom format,
+  but the convention is to implement for T where T is bound by std::io
+  Read or Write trait. Then you can provide a more robust public API
+  (from_bytes, from_writer, etc).
+* C
+* CPP
+* Nu
+[[https://www.nushell.sh/][~]]
+[[https://www.nushell.sh/cookbook/][cookbook]]
+[[https://github.com/nushell/nu_scripts][nu_scripts]]