What have I been writing when I haven’t been writing here?
Duck Alignment Academy
- Use reserved domains and IPs in examples — Domains and IP blocks specifically reserved for documentation purposes are far better than the placeholders you’re probably using.
- Adding pre-report bug discussion — The Ghostty project requires bug reports to start as discussion threads. If they’re actionable, a maintainer converts the thread to an issue.
- Growing your project means doing less coding — You can’t hide from the reality of a growth in non-coding tasks. If you want to keep writing code, recruit others to take on the rest.
- It’s okay to be partial to your work — It’s okay to be partial to — and promote — your own work, so long as you follow the community’s process.
OpenSSF
- New Guide on Simplifying Software Component Updates — My name isn’t on this, but I helped with some editing on both the guide and the blog post.
Kusari
- Open source accelerates secure software — The US DoD’s Software Fast-Track Initiative looks to improve software procurement and security. Open source software must be a key part of this.
- Code is More Important than Identity for Security — Asking open source contributors to prove their legal identity doesn’t make software more secure.
Thanks for sharing, Ben! Really useful tips on handling bugs, project growth, and open source. Appreciate the update!