this post was submitted on 08 Sep 2024
746 points (94.2% liked)

Microblog Memes

5402 readers
3147 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

Rules:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 1 year ago
MODERATORS
ReadyUser31@lemmy.world
746
Mozilla be like: (reddthat.com)
submitted 1 week ago by 101@reddthat.com to c/microblogmemes@lemmy.world
66 comments fedilink hide all child comments
 

Mastodon

you are viewing a single comment's thread
view the rest of the comments
[–] dohpaz42@lemmy.world 9 points 1 week ago* (last edited 1 week ago) (1 children)

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):

  1. Open a respectful discussion with one or more of the core developers to see if they can shed some light on the decisions made.
  2. 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.

[–] Pippipartner@discuss.tchncs.de -3 points 1 week ago (1 children)
  1. 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.
  2. I can't even script properly without accidentally deleting my home directory, so I don't think that's a valid path either.
[–] dohpaz42@lemmy.world 0 points 1 week ago

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).