I’ve noticed a small issue with my email client for quite some time now where composing a new email will have several blank lines by default.
It’s not too much of an issue to simply delete them but hey, maybe no one had pointed this out before! So I filed a bug report only to get this response… basically it’s not a bug, its a feature!
IMO call a bug a bug. Even if they were to say “yes this is a known issue, we’re aware of it but don’t know when we will be able to work on it” would be 100x better. The client is open source and I wouldn’t mind taking a look at it myself and potentially submitting a pull request.
However, saying “yes this is the expected behaviour” coupled with one closed pull request where someone implemented a “mark all as read” button (clearly a non-trivial amount of work) but closed the request months later with this comment doesn’t make me too eager:
There’s another where someone literally took the vector image that they use for their icon and created a PR to support Android 13 themed icons. After half a year someone rejected it due to only the design team being allowed to make design changes.
Is it something actually open source if
-
It requires a proprietary backend, kept secret
-
Not a single pull request is approved, all contributions are ignored for years, then finally rejected
-
The issue tracker is kept secret
?
“Expected behavior” doesn’t mean “intended behavior.” It just means that it’s a bug they know how to fix but don’t have the bandwidth to fix yet. So it’s not a feature, it’s just a defect that isn’t important enough to remove yet.
Most likely, next time they have cause to open the file that’s causing the bug, they’ll fix this too. Fixing bugs by attrition is one of many ways to keep dev costs low. Well, lower.
