It’s one thing to be disappointed by a business decision made by a company that you do not agree with, but to be offended by it seems a little much; especially when said decisions aren’t offensive to begin with (i.e., there is no political/religious/sexual/social ties).
I see two possible solutions (there may be more):
Open a respectful discussion with one or more of the core developers to see if they can shed some light on the decisions made.
Become a contributor to the project and make pull requests for the changes you want to see implemented. Of course, talk to the developers first so you don’t waste your time on a contribution they don’t want.
Keep in mind that neither of those options guarantee that you’ll get what you want. Developers do not owe users for decisions they (or higher ups) make on a project. Also, they are not required to accept outside contributions if it goes against their roadmap.
I don’t think that the core developer would disagree much, I think it’s a problem of project decision made by that projects government body which is the Mozilla foundation and Mozilla Corp. So I would need to have a civilized conversation with these bodies executives.
I can’t even script properly without accidentally deleting my home directory, so I don’t think that’s a valid path either.
Talking to core developers can yield a lot of information about a project; both about whatever decision-making body has decided, and under-the-radar things they’d like to see. Plus it never hurts to ingratiate yourself to the folks doing the heavy lifting.
As for contributing, you can do more than just coding. And who knows, it could eventually lead to something else you might like (e.g., qa, documentation, evangelism, etc).
It’s one thing to be disappointed by a business decision made by a company that you do not agree with, but to be offended by it seems a little much; especially when said decisions aren’t offensive to begin with (i.e., there is no political/religious/sexual/social ties).
I see two possible solutions (there may be more):
Keep in mind that neither of those options guarantee that you’ll get what you want. Developers do not owe users for decisions they (or higher ups) make on a project. Also, they are not required to accept outside contributions if it goes against their roadmap.
Talking to core developers can yield a lot of information about a project; both about whatever decision-making body has decided, and under-the-radar things they’d like to see. Plus it never hurts to ingratiate yourself to the folks doing the heavy lifting.
As for contributing, you can do more than just coding. And who knows, it could eventually lead to something else you might like (e.g., qa, documentation, evangelism, etc).