5 ms·
Here's how you contribute to open source. Start writing some software. Use an open source library. One day, something will break. Instead of whining on the
by jrockway 16y ago
Here's how you contribute to open source. Start writing some software. Use an open source library.
One day, something will break. Instead of whining on the bug tracker or hunting for shitty workarounds... open up the library source, delete the bug, make a diff, and send that to the project maintainers with a note like, "I was trying to call foobar, but it segfaults because bazquux is off by one. Patch attached."
That's contributing to open source.
Alternatively, write some code and share it with people. That's good too.
- pavel_lishin 16y agoI just committed a change to someone's library last week. It was like a lightbulb going off in my head - "Oh, so it's just this easy." I wonder how much more difficult this was before Github.
- davidw 16y ago> I wonder how much more difficult this was before Github. Not much. Open source, and... well, software development in general is about people. Github makes it a bit easier, but the basic process is the same. Here are some programs developed before github: Linux, Emacs, X11, Gnome, KDE, Apache, PHP, Tcl, Perl, Python, Ruby. They turned out ok and managed to garner their fair share of contributors.
- aaronblohowiak 16y agoDealing with weird build chains and getting each projects particular patch acceptance processes correct was pretty annoying. Dynamic languages / more "sane" build systems and "pull requests" have reduced friction, but it is not a categorically different process. The interesting thing is that the friction has been so reduced that GH has made contributing patches upstream my default behavior instead of something I would do if I wanted to commit to being a contributor.
- pavel_lishin 16y agoSure, but I imagine that actually working on the Linux kernel, making and testing patches, submitting them, and having them accepted was much more difficult. Yes, they turned out okay, but that doesn't mean it wasn't much more difficult, right?
- davidw 16y agoThe difficult part is in understanding and working with the code. The rest is 'transaction costs', which are certainly lower with github, but IMO not that big a deal compared to getting difficult C code right.
- kelnos 16y agoWhat does github have to do with the Linux kernel? iIt's not hosted there, and I don't imagine cloning from git.kernel.org and pushing to github would provide much value (not to mention you'd probably blow right past the free account's space limit).
- Scaevolus 16y agohttps://github.com/mirrors/linux-2.6 https://github.com/mirrors/linux-2.6 Github hosts mirrors of a few popular open-source projects, which is handy because they have much better source browsing than the alternatives.
- pavel_lishin 16y agoThat was an example.
- kamaal 16y agoWhen the process to doing something becomes easier it acts as a catalyst to doing things(Increases the pace of things, makes people less stressed out). But that itself doesn't increase the total number of new projects. Doing something new is totally different. What it takes to do nobody knows very clearly. This question has eluded humanity since its existence. You don't find Pyramids like the ones Giza in all ancient civilizations. You don't find literary works like that in India in any other ancient civilization. Sure the process to do anything in those societies may have been a catalyst.But starting something new totally depends on the quality of people who are there and in what many volumes they exist. While git might have made contribution easier, it will not make number of new projects higher.
- iloveponies 16y agoIt wasn't much more difficult. It just wasn't as good looking.
- albertzeyer 16y agoI would say it was. First you have to search for information about where to get the source and where to submit patches. Sometimes even this can be annoying. Then systems like SVN makes it complicated when you want to work on it, try things out, etc., i.e. when you want to produce a patch-series where you could also revert some stuff. I.e. all non-trivial work. You need a system where you can make offline-commits. Then there is some extra work to generate the patch, zip it and attach it to some report somewhere. On GitHub, you just fork, work on it and make a pull request.
- FrojoS 16y agoYou're mostly talking about the free git Software by Junio Hamano and Linus Torvalds [1] not the commercial GitHub [2] system, by GitHub Inc., right? [1] http://en.wikipedia.org/wiki/Git_(software) http://en.wikipedia.org/wiki/Git_(software) [2] Of course, free software on github is hosted for free.
- albertzeyer 16y agoWell, for one part. Whereby I was talking even more generally; any decentralized revision control system can do what I meant. But 'before GitHub' was a time where such decentralized systems where not really in wide use as they are today now (and GitHub has played an important role here). But another important part where I was indeed referring to GitHub: The portal allows easy forking on the site and you can easily make pull requests. That means you don't have to prepare a patch-queue or so which would require additional work. The project maintainer can actually easily look at your fork. The functionality GitHub provides makes it just simpler and more importantly also straight forward, i.e. you don't need to figure out first where to put your patch.
- fhars 16y agoThe real breakthrough wasn't github, but patch by Larry Wall, http://groups.google.com/group/mod.sources/browse_thread/thread/c5240ceb77b7f586/488b0929254d936a http://groups.google.com/group/mod.sources/browse_thread/thr... together with UUCP. In the grand picture, github is just a nice frontend to patch that also replaces UUCP with something more modern.
- jrockway 16y agoI'm a hardcore UNIX fan that hates "social networking", but Github is really a major advancement over patch + email. Here are a few questions that might come up if you aren't using Github: "Is what I'm patching the canonical source?" "How do I set up my own VC for my patchset I'm maintaining?" "Am I sending my patch to the right person?" That adds up to mental friction that distracts from actually writing the patch. With Github, you click a button and get your own repository. You click another button to inform the author (and! other people with their own forks, if you want). The author accepts your patch and the revision history has your name attached to it. It makes it so easy that there is no excuse not to fix that tiny bug. Especially documentation bugs... you don't even need a git client to fix those!
- kamaal 16y agoThe trouble isn't in installing git, or interacting through mailing lists. The trouble is in getting started. In order to contribute to something(fix a bug/develop something new) one has to understand what the expected behavior of the software is, how is it deviating from the current behavior. How and what can one do to correct it. This involves understanding of many things. Technology, the programming language and some CS areas. All of this most of the times a little out of reach of the ordinary day to day to programmer. The problem in simple words is 'The barrier to entry' to contributing most Perl/Python interpreter kind of projects is too high. You need to know a lot to do anything there. I think that prevents most people from contributing even if they want to contribute.
- itsadok 16y agoI'm not an expert in Unix history, but I think that long before "patch" the tool, the output of diff was a script that you could use as a patch by piping it into ed.
- vog 16y ago> I wonder how much more difficult this was before Github. It wasn't really that more difficult. You either uploaded your patch into their bug tracker, or you sent it to them via email. Not a big deal at all. Many projects still work that way. EDIT: Those who downvoted this comment, would you care to explain what's wrong with this statement? That would be very helpful. Thanks.
- deleted 16y ago[deleted]
- danvet 16y agoExactly. All the time while I was studying I've lamented about contributing to open source, especially to the kernel. I've read tons of things, code, os books. I think I've teached myself a pretty good understanding of how it all works (never taking a os course at the university, majored in math). Not a single patch came out of it over the course of almost 10 years (taking the time into account I dabbled around in Linux in high school). Then the massive linux graphics stack rewrite broke my laptop. I've had no clue. Zero. Nada. But I've tried to fix it and actually succeeded somewhat. Then I've noticed that other stuff isn't working anymore in the new graphics stack (it was an old machine and devs were busy porting the newer chip generations). So I've started with more serious stuff. In retrospection, re-reading old mails and patches my lack of clue about the code, process and people is hilarious. But pretty soon some fools started to use my XVideo implementation (despite all the bugs) and reported problems. And I just wanted to get my laptop back into a working order with the cool new linux graphics stack. I've had a reason to ship and users that bugged me. So I've shipped. Now, two years later I'm a major contributor (even managed to once get a top 20 position by patches for a kernel release due to a major cleanup). In a specific area (Intel graphics memory manager) all patches are either reviewed by me or written by me.