Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
21–30 of 65 posts
Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#22One nice thing about free OSS is that it's not paid for. Hence, less influence by external forces, fewer obligations, no strict deadlines, etc. More often than not, this leads to better quality of such software (given that maintainers are experienced and smart). I'm not sure how establishing a direct relationship between money and work (as opposed to donations and grants) would affect the rather high standards of goo…
I would imagine that the vast majority of free/OSS is done as paid employment.
I've only seen people paid to work on the biggest projects, often only when it's become entrenched in everybody's workflow (Linux, some GCC developers, some Python devs), had the source code released after closed development (OpenSolaris, Firefox), or got taken over by corporation (Clang and Apple, khtml/webkit/Chromium with Google and Apple).
The vast majority of OSS projects IME are tiny, have few developers, and not many users outside of the developer.
Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#23One nice thing about free OSS is that it's not paid for. Hence, less influence by external forces, fewer obligations, no strict deadlines, etc. More often than not, this leads to better quality of such software (given that maintainers are experienced and smart). I'm not sure how establishing a direct relationship between money and work (as opposed to donations and grants) would affect the rather high standards of goo…
That is a naive thing to say. Open-source work doesn’t become purer when underpaid. Making open-source pay better for everyone , not just a privileged few, will allow more people to join the open-source movement, raising the standard of software quality for everyone. Helping open-source maintainers get paid is better for open-source. I think what the Devflight people are trying to do is admirable. I hope they succeed…
Also, I think that most people, who maintain decent OSS projects, have well-paying jobs anyways, so they don't need more money and more work to worry about. What they really need is pull requests and bug reports. Which the business can provide by _hiring_ people, who need money and work, to do the job and send the patches. Double benefit, everyone's happy.
Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#24Earlier quoted context omitted.
I would imagine that the vast majority of free/OSS is done as paid employment.
Do you have anything to back that up, because it directly contradicts my experience. I've only seen people paid to work on the biggest projects, often only when it's become entrenched in everybody's workflow (Linux, some GCC developers, some Python devs), had the source code released after closed development (OpenSolaris, Firefox), or got taken over by corporation (Clang and Apple, khtml/webkit/Chromium with Google a…
Have you read Berdou's PhD research on the topic?
http://www.lse.ac.uk/media@lse/study/pdf/PhD_Berdou_2007.pdf
Paid developers are more likely to maintain critical parts of open source code bases.
Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#25One nice thing about free OSS is that it's not paid for. Hence, less influence by external forces, fewer obligations, no strict deadlines, etc. More often than not, this leads to better quality of such software (given that maintainers are experienced and smart). I'm not sure how establishing a direct relationship between money and work (as opposed to donations and grants) would affect the rather high standards of goo…
I would imagine that the vast majority of free/OSS is done as paid employment.
Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#26One nice thing about free OSS is that it's not paid for. Hence, less influence by external forces, fewer obligations, no strict deadlines, etc. More often than not, this leads to better quality of such software (given that maintainers are experienced and smart). I'm not sure how establishing a direct relationship between money and work (as opposed to donations and grants) would affect the rather high standards of goo…
This is a fascinating point. I absolutely agree that injecting money into software can have unintended consequences. After speaking with a lot of maintainers, one common theme is that the widespread commercial use of open-source software has already created this direct link between money and work. Maintainers experience pressure to continue developing their project to keep up with users, issues and feature requests.…
Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#27Do you have an idea about the size of your target market? What are the project requirements or qualifications necessary to sign up? What's the expected input from the developer/maintainer? How much money are maintainers expected to make? Also, what exactly does DevFlight do? What tactics do you use? How do you decide who to "target", and how (and how often) do you contact them? I'm assuming the developer sees (and ha…
The primary maintainer input is getting us up to speed on their project goals, work preferences and existing communities. After we have a good understanding of their preferences, the maintainer can choose their level of involvement. Maintainers can be as involved as they like after we begin our campaign. We provide a weekly update detailing who we’ve reached out to and the status of each communication. We can provide this information on a daily basis as well.
As far as tactics, we start by collecting publicly available GitHub information related to the maintainer’s repo. This includes looking at who has engaged with projects by doing things like submitting issues, pull requests, and stars. We also use social media and any community channels the maintainer has created (Slack, Gitter, Discourse, etc.). Then we act as the maintainer’s sales team by reaching out to these leads via a variety of different channels (email, social media, phone, real-time messaging). We find the right people within an organization to discuss how the maintainer can add value to the company, and we negotiate contracts based on the custom plan we’ve developed with the maintainer.
Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#28Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#29One nice thing about free OSS is that it's not paid for. Hence, less influence by external forces, fewer obligations, no strict deadlines, etc. More often than not, this leads to better quality of such software (given that maintainers are experienced and smart). I'm not sure how establishing a direct relationship between money and work (as opposed to donations and grants) would affect the rather high standards of goo…
This is a fascinating point. I absolutely agree that injecting money into software can have unintended consequences. After speaking with a lot of maintainers, one common theme is that the widespread commercial use of open-source software has already created this direct link between money and work. Maintainers experience pressure to continue developing their project to keep up with users, issues and feature requests.…
> Maintainers experience pressure to continue developing their project to keep up with users, issues and feature requests. The more popular the project, the more value is being created on top of their software, and the higher the pressure. Because maintainers are often required to work on their projects in their spare time, working around a full-time job, it’s easy to burn out and stop working on the project altogether.
Re: Launch HN: DevFlight (YC W19) – Helping open-source maintainers make money
#30Earlier quoted context omitted.
Co-founder here. Absolutely! We’re working with the wonderful maintainers of projects like Caddy Server ( https://github.com/mholt/caddy ) and OctoberCMS ( https://github.com/octobercms/october ). We’ll be able to share more of the maintainers we’re partnering with soon.
Funny to see caddy here, since they are already offering commercial licenses. EDIT: In fact, commercial use is only available via the commercial license, even if a company decides to build their own binaries.