Disclaimer
Not trying to blame anyone here. I‘m just taking an idea I‘ve read and spinning it further:
Intro
A lot of people use free open source software (foss), Linux being one of them. But a lot less actually help make this software. If I ask them why, they always say „I don’t have the coding skills!“.
Maybe its worth pointing out that you don‘t need them. In a lot of cases it’s better to not have any so you can see stuff with a „consumer view“.
In that situation you can file issues on github and similar places. You can write descriptions that non technical people can understand. You can help translate and so on, all depending on your skills.
Other reasons?
I‘d really like to know so the foss community can talk about making it worthwile for non coders to participate.
I have a background in Games, UX, Service and Product design and I would really like to contribute to FOSS projects but have no idea how to
I’m unfamiliar in the etiquette of GitHub and how I could contribute my skills
Happy new year. I took a couple days off from socials to recuperate.
Those are important questions that youre asking. Like in any team, its about achieving a goal together. The goal often is as important as the cooperation. If you see someones mistakes or think this could go better, its important to help them understand. Obviously, this doesnt always go without a hitch.
Just go to your favorite github page that uses stuff you understand (programming language, technique or whatever) and look if there are issues listed. You can check for pull requests (community made patches) and if they actually get pulled. If yes, find a issue to work on, create a branch, fix something and create a pull request.
If you need more help understanding this google github tutorial or first pull request. There are a lot of repos that auto accept your pull request to show you how its done.
Good luck! :)
I think the biggest issue with this would be that it would require non-technical people to use ticketing systems (have you ever worked in admin IT?).
They tend to put things like, button broken, or will not load, which are not necessarily helpful tickets.
I have worked in IT on and off for 20 yrs so I‘m quite familiar with tickets. The problem is mostly the organization. If you have a hybrid like me who has seen many jobs, you have no problems with tickets. The issue is reducing the headcount to the most skeleton crew as possible and then letting high profile coders take tickets from IT noobs. Thats a bomb just waiting to explode.
I really appreciate your reply, the honesty and the positivity of it. Pretty sure you‘ll do great participating in projects. I can relate when it comes to getting flamed and dumped on pretty much anywhere. Often its just misunderstandings but people in general can be jerks. Feel free to contact me if you need help with github or project stuff. Have a good one.
Because FOSS devs think the “consumer view” is wrong and the software should correct it, not the other way around.
I think a major deterrent from contributing things that aren’t code is that whoever is implementing it might think their design is better just because it’s theirs.
Try talking to the GNOME team, for example. You will never be able to get a suggestion past them because they’re always right and you’re always wrong.
Even when you prove them wrong and they backpedal, they are still correct and you are still wrong.
I ran into basically this with home assistant. Commented on an issue about an integration to point out that it didn’t work at all, and to support another user that had rewritten it in a way that fixed it. The approval dev jumped in to say that they only permit single changes to be approved. That’s fine, I guess, but to fix the issue multiple changes were necessary. The user that had rewritten it then tried to limit the change to a single fix, but because that didn’t resolve the issue they blocked the change. The integration still doesn’t work and the user stopped trying to fix it.
I totally believe you.
That kind of rigidity in software design leads me to believe more people need to read The Pragmatic Programmer.
I, of course, do not; because I am already a pragmatic programmer.
Gee if someone wants to fix an issue they can be my guest, that way I don’t have to deal with it. It’s not that people aren’t pragmatic it’s that they are little generals of their own world and they don’t want to give that up even if it would make the world better.
I’ve met some absolute Napoleon’s in my time programming. I don’t know what it is that attracts them, perhaps it’s that programmers historically tend not to have very good social skills in general? I don’t know, but it’s weird. You’d think they’d all be total nerds and be somewhat deferent, but nope.
You will never be able to get a suggestion past them because they’re always right and you’re always wrong.
I said similar in another comment. The Lemmy devs are the same.
I mean, you‘re not wrong. But I think you’r example applies to far more than you think.
I think the reason we are in a dystopian hellscape is because people need to be always right and never say sorry. That is why the master manipulators are running our countries and economies. Because then you can be always right, poor and exploited but always right.
The movie idiocracy is a perfect depiction of our current world.
But I think we can make it happen nevertheless. We need to tackle points like yours and take them serious. This would be excellent in a code of conduct for the foss community to take on.
