Conversation

Notices

1. Embed this notice
   Rich Felker (dalias@hachyderm.io)'s status on Wednesday, 29-Jul-2026 01:20:50 JST Rich Felker

   • Graham Sutherland🎃 / Polynomial.pdf.exe
   • ARGVMI~1.PIF
   • 波鉄 (Hatetsu)

   @ariadne @gsuberland @argv_minus_one @HaTetsu Fair, but I still think the socially decent thing to do, especially if you're not a contributor with an existing history, is to first open an issue before sending any code. Issues catch different eyes, and are documentation.

   • Embed this notice
     RealGene ☣️ (realgene@hachyderm.io)'s status on Wednesday, 29-Jul-2026 02:21:00 JST RealGene ☣️

     in reply to

     • Graham Sutherland🎃 / Polynomial.pdf.exe
     • ARGVMI~1.PIF
     • 波鉄 (Hatetsu)

     @dalias @ariadne @gsuberland @argv_minus_one @HaTetsu

     A few weeks ago I stumbled across a bug in #HomeAssistant and tracked it down to an incorrect value in an enumeration.

     I probably could have fixed it and submitted a PR, but I'm a user, not a dev for HA, so had no idea what the potential for breaking things downstream were, and it wasn't my language of choice.

     So I submitted a highly detailed issue, including a highlighted excerpt from the device datasheet showing what the correct value should be, and where the offending enum was located.

     A day or so later, I saw that the maintainer handed it to some codebot to fix, but at least they appeared to check the bot's fix and told it to stay in its lane about some aspect of the process.