𝕹𝖞𝖝 妛彁λ♀ :xf_nyxsigil: :labrys-45-sickle: :nyxcat: on Nostr: I mean like, once again I'm just talking out of my ass here instead of actually ...

I mean like, once again I'm just talking out of my ass here instead of actually writing code, but as a place to start...

so this is pretty much what I was thinking would be the way to do what I'm describing. like, organize around working on a large and substantial project that would be useful to CL as a whole, maybe something like a new implementation or a fork of an existing one which frankly there might be more of a need/demand for since SBCL is getting LLM slop in it, and with all the progress SICL has made over the years I'd imagine it's gotten a lot easier since the time SBCL was written to implement CL. I know λzyd (npub14gt…xth6) already forked SBCL but as far as I know there are no plans by anyone other than for it to be a maintenance fork. but anyways, yeah have the project like a CL implementation/fork of an existing one be run in like an explicitly collective sort of way with actual governance, have a standardized process for writing extensions (and require actual documentation) that other implementations already do anyways in an ad hoc sorta way that then later gets papered over by compatibility libraries, then you have a route for people to contribute with easier things like e.g. checking off RFC implementations that would be useful for the implementation and CL as a whole but that aren't just random people making hobby projects 15 years ago that sorta work well enough but that no one bothers to document and maintain and potentially improve.