6 ms·
What contributing to Open-source is, and what it isn't
- beckthompson 3y agoUnless I missed something the article never really explained how to contribute to open source software the "right" way so its kind of silly. According to the article there are four ways: 1.) Use open source software (Fair enough but not helpful) 2.) Take over a unmaintained package (If your a brand new developer probably not the best idea! 3.) Make your own thing (Not really what most people want to do...) 4.) Get paid to do it (Not really possible for new developers) I don't feel like any of those are reasonable solutions. I'm not a particularly good programmer but I have just recently been trying to contribute to an open source project (Apparently doing it the "wrong way" according to the article!) and its going amazing! Everyone is very helpful pointing out issues with my PR and helping me understand what to do better. Is it the most efficient use of the maintainers time? As of right now, probably not! However, if I continue to help develop the project them training me now will certainly be worth while as I become better at contributing.
- bawolff 3y agoI disagree. I don't think the article is saying that. The article basically says you should have some connection to the project. This is very much the traditional view - you should contribute to open source by scratching the itch you have. > I'm not a particularly good programmer but I have just recently been trying to contribute to an open source project (Apparently doing it the "wrong way" according to the article!) and its going amazing! Why do you think the article is saying you are doing it the "wrong way"?
- beckthompson 3y agoHmmm after re-reading the article I think you might be correct! > Heck, with proper supervision the kids themselves can help too. You can do open source as a beginner, you don't need to be a senior for that. > But you need to be involved in the project and act accordingly, you don't just go and throw bricks around. I guess I am doing it the correct way! I think the author should have also mentioned this point in the how to contribute the right way so its more obvious.
- Dunati 3y agoRegarding the package maintenance item, that is just an example of something that was right for the author, not a suggestion for the general public. It was something they found useful, used regularly, and happened to be unmaintained. This put them in a position to make a meaningful contribution, beyond padding their work portfolio. This is the whole point of #1. You are in a better position to understand the flaws in software you use, and you have a vested interest in fixing them. Picking a random bug on a random project isn't going to give you the same insight.
- philipwhiuk 3y ago> However, if I continue to help develop the project them training me now will certainly be worth while as I become better at contributing. The problem is the 'if' is a big barrier.
- Alpha3031 3y agoI feel like the article documents the author's own experiences (which, to be fair, is a valid thing to do) without emphasising, or really even trying to emphasise, the how. Which really makes it less useful for anyone looking for learnable takeaways. But hey, it triggered this HN discussion, and I see a lot of replies here which seem more useful for that kind of thing.
- gus_massa 3y agoYour first point is backwards: > 1.) Use open source software (Fair enough but not helpful) It should be > 1.) Send PR to projects you already use. The idea is that you understand how the sofware is used before triying to fix or improve it. It also work for propietary software, dogffod it yourself and use hallway usability test. (There are some examptions like fixing typos or transforming the automatic test suit to be run in github actions, but most of the times it's very useful to already use the project to understand what is the correct fix.)
- beckthompson 3y agoYeah your right, after re-reading the article that was the point the author was trying to get across!
- atoav 3y agoMy best open source contribution (judged by the fact that its founder wanted to meet me specifically when he was in town) was to a project that I use and deeply care about, yet I couldn't contribute as I am not fluent in the programming language used. So I did the next best thing and made an effort to collect a list of UI/UX papercuts and logical inconsistencies, each with a list of proposed options to fix it, sometimes including mock ups how I imagined it could look like. And posted it in multiple well sorted issues once I felt it had a certain level. I did this after giving the maintainer a friendly hint of the things that I planed and told them to not feel pressured to resolve any of that quickly (or at all). He still did and that lifted the software from a usable but rough piece of software to another level. Then as I was already very familiar with the UI I went and write the documentation for the usage. The worst open source contributions are the once where you quickly "fix" a thing that has never been broken all while not coordinating with the other people on the project.
- ticoombs 3y agoUI is honestly what a lot of open source projects need work on. The fact you took the time, made mocks and contributed to the documentation is amazing! People forget that there are more items to maintaining a product than writing code.
- lukan 3y ago"UI is honestly what a lot of open source projects need work on." I agree, but I would assume many maintainers themself would not agree. So the sensitive approach atoav took, (asking first) is probably the right thing to do.
- bawolff 3y agoI think UI can be hard because it is hard to be objective about it. It is critical work, but at the same time if someone came out of nowhere, totally re-arranged all the UI elements, and was just, "trust me bro, this is better", i would be extremely doubtful.
- bawolff 3y agoAs someone who has done open source work, i sadly agree. People who contribute because they want it on their resume or want "experience" without caring about or using the software usually make terrible contributors.
- brainzap 3y agobut this can be solved
- dartos 3y agoHow do u think?
- drycabinet 3y agoexample: apply typo-fix PRs as commits by the maintainer, so that only those who are genuine will submit those.
- prepend 3y agoI agree. It can be reduced through PR review and since it’s public, people who make low value contributions are easier to spot than in non-OSS projects where the same vanity contribs are harder to see. I’d say that if I saw bullshit open source contribs on a resume it would be counterproductive. So I think people may do it for t-shirts, but to list as experience seems like it doesn’t happen as much as it seems it may.
- JTyQZSnP3cQGa8B 3y agoThe whole thing is ridiculous. He compares a curious nerd with the hacktoberfest disaster in order to discourage people, and then describes what happens in a professional context where you are paid to code. A "senior" developer with less than 10 years of experience, an empty GitHub repo, and a fake degree should be more humble. Sorry for the rant but he’s not helping anyone. There are abuses, but we should encourage juniors, not describe the open source world like that.
- pauby 3y ago> A "senior" developer with less than 10 years of experience, an empty GitHub repo, and a fake degree should be more humble. This says more about you than it does about them. The author is offering an opinion. You can disagree without resorting to this. You need to be better than that.
- BoingBoomTschak 3y agoAttacking the authority of people who start their article with an appeal to said authority isn't really far-fetched.
- erikbye 3y agoAnother red flag is "I use Arch Linux, btw"
- janosdebugs 3y agoOpen source can be a wonderful thing when people come together and build something cool. Unfortunately, maintainer burnout has been a thing recently and part of the reason is that IT and open source are seen as a way to get a lucrative job. Some (and by no means all) people disregard the consequences of their actions to get there. Juniors should absolutely be encouraged to either build a project on their own or collaboratively, or to start by joining the community and listening before starting to write code. This is something that's lost on many and "drive-by PRs" happen a lot on high profile projects from people just wanting to say "I'm an X contributor" on their CV or get a coveted t-shirt and never come back again. These drive-by PRs come in a variety of forms. Some are just absolute nonsense, some rename things for no good reason, some refactor a part of the code that nobody asked for, and some do add a tiny bit of value, but are extremely bad quality to the point where rewriting it would take less time than going through several (dozen) review rounds explaining to the budding contributor how to write code. (Or how to even use git. Rebasing a PR is a problem for a lot of people, for example.) Maintainers of open source projects typically didn't sign up for being mentors to people who barely know how to code. More than that, these random PRs increase the noise level in the project by a lot and take away time from the contributors, junior or not, who put in way more effort that a drive-by PR author did. Leaving PRs to rot is bad because they will start having conflicts, so not reviewing them is not an option. Each of these PRs needs to be properly reviewed because they have a maintenance cost later that rests on the shoulders of the maintainers, not the contributor. Each PR carries the risk of someone introducing malicious code. Answering these PRs politely but firmly also takes quite a bit of effort. Yes, juniors should be encouraged, but realistic expectations should be set. Contributing code to a highly complex project probably isn't going to happen. They should try and contribute to small projects that they themselves know and use. That way they understand what is good an what is bad for that piece of software. Also, they should "read the room" and the contribution guide before jumping in. The best way to start is with small things: reporting issues, fixing docs bugs, and once they are comfortable with the workflow, move up to writing code. Unfortunately, communication is hard and getting this message across ("be considerate") to the right people is harder. This post has a good analogy for that with the bricks.
- noufalibrahim 3y agoMany of these efforts work best when they are consist of a small group of competent elites. There is a path to get in there for everyone but the bar is high. I get the good intentions behind democratizing this but that, coupled with companies using contributions as a metric, leads to the original (fragile) system being damaged. In spirit, I agree with the article.
- globular-toast 3y agoTotally agree with this. Been a free software advocate my whole life. It's all about freedom to tinker and contribute should you wish to. If you use computers you'll know when the time comes to do that. It's usually when the software doesn't quite do what you want or there's something you need that nobody has thought of yet. It's up to you whether you just hack it for your own purposes or put in some extra effort to get the code merged upstream. Definitely recommend the latter if you want to learn how to contribute to a live codebase (free or otherwise). But don't go in with the goal of getting something merged, it's got to start with your problem. Anecdotally, some of the best hackers I've known have started off as kids building things like game mods and chatbots and the like. Then later they've learnt how to do it "professionally". The worst are the ones who know how to make a pull request etc but have never been through the trenches solving a problem that nobody else has.
- rvz 3y agoThe only valid advice given by the author is that open source contributions work much better if the person is paid or sponsored to maintain it. Other than that, do not listen to the authors advice. 95% of this article is terrible advice and at this point wastes the student’s time for free work, which is not sustainable for open source at all. They are better off building a startup and making money out of that to fund open source projects whilst getting paid or paying others for it. The majority of companies are already doing that. Otherwise you will end up with a wave of unmaintained packages, abandonware and no community picking it up for the long term maintenance. Overall this is another article pontificating ‘a right way’ for students when open source is already a thankless ecosystem where maintenance is paid in time with little to nothing in return. This is why lots of open source developers complain that no-one is paying them as they are extremely bad at pricing their own time and end up doing free work for years… …Because companies want you developers to be happy to rip off your valuable time for free whilst your scream: ‘x company is using it!’ yet they are exploiting you by them not paying for your time.
- firesteelrain 3y agoThe way I thought the article was going was that it’s pointless to contribute to open source if you don’t know what you are doing. The contributor needs someone to show them. Which is a great point - how are we actually mentoring the junior engineers so that they can take over some day?
- mfuzzey 3y agoThat's not what I get from the article. More that it's pointless to contrinute to an open source project if you're not interested in improving the software the project is building for a reason that matters to you. That's true regardless if you know what you're doing or not. So if your objective is just to "get a PR merged" that's not really helpful. Rather it should be to "fix this bug" or "add this feature" because those things somehow matter to you. The "you" can also mean your employer. So if you use some software as part of your job and it's got a bug or is missing a feature that matters enough to you then fixiing it and contributing it back is a perfectly valid and great way of funding open source. It's also not normally philantropic, because when you make the effort of getting your changes merged upstream it also reduces your own long term maintenance burden of having a private fork.
- kzrdude 3y agoThe best advice for starting out is just to start hacking on your own projects. This is the first stepping stone for being able to jump in and positively contribute to other's projects later, I think.
- Levitz 3y agoIs it really? I'd posit this isn't even really "open source" 99% of the time. Github is absolutely littered with hundreds of thousands of repos that nobody but their original creator has ever looked at. "Make your own project" sounds good, but in practice it almost always means "Make a personal project and make it public". You don't reach the point in which you have to handle issues, or contributions, or pull requests or anything because the vast majority of the time, projects get nowhere, it's open source only in the most literal sense. Also I'm not sure I see the logic even if the expectation is to make a successful project. How can someone who has a hard time meaningfully contributing to a project possibly manage a whole project?
- johannes1234321 3y agoIs that bad in any way? People do their projects for their own motivation. If nobody else cares so be it.
- kzrdude 3y agoYes it is really, I think. The self-motivation is one thing. If you build it yourself it's because you either need it or want it enough. If you build something you get self confidence based in reality and experience based in something. It is expected that only few of the personal projects are ever interesting to someone else. Maybe hacking on some small stuff for four years is what you need to be able to graduate to know enough real world stuff to contribute to bigger projects in practice, then that's just how it is. Now I think of neovim and it's ecosystem right now because I'm in that phase, but most of the small plugins are driven by single people alone, and they can still have a ton of users. Is it still open source? Yes, it's open source if it has an open source license. You are correct that an open project and open source are not the same thing and don't need to be.
- 3y ago
- palata 3y agoThat's a lot of words, but I'm not sure what I get from them. Here's my take: If you want to contribute to open source, start with using open source software even if there is a better proprietary alternative. Only when you use code can you contribute meaningfully to it. Maybe it's a bug fix, maybe it's a small feature you need. Maybe it's a package for your distro. Whatever you need. And if you actually need it, then the best way is to do it in a fork and use it. When you feel like it works for you, offer to contribute it back upstream. It is fine to ask guidance to the maintainer while you do it, but don't expect them to work for you. Avoid meaningless contributions just for the sake of contributing, like making a package for a distro you don't use ("I use Ubuntu myself, but let me contribute an Arch package I won't ever test"). Or features you don't need but think would be cool. And stop opening 10 feature requests per day: either you code them or you don't, but nobody cares about what you think would be good features. Bug reports are fine if you give proper instructions to reproduce ("sometimes it fails for me plz fix" doesn't qualify as "proper instructions"). And always remember: whatever the maintainer(s) merge becomes their burden, meaning that they don't do it lightly. If they don't want your contribution, don't take it personally: maybe they can't commit to maintaining it, or just don't feel like maintaining it. It's their right, you don't pay them. Just keep your fork in that case.
- gwd 3y agoThis is pretty much exactly what the article says.
- palata 3y agoWe have a pretty different definition of the word "exactly", then :-).
- markx2 3y ago"Only when you use code can you contribute meaningfully to it." I disagree. I started using WordPress in January 2004. I was invited to join Automattic in 2006. I never once wrote any code or even tried. What I did do was a huge amount of Support in the wordpress.org forums, and I write the first guides covering everything from changing your password in the database (there was no other option at the time), how to insert adsense, lots of CSS stuff and more. I know of other current Automattic employees who came that same forum route. Code is needed obviously, but you also need people who will support others in using the program you create. When I started in the forums I would see the then current WP devs replying to questions. Matt in particular would reply, but he replied as a dev would talk to another dev. He was always technically correct but he wasn't really good at explaining. I - and others - could explain in a way that people understood. I would like to think that the very positive and helpful way the forums were run was a helpful step when people were looking to what blogging software to use at that time.
- dmezzetti 3y agoI tend to agree with this sentiment. Many junior devs and/or those in college want to contribute. Then they feel entitled to merge a PR that they worked hard on often without guidance. I'm all for working with people but projects have standards and not all ideas make sense. In many cases, especially with commercial open source, the project is the base of a companies identity. So it's not just for drive-by ideas to pad a resume or finish a school project. For those who do want to do this, I'd recommend writing an issue and/or reaching out to the developers to engage in a dialogue. This takes work but it will increase the likelihood of a PR being merged. Disclaimer: I'm the primary developer of txtai (https://github.com/neuml/txtai https://github.com/neuml/txtai), an open-source vector database + RAG framework
- imtringued 3y agoI don't know how you managed to do it, but you slipped in a critique of classical and neoclassical savings theory in this blog post with your school article. In classical economics, people must build the bricks before they can build the school. This sounds like the obvious and correct way to do it from a thousand miles, but as you pointed out, bricks produced by an uncoordinated group of people is going to result in a bad outcome. On the other hand investment preceding saving sounds impossible, right? How can you invest something that doesn't exist? The bank gives you a loan using created money that does not exist. You use this money to order bricks from the brick factory. You then wait for the bricks to be produced and delivered in the future. The bricklayers get paid and save the money created by the loan. This way, the bricks meet the specification of the architect. The money held by the bricklayers is an implicit claim on the school. Each dollar represents a brick in the school. This is how the organisation of labor is coordinated in a market economy. The problem with open source software is that there aren't organisations from which you can just "hire" contributors from. Instead you must already have the skills and then get lucky they don't reject your contributions before you can even think about becoming a member. It's the speculative brick problem all over again.
- snowstormsun 3y agoOpen Source Maintainers shouldn't judge the people trying to contribute, but the contributions. If the contribution is misguided or not good, it's their responsibility to reject it. On the other side, if the contributor's intention is to boost their resume, but the contribution is also good and an improvement, so be it! Good contributions are too rare to only select the ones done with selfless intentions...
- arp242 3y agoThis is one one of those things that sounds nice in theory, but falls down in practice, because in reality the overlap between "spammy junk" and "contributions done purely to boost resume" is very close to 1:1. I'm sure there's the odd exception, but it's rare. So in practice "judging the contribution" and "judging the contributor" are identical.
- nrabulinski 3y agoThey aren’t really. Even if the overlap was completely perfect and all spam contributions were the ones done to boost resume, you still shouldn’t judge the contributor for trying to boost their resume but judge the contribution by how useless and spammy it is.
- dartos 3y agoJudging by the Jia Tan situation, I think maintainers should judge contributors as well. It’s the maintainer’s job to be defensive of their projects and prevent them from being abused. It’s not necessarily their job to build and foster a community.
- hirsin 3y agoWhat does it mean to judge a contributor? They're a faceless account, maybe a dog on the internet. Isn't the contribution the defining piece of work? Maybe for growing your maintainer collection, with privileged access, but not contributions?
- 3y ago
- pfdietz 3y agoI contribute to an open source project by doing extensive testing. I've been doing this off and on for more than two decades. I don't fix the bugs I find; the people who do are much better at that than I am. But I like to think I've gotten good at finding bugs, and try to find new ones as soon as possible so they can be fixed before formal releases.
- brainzap 3y agorespect
- lagt_t 3y agoDo you recommend any bug report template?
- pfdietz 3y agoThere's a bug tracking system associated with this project https://launchpad.net/sbcl https://launchpad.net/sbcl I include (1) minimized input that can reproduce the bug, (2) a copy of the error and stack trace, or of an incorrect output, and (3) identification of the specific version of the software (a git id) and the architecture it was compiled for (typically x86-64). Example: https://bugs.launchpad.net/sbcl/+bug/2063205 https://bugs.launchpad.net/sbcl/+bug/2063205
- johngossman 3y agoThe author seems to have forgotten that most schoolwork is also not something the student is passionate about, and the value of apprenticeships. Of course it would be better for students to work on something they love, but that needs to be weighed against working in a community, on a codebase, that will maximize learning.
- johngossman 3y agoThought about it so more. I’d say it is more important who you work with than what you work on (that’s also important).
- deleted 3y ago[deleted]
- newswasboring 3y agoDoes anyone else find the sentiment of this post a bit... gatekeep-y? The way I read it, the author discourages people from just going out and trying to contribute to a random project. The reason given is because you would be bad at it as you don't know anything. But then the author gives the example of maintaining an AUR package and they got it to work because they needed it. From my point of view both these paths lead to the same result, a person arrives at a project with objectives they don't have the skills to build. (Unless the argument is to only try to contribute when you have all the skills needed, and that is just straight up gatekeeping). Edit: Spelling and typos
- oooyay 3y agoI don't know that gate keeping is the right word, but I think it's doing a lot in the way of speaking for a number of projects (near infinity) that the author can't possibly represent. I comaintain a piece of infrastructure software that is fairly complicated - it fits the analogue of a commercial building. Setting some arbitrary bar for when to commit would frankly put just a few of us ever working on the project. When newcomers have a thing they want to do we spend a while talking it out in issue comments, then we modify that strategy on the actual PR as needed. To be quite honest, there are parts of this codebase I forget the nuance about all the time, so I'm really only a step or two more familiar than someone that knows the language and can write to the problem they desire to fix at any given time. Most of my job is reasoning about, "should this feature be in this project" and maintaining some bar for quality in merges. I can always push the latter along if worse comes to worse.
- erikbye 3y agoI found the article to be terrible, and his school building analogy falls flat on its ass. Both junior and senior developers can and should contribute to open source, for a variety of good reasons and there are good ways to go on about it.
- 8372049 3y agoDid you read the last 2/3 of the article?
- _wire_ 3y agoWhen is a title not a synopsis of the article? Here's the rundown: - I am wearing a hacktoberfest t-shirt. - Some things are good, some are bad, including hacktoberfest. - Trying to contribute to a project you know nothing about is bad. - Unnecessarily belabored "build a school" homily with digression into importance of listening to parents and teachers. - A weirdly a-contextual Viking comic that injects the word fuck for no reason. - Something about Arch Linux. - Wanting something not getting it... "infuriating!" - Note to self: Contracting for the French gov. can be a good gig. OK THANK YOU FOR THE INSIGHTS All of this jibber-jabber can be reduced to a simple point: Contributing comes down to being helpful. If what you are doing is helpful then you are contributing. — What it is and what it ain't https://m.youtube.com/watch?v=uyXE4saB6RU https://m.youtube.com/watch?v=uyXE4saB6RU
- thomk 3y agoId like to contribute to a large project like Linux or python by writing docs, testing or some other non development activity. Is that possible or needed? How would I go about doing that?
- ericyd 3y agoBuilding your own thing is great, but one unintended consequence is that if your thing actually becomes popular, you'll be expected to maintain it forever. If your interests or preferred tech stack change, you are stuck with a mountain of your own tech debt. Chances are no one will ever rescue you. For juniors who barely even know that their own preferences are, much less their long term career goals, this can be a serious downside. When I was just starting, I had a side project that got reasonably popular but I never expected to be maintaining it years later, and it became a serious mental burden. I think the author is correct that you know you're doing it right when it feels like a chore, but it is kind of a bummer if a junior gets sucked into this maintenance burden without understanding the consequences. As a more senior developer, I think long and hard before seriously committing to a new open source project, and ask myself if I want to be maintaining it in several years before I write a line of code.
- supernikio2 3y agoDoesn't the very nature of open-source mean you can just abandon it and have someone else take up the torch when you're done maintaining it?
- cjpearson 3y agoThis is a good point and thanks for sharing. I would add that in my experience the bar for "reasonably popular" is much lower than people would typically expect. One or two issues a month may not be much if you're actively using and maintaining the project, but it can easily become a burden if you've moved on from the project. You either spend a few hours a month keeping it up to date, or feel like you're letting someone down. There isn't really a good solution to escape. Someone may submit patches on their own or offer to take over maintenance, but I'm not willing to ship code that I haven't reviewed or tested and would not risk transferring it to someone unknown. (We've seen what can happen there.) Deleting the project is an option, but that also negatively impacts existing users in a drastic way. The best approach I think is to clearly indicate that the project is no longer maintained and suggest creating a fork if they need to make changes.
- keskival 3y agoDoesn't the same thing apply to corporate software? Pass a LeetCode hard and bring a backpack full of bricks, and go for it?