5 ms·
I'm not a contributor but I've worked with core contributors to major projects. This is usually how I see things go down: 1) You work on an open source projec
by jedberg 10y ago
I'm not a contributor but I've worked with core contributors to major projects. This is usually how I see things go down:
1) You work on an open source project and an altruistic company hires you to keep working on it. This is ideal, and I've only ever seen it once (Sendmail hired a couple of core contributors to keep making Sendmail awesome back in the 90s).
2) You work on an open source project, people see the work because they use the project, and then offer you a job to keep working on the project, but slowly over time you are working less on things that are great for the community and more on things that are great for your company. I've seen this a lot.
3) You get hired by a company that uses a big project, and they ask you to start making modifications that are useful for the company. It turns out what you did was useful for everyone so you contribute it back. Sometimes it turns out to be a huge win and so you keep working on it. I saw this with Cassandra and some of the folks at Netflix.
4) You create a cool project and your company lets you open source it. It becomes well known and then other companies want to hire you for either 1, 2 or 3. I saw this a couple times were people left Netflix to go to Facebook or Google to continue work on an OSS project.
If you work on Chromium or Firefox, you'll pretty much be limited to Google or the Mozilla foundation (with some exceptions). So if you want to do it to learn some great code but don't have a particular project that you love, I'd suggest one of the more infrastructure projects that are widely deployed if you want to increase potential job prospects.
In summary: There are lots of ways to get paid to write OSS, but you may not like them all.
- ivraatiems 10y agoThere are companies like Canonical and Redhat that do a lot of work supporting mainly OSS projects. There are also companies like Oracle that are the progenitors of other OSS projects, even if they are no longer the primary maintainers. How do they factor in?
- jedberg 10y agoCanonical and Redhat are usually 1 or 2, depending on the project. Oracle is usually 2 or 3.
- webaholic 10y agoCan you cite the projects which are examples of 4?
- ivraatiems 10y agoNot the parent poster, but Microsoft did this with .NET Core and also supports Mono. Google has definitely done it too, but I am blanking on specific projects.
- justinlardinois 10y agoI'm curious, does anyone else have examples of #1?
- adekok 10y ago5) you start your own company for the open source project you started, and then start hiring people.
- davidw 10y agoThat's a pretty good summary. To make money, you need a source of scarcity: https://journal.dedasys.com/2007/02/03/in-thrall-to-scarcity/ https://journal.dedasys.com/2007/02/03/in-thrall-to-scarcity...
- sytse 10y ago"This is ideal, and I've only ever seen it once" I think this is happening more and more. At GitLab we hired more than 10 people that first contributed to the project voluntarily. Including our CI lead Kamil and VP of Engineering Stan Hu. Our last hire that joined this way was Clement Ho that was an MVP (most valuable volunteer) on August 22nd, 2016.
- jedberg 10y agoI guess it gets interesting when you're an open source company. It could be argued that the people you hire fall into category 2 (doing things the company wants), but since the company is driven by community desire, it's sort of a nice hybrid of 1 and 2. :) (BTW I love GitLab and you guys are doing!)
- sytse 10y agoThanks for your kind words! Number 2 is: "you are working less on things that are great for the community and more on things that are great for your company" => I hope that at GitLab everything we do is good for the community. There is a split between working on great things that end up in the community edition and great things that end up in the enterprise edition (proprietary). Part of the community is using the enterprise edition, so those things are good for the community but at a reduced level. But I hope they are always things everyone can get excited about.
- deleted 10y ago[deleted]
- connorshea 10y agoI was one of the people who first contributed to GitLab voluntarily, its been quite awesome :) Another great example of a company like this is Sentry[1], which is fully open source, although I'm not sure if they've hired anyone from the community so far. [1]: https://sentry.io/welcome/ https://sentry.io/welcome/
- zegerjan 10y ago
- clueless123 10y agoOne more.. You work on an open source project to scratch your own selfish itch.. years later when applying for a job/gig, someone recognizes you or the project and offers you the job on the spot. (happened to me twice!)
- spdustin 10y agoOut of curiosity, what (was|were) the open source (tool|tools) you had written?
- loeg 10y ago(3) is sort of what happened for me. I got hired by a company that uses a big project. Several years later I had the opportunity to move to a team that does upstream open source work, and did.
- Biganon 10y agoAre you that guy from reddit?
- ddorian43 10y agoHe is.
- vram22 10y agoThe Perl Foundation used to fund a few (and may still do), and the Python Software Foundation funds a few OSS projects. Maybe the Free Software Foundation too. Bu I guess the number of such projects are relatively small.
- grkvlt 10y agoAgree. I've done several of these, for example I worked as a contractor at an investment bank where the team I was on developed the Apache Qpid message broker. This was full-time work on an ASF project, and how I got my first commit bit in an open source project. Currently, the company I work for produced an open source project that they donated to the ASF as an Apache project, which I work on full time, as well as contributing to various other open source projects we use as dependencies or are part of the ecosystem. I ended up founding another open source project inside the company, that has now become part of our project line. To make a living developing open source software, this is probably the best/easiest way, and is certainly incredibly rewarding.
- deleted 10y ago[deleted]
- iamcreasy 10y ago> You create a cool project and your company lets you open source it. Why would you need to ask for permission to open source your side project? Is that always the case?