Update on my Racket exit

Summary

Figure 1: Blasting off from planet Racket to other planets. Thanks ChatGPT. It’s been almost two years since I took a public step away from the Racket diaspora. I’m writing this post to air out how my Racket projects have gone since then. I believe, as of now, I have zero Racket codebases to maintain — hooray! I want to show how to handle old codebases. Let’s reaffirm the importance of handing off inactive projects instead of holding on to them. Kill your darlings. Let your babies fly from the nest. Let go of your projects so they can evolve without you. Embrace growth, even if it comes with a modicum of chaos. That’s the path. Something beautiful will grow. §Steps to hand off a Racket project Here’s my checklist for handing off a Racket project. Only step 4 is Racket specific. Find an interested future maintainer. Create a GitHub org and transfer the repository into the org. Add your future maintainer as a GitHub organization owner. Update pkgs.racket-lang.org entries with An additional author email linked to the future maintainer’s pkgs.racket-lang.org account Update the repository path because presumably, GitHub will eventually stop redirecting after a repository move. Communicate and clarify any further questions for the new maintainer as they arise. Or not and disappear. Long term projects success hinges on providing the easiest possible hand-off and continued support, as needed. §toml-racket was rehomed Turns out, more people used my revival of Greg’s toml-racket than just me. Go figure: TOML is sweet and simple. The revival codebase touts combined encoding and decoding support. Thanks to Benjamin Yeung for adopting toml-racket. 🙇 §tinybasic.rkt was rehomed Previously. I was on the fence with archiving the tinybasic.rkt repository; given the 10+ stars for this boutique programming language that exists within a niche community, it seemed like a raw deal for these passionate individuals. A random GitHub Pull Request appeared! I’m not set up anymore to QA and rev...