After years of putting it off, I landed my first patches in Emacs 31

My Emacs 31 contributions

After years of putting it off, I landed my first patches in Emacs 31

A personal account of finally contributing to Emacs upstream after years of hesitation, largely over the copyright assignment process. The author landed several small changes on master, all shipped in Emacs 31: a Dired option to hide the absolute directory location, macOS speech recognition permission in Info.plist, a "Send to…" sharing command with native macOS support, and a fix restoring macOS dictation. He thanks the maintainers and urges others to sponsor them.

Open source is unsustainably tricky. As consumers, we often like free as in freedom and free as in beer, but neither pay the bills.
  1. kodoman

    Hmm no one has said it yet but thank you, I get a lot of benefit out of your work I love acp.el, when I get a bit more money would love to start sponsoring this sort of stuff because thanks to people like you emacs can use all the modern stuff better then the IDE's. Thanks!

  2. pnathan

    thank you! I use emacs daily!

  3. noctuid

    > which does feel a bit archaic (download, sign, and return a PDF) and slow (mostly waiting for an email response), though hey, I have nothing but sympathy. Open source is unsustainably tricky. As consumers, we often like free as in freedom and free as in beer, but neither pay the bills. We hope some company steps in to fund these projects, but that rarely happens. As a result, most open source projects are starved (even popular ones), run by volunteers working for free.

    These two are completely unrelated.

    > All that is to say, if the upstream Emacs contribution/onboarding process seems less than ideal, cut it some slack

    At my first job I tried for over a year to get my company to sign. Since then, no job I've interviewed for has been willing to sign the papers or actually signed them regardless of the company size. Too much process that stalled and never completed. It was actually the smaller companies I spoke with that weren't even willing to sign anything regardless of narrow, straightforward, and clearly unrelated to job work it would be. Obviously there are software engineers that are able to get the papers signed, but that's just one small aspect of how ridiculous everything GNU and FSF related is. I can't wait for a proper non-GNU emacs again.

More from this day

2026-11-18