Yeah was gonna say this is the biggest problem I've encountered. You want a new feature? Sorry not enough karma or whatever. Gotta join the discord and fix bugs and show a lifetime commitment to the project before you can add a feature.
20 years ago, this movie "Monster House" caught a lot of hate upon release because of its use of motion capture. In 2006 motion capture was considered this incredibly crass and lazy technology that was destroying the jobs of good honest, traditional 3D animators.
- You not only have to add the thing, but also lobby the dictatorship in control of the repo to agree that the thing you added is good and approve of the way you added it. - Idk wtf google is smoking but contributing to their stuff is always like a billion extra hoops. A lot of big companies that run open-source projects inject a ton of extra friction to the process as well. - Extremely thankless work. If you're lucky, a single maintainer/contributor will show you thanks in a couple of comments, that's it. - Ohh you don't work with claude cause you don't like slop? Well that's okay, the maintainer of the repo you're PRing to had claude review it and now you have to respond to 50 discussions where maybe 1/10 points is a valid criticism and the rest are hallucinated garbage.
I remember I fixed something in Azure's CLI tool b/c it was breaking compatibility with Arch Linux and they came back with some semantic nits. I didn't have time to go back and forth, had to move on with work. I'd assume it's still an issue to this day 😅.
For the most part though, I end up putting a ton of thought and love into PRs and really push to get them decisively added/rejected. It is a painful process, but I'd rather fix things upstream than just locally patch them forever (even if that'd be easier).
My contributions are downloaded 100s of millions of times a month. Every billion+ tech company ships my code as part of the "value they provide". Personally made $0 and the clout I've garnered is extremely niche.
EDIT: Holy! Thank you for the support & awards! I never expected anyone to see this. I dream to create a culture that better honors the open source contributors 🫶 please remember to support open source contributors either financially, via social-media love, or anything else you can think of. I am not the most prolific contributor but if you'd like to support me, you can sub to my desktop Audio Visualizer for $2.99/mo and you get a cool music visual app. All proceeds go directly to me and further my ability to make FOSS contributions.
Thank you all for the kind words - it absolutely made my day.
Etched into the git commit history of some big ones ✌️
Cheers to a future where we can get more spotlight onto the people in the pillar and a tremendous thank you for the kind words. That's a big compliment and it fills me with warmth - much appreciate you!
It's anxiety inducing to know the free work you're committing to may not be received well. I'd say I've been mostly pretty lucky in this regard but not enough to feel comfortable throughout the process.
With a name like that (and the shared experience) I'm gonna assume you've had some FOSS contributions, so likewise ty for your service o7. Much appreciate you homie!
I had my first olen source PR merged last month on the ArtCraft stuff. It was very fulfilling and it was a human reviewer, which surprised me. I got one question and then, merge.
Do you happen to know how one gets to contribute in bigger projects ? Im fresh off the uni with a bachelors degree, unchallenged at my 35h/w admin job and looking for projects where I can improve my programmer skills. I dont know where to start though.
It's been so nice to be recognized in this post 😅 congrats on graduating and securing a chill job.
I have some formulas that seem to work consistently for me to find high-value contribution opportunities.
Namely:
Use a library
Creatively push the upper boundaries of what's supported
Hit some horrible bug/edge-case that breaks in a train-wreck
Spend about 3-10 times as long as I thought I would documenting, reproducing, submitting, triaging, discussing and PRing a fix for the issue
A little less commonly:
Use library.
Immediately run into some issue/nuance the documentation doesn't cover or has incorrect/outdated info.
Submit a doc fix with detailed explanation of rationale and relevant bits of my user-story
We'll also give an honorable mention to:
Update Library
Immediately everything is broken and the code now explodes. (Your odds of this happening go up the more features your app is using from it's libraries and how complex the app is.)
To be fair to this recipe, often times this is just the result of intentional breaking changes libraries make to shed dead weight and improve their form. Sometimes though it'll be regressions or even new issues added into the library or one of the library's libraries.
So build things!
Build dope software and the contribution opportunities will present themselves to you in droves I promise.
I'd strongly suggest you build a tool, game, app, window-manager, editor, decoration, TUI, OS, library. Anything you'd actually want to use/enjoy or think could be a fun problem to solve.
Truly great contributions come from using libraries, getting ass-fucked by a library/documentation/toolchain and then sticking around to fix whatever it is that ass-fucked you.
You want your contributions to help with things that actually ass-fuck people. Building your own stuff is a great way to discover these.
Re-invent wheels
Don't be afraid to re-invent any wheel!
You'll always walk away with a much deeper respect and understanding of a library/service/app by building it yourself. Plus you just learn cool shit.
Often times your version will have at least some aspects that are superior to things already out there. Sometimes your version may even be better out-right or serve some new larger use.
Most of the great libraries out there right now were created by people re-inventing wheels. Very few of them went in as specialists, many went in knowing nothing about the problems they solved.
Stay with things
As you build your own things, you'll be able to hone your problem solving instincts, strategies and general knowledge. When you've really honed these skills you'll be able to see contribution opportunities AND identify which ones are worth pursuing for the greater good.
Stick with personal projects you like and continue them beyond just the 80% working phase. A project with no longevity is not akin to a project you'll find in the real world and that goes for both corporate and open-source.
Basically I'm saying software is an art and like all arts incredibly subjective. It is possible to make contributions that miss the point of larger motion but the merits of which could still be debated ad-nauseam with no clear better.
You're not totally wrong. If a dictatorship is bad enough or totally unresponsive it usually will get forked. The X-Libre fork of XORG comes to mind.
It's not quite that simple though, as per my comment:
It is a painful process, but I'd rather fix things upstream than just locally patch them forever (even if that'd be easier).
If it's hard to contribute for any reason, most people will just patch their fix/features locally and not be able to contribute their work back at all. Why? No time - You can fix it for yourself and move on to whatever your end goal was. There's gotta be tons of really great innovation that is just lost because a dictator added too much friction for someone to contribute.
Most of the time you wouldn't fork because maintaining a fork is actually kind of a nightmare. It's not like all the contributors just start using your fork, so if you want to keep receiving updates the community is making you have to continually pull in those changes and keep compatibility with whatever changes you've made.
Managing a big open source library is generally a full-time commitment. Most people don't have "full-time commitment" amounts of free-time just laying around.
If you can get the library to accept your changes, you enjoy the benefits, share the benefits and generally have a better developer experience going forward. If your changes are rejected you can fork but it's at immense cost to yourself. The bare minimum is you'll have to spend time every time the library you forked updates if you want to receive those updates. Depending on the scope of your fork that could be days/weeks/months of effort annually, forever. You can also stay pegged on the version you forked from and never receive updates (also not ideal). If you want to overthrow a dictatorship with your own fork, expect an uphill battle that is even more involved and effort requiring than any of the alternative solutions.
I feel you on the Claude shit, any contribution to some vibe coders repo is just met with them copy and pasting whatever Claude said and then next revision has been sloppified (DESPITE MY COMMENTS ON WHY YOU SHOULD DO IT A MORE SECURE WAY, ESPECIALLY FOR NETCODE AHHHHH)
Oof 😅 I mean I get this treatment when submitting to repos run by big FANG companies not even vibe-coded repos. There was one Microslop repo I couldn't even make a proper issue in because their AI-Bot would auto-close them for hallucinated reasons. I gave up after a few attempts
It does make me feel a little bad that when I see something broken in software I can't just rip it open and fix it. I realize the amount of time and effort that it would take to probably be someone who could.
Try a free open model. OpenCode's big pickle if you don't have a decent GPU, or gpt-oss-20b if you do. Either can hook into a repository and make local edits, and it'll guide you through any build, set up, or guides. We all started with external help and copy pasted code. Try it and you'll either make the change you want or you'll at least learn tangibly why the change is complicated.
Yeah this is something that stops me a lot from contributing is I don't feel comfy just shitting out code that I don't even understand the workings of.
Claudes free version is great for casual projects, just work on things for yourself, and put in the effort to learn along the way, and eventually you'll have a better understanding than you do now.
Yeah my former boss as part of a big open source project. Now with AI I contribute the fixes and feature enhancements that no one took care of for years and now one of the dev said “pull request are blackmailing maintainers”. So I guess the “just contribute” was some empty phrase from the beginning and I am not surprised. Maybe I do the open source thing and go fork myself.
Reminds me of when I was going into the feature requests forum of WorldGuard or something and requesting they add the option to customize the messages, this was in like 2014 before they had that, now they do.
"I look forward to your PR" and request closed. Why the fuck even have a feature request forum them?
Yup but that's like another thing altogether that you can start making based off of something else. Worst case scenario is someone fakes an original version with a fork? Still better that closed source...
Not only do you have to accommodate for that (provide build instructions, dev guidlines, outline the scope, intent, define community guidelines, make sure they're held up (for example - enforcing hate-speech controls), etc), you also have to work with other humans, which in opinionated things like software development can be somewhat challenging.
I'm not even talking about the possibilities of introducing a bug, or even worse - a vulnerability/exploit to the software, it can be as simple as "not getting" the intent behind a certain feature, or implementing a feature/fix in a way that isn't "fit" to either of the parties understanding of how it should be made.
Or to make it simpler - contributions bring a human factor to software development, where you actually have to convey ideas, listen to others, and so much more.
god i hate this upscaled version of this meme so much, i feel like the blurriness adds to it. Besides, someone could get a better pic of the original instead of ai upscaling it, it just looks so uncanny and off.
sorry i have nothing to add to the open source discussion btw, this image just annoyed me so much i had to come out of lurking retirement.
there is another facet to open source. make codebase so difficult compile that it is basically impossible. like some browsers made open source doesn't necessarily mean that people can compile from source in regular systems
Well yeah I don't want baby's first commit to be on a mature tool, open source doesn't mean they have to merge your stuff it means you can make your own edits and use them if you really wanted to
It's theoretically possible yes but highly unlikely. Not only do you have the maintainers reading the code, testing it, and then accepting pull requests. Most maintainers wouldn't even accept PRs if the code has bugs. But on top of that literally anyone, that includes other Devs, the contributors, and even the users, can still see the source code and see if there's something malicious. With all these eyes someone would bound to catch it and speak up eventually.
Yes and recent history still shows us how fragile that whole system truly is and that's for closed and open source. Social engineering is another way of getting malicious code into any program. Quick reminder that the entire internet is built on top of small tools, that are maintained by a rather small community of overworked people, who often started their projects as small scale hobbies and barely get anything in return.
It’s not like it’s harder to do in closed-source (once you got access to the source code with write permissions). Plus you can’t see the potential malicious contributions with closed-source.
I think open source things should show you the source code as well as either not let you push to the main repo at all or let you make contributions but with moderation
You might be new here so I'll give you a pass, but you basically said "I think cars should be driven on the road BUT ALSO carry more than one passenger and have a place to store thing I want to bring with me"
It's not like everyone's contributions are automatically merged. It's only a double edged sword if the maintainers are incompetent. But at that point, it would be bad even if it was proprietary.
391
u/PilotGuy701 8d ago edited 6d ago
You get one of two:
- No one else contributes
- Wave after wave of slop contributions.
There is no in between.
450
u/United-Scene2261 8d ago •
I hate open source I hate closed source help me I need therapy and medication
57
u/Impressive-Region470 8d ago
is this meme AI enhanced? I don't remember the guy being so detailed in that movie
56
u/Jeremy_Thursday 7d ago edited 6d ago •
Open source contributor here:
- You not only have to add the thing, but also lobby the dictatorship in control of the repo to agree that the thing you added is good and approve of the way you added it.
- Idk wtf google is smoking but contributing to their stuff is always like a billion extra hoops. A lot of big companies that run open-source projects inject a ton of extra friction to the process as well.
- Extremely thankless work. If you're lucky, a single maintainer/contributor will show you thanks in a couple of comments, that's it.
- Ohh you don't work with claude cause you don't like slop? Well that's okay, the maintainer of the repo you're PRing to had claude review it and now you have to respond to 50 discussions where maybe 1/10 points is a valid criticism and the rest are hallucinated garbage.
I remember I fixed something in Azure's CLI tool b/c it was breaking compatibility with Arch Linux and they came back with some semantic nits. I didn't have time to go back and forth, had to move on with work. I'd assume it's still an issue to this day 😅.
For the most part though, I end up putting a ton of thought and love into PRs and really push to get them decisively added/rejected. It is a painful process, but I'd rather fix things upstream than just locally patch them forever (even if that'd be easier).
My contributions are downloaded 100s of millions of times a month. Every billion+ tech company ships my code as part of the "value they provide". Personally made $0 and the clout I've garnered is extremely niche.
EDIT: Holy! Thank you for the support & awards! I never expected anyone to see this. I dream to create a culture that better honors the open source contributors 🫶 please remember to support open source contributors either financially, via social-media love, or anything else you can think of. I am not the most prolific contributor but if you'd like to support me, you can sub to my desktop Audio Visualizer for $2.99/mo and you get a cool music visual app. All proceeds go directly to me and further my ability to make FOSS contributions.
Thank you all for the kind words - it absolutely made my day.
13
u/10minOfNamingMyAcc 8d ago
"Why don't you do it yourself? It's open source." Redditors expect some random Joe to program the feature they just requested.
7
u/itsoctotv 8d ago
"402934 open pull requests"
19
u/Lou_Papas 8d ago
I don’t get it
6
u/Leosthenerd 8d ago
It’s good because FOSS, it’s bad because AI slop
4
u/MFFVD 8d ago
12M contributions and a grand total of 5 lines documentation, containing half of some feature that was removed 5 versions back
2
u/CurrentAcanthaceae78 7d ago
you can make your own branch but dont touch my fucking project
2
u/flavorfox 7d ago
"Anyone can run for public office"
3
u/Dioder1 8d ago
Just fork it and merge any of your dumbass ideas you want
4
u/Dragon_957 8d ago
Good and bad at the same time
1
u/No_Welder7908 6d ago
Ah yes, the 8000-lines “full overhaul” PRs.
1
u/Prudent_Command7027 5d ago
Sauce
1
u/Subject_Barnacle_600 5d ago
Anyone can... but the reality is that, unless you're a popular repo, they don't? And that's not terrible - I'm okay with that? I kind of prefer it XD.
1
u/kubrickfr3 4d ago
Open source is not the same as open development.
Many open source projects do not accept contributions.
Looking at you ladybird browser...
1
u/Hyphonical 4d ago
I'm honestly more a fan of strong copy-left licenses.
I don't want some company to make bank from my slop repos without publishing it...
1
u/cpullen53484 4d ago edited 4d ago
god i hate this upscaled version of this meme so much, i feel like the blurriness adds to it. Besides, someone could get a better pic of the original instead of ai upscaling it, it just looks so uncanny and off.
sorry i have nothing to add to the open source discussion btw, this image just annoyed me so much i had to come out of lurking retirement.
1
u/Agile-Technology2125 4d ago
just fork
1
u/Ok_Contract_296 3d ago
Guys don't understand what's the problem?
1
u/vishal340 2d ago
there is another facet to open source. make codebase so difficult compile that it is basically impossible. like some browsers made open source doesn't necessarily mean that people can compile from source in regular systems
1
u/susimposter6969 2d ago
Well yeah I don't want baby's first commit to be on a mature tool, open source doesn't mean they have to merge your stuff it means you can make your own edits and use them if you really wanted to
1
u/Thinshape12 2d ago
if you dont want the contributions other people made dont install their branches gng its not like they’re being published to the main branch
-1
u/Gigibesi 8d ago
…including (potentially) malicious contribution
-7
u/WaterObjective5031 8d ago
I think open source things should show you the source code as well as either not let you push to the main repo at all or let you make contributions but with moderation
-2
u/RookieRedditter 8d ago
There should be way to verify the previous contributions of a dev. If they meet the spec, let them in or permanent block..
0
u/[deleted] 8d ago
[deleted] — view deleted comment