Conversation

Notices

1. Embed this notice
   doll! (hierarchon@inherently.digital)'s status on Wednesday, 20-Sep-2023 03:26:24 JST doll!

   i think if we want a better open source culture we have to accept that for small single-dev projects "no, i don't feel like doing this, patches welcome" is a valid response to a nontrivial issue, and "no, I don't feel like doing this, and I also don't want the maintenance burden so i won't even accept patches" is as well

   • clacke likes this.
   • Embed this notice
     doll! (hierarchon@inherently.digital)'s status on Wednesday, 20-Sep-2023 03:26:25 JST doll!

     in reply to

     like I'm working on my music player and it supports a limited set of formats, right, and if someone opened a PR for one of the missing formats I'd be like "no, but if you rewrite it to support multiple decoder backend I'll take a look"

     on the other hand if someone asked for a gui or Spotify support I'd just close it with "this is a terminal player and I don't use Spotify, fork it if you want those things"

     clacke likes this.
   • Embed this notice
     Janne Moren (jannem@fosstodon.org)'s status on Wednesday, 20-Sep-2023 03:26:26 JST Janne Moren

     in reply to

     @hierarchon
     Yes, except for the "small single-dev projects" part.

     You can be a larger, well-funded years old project with multiple developers and still don't want to branch out into features or use cases you didn't plan for or care about.

     I've been tangentially involved in one and it was quite common.

     clacke likes this.