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!

  • fafff@lemmy.ml
    14·
    2 years ago

    I feel one of the most important things for a thriving open source project is easy onboarding.

    Statement of friendliness and similar are not that useful if I don’t know where to start to contribute to your project. A clean, up to date CONTRIBUTING file goes a long way, architecture documentation is extremely good, optimal is having an experience developer checking your patches and offering help.

    Repositories that I contribute to the most helped me in the first phases of the journey, it was awesome, I gave back.

      • glad_cat@lemmy.sdf.org
        11·
        2 years ago

        It is their project, their code, their processes. They do what they want. I hate when people tell me what to do on my own projects.

        GitHub (and the others) are more inclusive than ever: free to fork, free to work.

        You’re describing and demanding additional work that takes time, and that they may not want to do at the time. If you want it, fork it and do it since it’s free for you.

          • severien@lemmy.world
            6·
            2 years 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.

          • gian @lemmy.grys.itEnglish
            1·
            2 years ago

            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.

            So people can come up with “the maintainer do not answer to the community” drama ?

      • gian @lemmy.grys.itEnglish
        1·
        2 years ago

        I don’t care that much about those examples, what I really care about is them not following what I consider to be some important principles when it comes to open source projects.

        Did you realize that nobody is stopping you from forking any opensource project you want and then to follow whatever rules you want, right ?

  • Avid Amoeba@lemmy.ca
    11·
    2 years ago

    Open source isn’t some special ordinance that makes a software project subject to any principles other than the ones outlined in its software license. The most basic principle being that someone wrote something which they thought could be useful for others and therefore published it under an open source license. If by releasing a piece of software I were strongly expected to adhere to any other principles like some of the ones you’ve suggested elsewhere, I wouldn’t have released half of the stuff I have because I simply can’t uphold these principles. Upholding them isn’t free. It requires work which I don’t have time for. I’ve already shared the work I was able to do by releasing as open source.

    Edit:

    I see a lot of confusion among what I assume is younger people who are relatively new to open source. Confusion as to open source being about freedom of choice, inclusion, democracy or what have you. It isn’t. Some open source projects may be about one or more of those things. Many, even possibly most aren’t. For example the Linux kernel is a hard dictatorship with Linus as top executioner. Convincing people of varying software engineering proficiency of why their favorite feature shouldn’t happen or why their PR is garbage and will decrease the quality of the project in various ways takes way longer than closing the respective item. GNOME is famous for “Closed/Won’t fix” with no explanation. Perhaps if open source developers were handsomely paid to spend the extra time to be nice, things could be different. Of course that implies that more developers must be paid to do the work since everything takes longer, or the pace of the project would be slower. Pick your priorities and pay for them appropriately.

  • mo_ztt ✅@lemmy.worldEnglish
    91·
    2 years ago

    Dude, please take this with all the kindness in the world, but to me it looks like you asked some questions yesterday about contributing to Lemmy, you got answers you didn’t like, and now you’re asking the exact same question in a much more indirect way in hopes of steering the conversation back to what you want to hear and how you like to look at it.

    I and the other people who gave you answers before are trying to help you be more successful with your contributions. We’re not trying to criticize or put you down or anything. I might be right or wrong about this or anything else, but I think it’d be to your benefit to slow down and really listen to what people are saying and how you can contribute in a good and productive give-and-take way, instead of just making your list of demands for how everyone else needs to be.

    Or not. It’s up to you; just that’s my recommendation based on my limited knowledge of the situation.

  • Pantherina@feddit.de
    6·
    2 years ago

    I like KDE in how they approach new users. There are some people like Nate Graham investing so much time into talking to stupid bug reporters like me.

    Having the first “start contributing” link be a Matrix Group is also nice, instead of some Git instance.

    Change my mind, but I think Git* is horrible for collaboration if you use it exclusively

  • Daniel Quinn@lemmy.ca
    4·
    2 years ago

    This post (and your comments here) read like a thinly veiled attempt to justify your existing beliefs rather than an honest attempt to acquire feedback.

  • it_a_me@literature.cafe
    3·
    2 years ago

    I like curl’s standard and trasparent release cycle. The consistent feature freeze before releases seems like a good idea to prevent bugs.

  • LazerDickMcCheese@sh.itjust.works
    2·
    2 years ago

    I’ll humor you and give my input. If someone is making a FOSS project, get at least one person on your team with rudimentary social skills. Make them involved with support. Because as a simple user, “just use Discord” or “just use Linux” is not an answer to a tech problem, and it can sometimes be insulting to have the go-to people avoid answering the question

  • wiki_me@lemmy.mlEnglish
    1·
    2 years ago

    I would say good fund raising is often important, thunderbird and blender are good examples.