Live data from Hacker News

Ask HN: Getting paid to work on open source full-time?

news.ycombinator.com

31–40 of 69 posts

Re: Ask HN: Getting paid to work on open source full-time?

#31
post #30
post #28

This is an interesting question, because I'm in the process of looking to hire an engineer to work full time on contributing to WordPress. The twist is I'm looking for someone who is currently not part of the WordPress Community , which has made the search interesting. I know WordPress has a mixed view here on HN, but that's kind of the point - we're ( http://wpengine.com ) looking to bring some "outside blood" with…

Could you offer some insights why many engineers dont want to work full time on open source?

Sure, these are the kind of concerns engineers raise when you talk to engineers who are right for the job but not worked on OSS before:

* Perceived job security, especially developers with mortgages, families, etc. Going from a core-function role within a company to working on OS apparently feels like less job-security.

* Don't want to move from working in office environment to (probably) working from home.

* Project politics and different working relationships of "peers" - not aligned colleagues for same employer.

* Not considered the most financially lucrative engineering positions in terms of performance bonus or career progression

Re: Ask HN: Getting paid to work on open source full-time?

#32
WalmartLabs has a few teams working on mostly open source stuff: github.com/spumko and github.com/walmartlabs. The spumko team (the one I am on) used to be 100% open source work but has recently cut back in the short term to help out other internal teams. But, OSS is still a major component of our jobs.

Re: Ask HN: Getting paid to work on open source full-time?

#33
Me and my team work full-time on a popular open-source project. Based on our collective experience I can tell you about 3 different ways.

- The first way is to become a key contributor and maintainer for an open-source project with significant financial backing, and then get co-opted by one of the organizations providing the backing. As an obvious example, a significant Linux contributor or maintainer will have no problem getting a job at dozens of technology companies. In our case, we are constantly scanning the mailing list and irc channel for the most consistently helpful and reliable contributors. If you follow this route, make sure you pick a project you're passionate about and won't mind working on for a long time, focus on being reliable rather than impressing with your technical skills, and make sure to go beyond adding cool features: help other users, improve the documentation, review patches, fix small bugs, etc. I can't emphasize reliability enough. In a really successful project, the maintainers are usually busy and overwhelmed with demands. Be the person they can rely on, consistently, and you will earn their trust.

- The second way is to join a technology company with an open-source team, and be assigned to an open-source project. For example 2 of my co-maintainers joined as employees before the open-source project launched, and were assigned to this team via the normal company process. This will usually get you into a project in its early stages, when it is not yet large or popular enough to hire from the pool of existing contributors. In our case, we now hire almost exclusively out of the project's community.

- The third way is to turn your own project into a source of income. This means either hope that your project becomes popular enough to attract financial backing on its own (also known as "winning the lottery"), or secure funding yourself. Remember that open-source software is like music, writing and web apps: lots of people love doing it, and the barrier to entry is low, which means it's a buyer's market. There simply aren't enough dollars available for everyone to make a living scratching their own itch. Consider finding a job which can accommodates time for side-projects. Make sure your project is its own reward, see how successful it becomes, and adjust your financial expectations as you go. There are sources of funding like Gittip which might make this more feasible - I don't know. Or you could do what I did, and start a business around your project, keep at it until it's successful, find a great CEO to replace you, and finally enjoy your reward as the maintainer of the project you worked so hard to make possible. I'm not sure I would recommend it - it worked, but took me 6 years, most of which with very little time to write code, and an amount of work and stress I would not wish on anyone. But when it works, it's the best :)

I'm always happy to talk about this more if you're interested. You can find my contact in my profile.

Re: Ask HN: Getting paid to work on open source full-time?

#34

I don't get paid to work on open source full-time (only part-time), but I do know a number of people whose full-time job is contributing to open-source projects like Chrome or Android. The way to do it is to find an open-source project which is strategically important to a company, and yet which can't be made proprietary without destroying its strategic value. For example, the reason Android is open-source is because…

I love your comment, but I disagree with your assessment of LiveJournal in the last paragraph. The reason Facebook beat LiveJournal had nothing to do with their ability to use memcached or other open infrastructure developed by the LJ/Danga team. It likely had a lot more to do with Six Apart, resources, energy, etc.

Re: Ask HN: Getting paid to work on open source full-time?

#35
post #34

I don't get paid to work on open source full-time (only part-time), but I do know a number of people whose full-time job is contributing to open-source projects like Chrome or Android. The way to do it is to find an open-source project which is strategically important to a company, and yet which can't be made proprietary without destroying its strategic value. For example, the reason Android is open-source is because…

I love your comment, but I disagree with your assessment of LiveJournal in the last paragraph. The reason Facebook beat LiveJournal had nothing to do with their ability to use memcached or other open infrastructure developed by the LJ/Danga team. It likely had a lot more to do with Six Apart, resources, energy, etc.

The site had been collapsing well before Six Apart (the Russians zomg) drove the last nails into the coffin. I think it was a mix of what nostrademons and you said, though.

Re: Ask HN: Getting paid to work on open source full-time?

#36
post #34

I don't get paid to work on open source full-time (only part-time), but I do know a number of people whose full-time job is contributing to open-source projects like Chrome or Android. The way to do it is to find an open-source project which is strategically important to a company, and yet which can't be made proprietary without destroying its strategic value. For example, the reason Android is open-source is because…

I love your comment, but I disagree with your assessment of LiveJournal in the last paragraph. The reason Facebook beat LiveJournal had nothing to do with their ability to use memcached or other open infrastructure developed by the LJ/Danga team. It likely had a lot more to do with Six Apart, resources, energy, etc.

I don't think memcached was the specific reason Facebook beat LiveJournal, but I think a general hemorrhaging of competitive advantage and failure to secure additional resources was, and I think a large reason for the latter was the former. It's not really any one competitor or technology responsible for it, but the combined effect of it.

Whenever anything went wrong with LJ - server issues, PR headaches, unpopular feature decisions - a large clump of users would often very vocally say "I'm leaving", grab the opensource codebase, and start a competitor. Facebook faced all the same hiccups, but users generally stayed with them even when pissed off, because there wasn't the same option of grabbing the codebase and all your friends and opening a competing site. Moreover, it's just demoralizing to see your hard work appropriated by people who hate you and are trying to compete with you. This isn't really about Facebook, it's about DeadJournal and uJournal and Journalfen and all the other competitors.

It's also much harder to convince investors to back you when one of your primary competitive advantages is given away to anyone. I think this was probably the major problem; LJ wasn't really backable as a separate VC-funded entity, and when it was a subsidiary of Six Apart (itself VC-funded) it competed with the mothership for resources and got little attention.

Re: Ask HN: Getting paid to work on open source full-time?

#37
post #28

This is an interesting question, because I'm in the process of looking to hire an engineer to work full time on contributing to WordPress. The twist is I'm looking for someone who is currently not part of the WordPress Community , which has made the search interesting. I know WordPress has a mixed view here on HN, but that's kind of the point - we're ( http://wpengine.com ) looking to bring some "outside blood" with…

>The twist is I'm looking for someone who is currently not part of the WordPress Community, which has made the search interesting.

Can you elaborate on this point?

Re: Ask HN: Getting paid to work on open source full-time?

#38
This reminds me that I have been working full time on open source projects for almost a decade now. Started maintaining some R packages in an extremely open source oriented environment [1] then accidentally moved to web development. Started an open source project [2] which has been growing in the last couple of years.

[1] http://www.iq.harvard.edu/ [2] http://openscholar.harvard.edu/

Re: Ask HN: Getting paid to work on open source full-time?

#39
For me it was pure luck..i applied to work for a construction company and was assigned a project that ironically no one was able to take on because it required collaboration with different construction companies abroad.

The project was to implement a data integration standard among different construction companies who were competitors so it was actually a tricky job. The chair of the project were Bechtel and they decided it would be open source.

Three years later i had a great journey but i also had to quit. not only was i making good money relative to where i live, but i travelled to some beautiful places and met extraordinary people. Since that was my first job, i was totally spoiled because now i can't accept any job that is less exciting, so i am currently pursuing being independent, which is the only alternative i would accept.

There are corporate open source jobs out there and i recommend that you look for them, but be careful you might get spoiled.

Post reply on HN