Web Developer by day, and aspiring Swift developer at night.

  • 2 Posts
  • 260 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

















  • dohpaz42@lemmy.worldtoMicroblog Memes@lemmy.worldMozilla be like:
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    10 days 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).


  • dohpaz42@lemmy.worldtoMicroblog Memes@lemmy.worldMozilla be like:
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    edit-2
    10 days ago

    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.