I’m curious to hear people’s thoughts on what principles open source projects should adhere to in order to promote transparency, inclusiveness, and effective development. Are there any specific projects you feel do a great job following certain principles in how they operate? I’m interested in how projects organize decision making, manage donations, incorporate community feedback, communicate updates, and more. Please share projects you appreciate for how they approach open source development!

  • thejevans@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I don’t think they are tyrant but they are a bunch of hypocrites.

    Was this bit meant to illustrate hypocrisy?

    The only thing that I’ve seen the developers say in GitHub comments is things like we are busy and don’t have time for that. And that is after saying this:

    Before opening an issue, make sure that it hasn’t been reported before. And when writing comments, make sure that they actually contribute to solving the issue at hand. Generally it is better to move discussions to Lemmy if possible. We are very thankful to everyone who contributes by writing code, hosting instances, moderating communities, and answering questions.

    Originally posted by @[email protected] in https://join-lemmy.org/news/2023-06-17_-_Update_from_Lemmy_after_the_Reddit_blackout

    There are 217 people who have contributed to LemmyNet/lemmy. The people in charge are the original authors and maintainers, but they are not the only developers by a long shot.

    As you seem to be aware of in the rest of your comment, open source projects like lemmy are sustained because when issues are raised, community members contribute to the project to solve those issues. It’s entirely reasonable and often expected that project maintainers are picky about which issues they personally take on. That doesn’t mean they are rejecting the issue, it just means they won’t personally be writing the PR for the fix anytime soon. I see no issue there.

    • CoderSupreme@programming.devOP
      link
      fedilink
      arrow-up
      1
      arrow-down
      5
      ·
      edit-2
      1 year ago

      when writing comments, make sure that they actually contribute to solving the issue at hand

      The only thing that I’ve seen the developers say in GitHub comments is things like we are busy and don’t have time for that.

      Do I really need to explain to you what the hypocrisy there is? Rules for thee but not for me.

      If they are busy they shouldn’t say anything, let other people contribute something actually useful to the issue at hand.

      • thejevans@lemmy.ml
        link
        fedilink
        arrow-up
        6
        ·
        1 year ago

        Maybe they could be a bit more explicit, but I don’t see hypocrisy.

        Accepting your description of their comments:

        I’m busy and don’t have time for this

        is roughly equivalent to

        I will not be personally taking on this issue, so if someone wants to contribute, this is a reasonable candidate.

        which is good information to get from a maintainer.

        I will say, however, the times they said something along those lines in the examples you gave in your last post, they also said why they didn’t consider it a high priority, which gives more important context as well.

      • severien@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        Rules for thee but not for me

        It’s normal that there are different rules for authors and bug reporters.

        It’s like you’re complaining that there are different rules for guests and the owner of a house.