this post was submitted on 23 Sep 2024
153 points (98.7% liked)

Opensource

1428 readers
32 users here now

A community for discussion about open source software! Ask questions, share knowledge, share news, or post interesting stuff related to it!

CreditsIcon base by Lorc under CC BY 3.0 with modifications to add a gradient



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 24 points 2 months ago (1 children)

Same with me. I asked upfront if they would accept a PR for a minor change. I described the issue in detail and my proposed fix.

He said sure.

I made the PR.

Same guy comments, "Wtf do you need this for?! We already have X solution with Y features."

I reply back, "Because Y doesn't cover Z use case, which is what I need it for."

The issue was closed without further comment.

[–] [email protected] 9 points 2 months ago (1 children)

I got a single class that supported new hardware written for a controller. They said they don't want the overhead of maintaining an additional class for new hardware (a class that doesn't change ever btw). I thought whatever, works for me, doesn't need to be on the repo and "I got mine". I have since seen 3 people asking if the hardware is supported / asking for it to be implemented. Oh well.

[–] [email protected] 13 points 2 months ago (1 children)

In that case I'd point them to your fork with a link to the PR where they maintainer chose not to include it.

[–] [email protected] 9 points 2 months ago

Why? To start problems for me from pissy maintainers when I need help with something?