Repository navigation
Replies: 4 comments 1 reply
|
uBO is considered a complete software. Feature requests are mainly considered when they're made by list maintainers (or other long time contributors) for new filtering options/scriptlets, etc., when the current one can no longer handle some issues. Feature requests will be considered if they're well explained with examples how this would serve a significant part of the userbase. Obviously feature requests are low on the priority list. Bugs always come first. uBO is not alone anymore, there is also uBOL to consider. It's being actively developed and features are more likely to get implemented if they're also for the benefit for all/most. Feature requests cannot undermine the efficiency goal of both extensions. Yes, it's easy to say "just fork it", but contrary to that article, failing forks just prove the features and their maintainers were not popular/dedicated enough. They would just bloat the original software's code and make it more difficult for the original developers to maintain it. |
What are these expectations, and how are they being ignored? When considering the amount of time and effort that is put into the project by gorhill and the rest of uBO team, your statement is incorrect and frankly insulting. Thousands of issues have been addressed, and many enhancements (including feature requests) have been made to both uBO and uBO Lite. |
|
Keep in mind, there's only one dev for the uBO project, so don't expect any speedy developments. |
|
That article thinks it's delusion because those people just want to add the features and then ASK the original devs to maintain their ideas. They want less work from theirs and want more work from others right away. If anyone thinks your ideas are good and you really need it, just do and maintain it yourself. Think that you are helping yourself with it. Don't seek and ask for popularity and help from others. That should come from others' own voluntary. And yes, saying "no" is the key for this project to not burnout: https://www.jeffgeerling.com/blog/2022/just-say-no/ Do you know that how many volunteers here have already dropped due to burnout?
Incremental changes are keys to make the project sustainable in the long run. Many feature requests related to specific issues from specific sites were addressed quickly and improvements over time for those features are also slowly developed. Did you actually read the changelogs over time: https://github.com/gorhill/uBlock/releases and see how many Many feature requests just want really big changes without acknowledging any specific paths for their ideas. They don't care about how the changes should be developed incrementally and they don't care about the work labour it would take. They just assume that the devs should take those work freely themselves. Those will be invited to scratch their own itches. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is post is more "emotional" and social rather than technical. It can be summarized as follows:
I feel empathy for both sides, not just because "I've been there", but by looking at it "from the outside". However, it still feels unsatisfactory from either side. Yes, life is full of trade-offs, and our convictions guide us and tell us what to prioritize, but something still feels "off" to me.
To elaborate on the user side, I've recently read this blog-post (see also HN comments) which could be used as a counter-argument to the anti-"your software" argument.
But there's a saying that describes most maintainers of FOSS projects:
What do y'all think? Is this something that we should talk about, or am I concerned about a non-existent problem?
All reactions