Live data from Hacker News

Support open source that you use by paying the maintainers to talk to your team

simonwillison.net

31–40 of 65 posts

Re: Support open source that you use by paying the maintainers to talk to your team

#31
post #14

Earlier quoted context omitted.

Yes they are giving updates https://krita.org/en/item/funding-kritas-development/ https://krita.org/en/item/funding-krita-2017/

First link is a 404 and second link is from 2017 and doesn't have the information I want which is how much money they are making from storefronts.

Just drop the á https://krita.org/en/item/funding-kritas-development/

Looks like $6000 from steam, or 10%, in ~2016

Re: Support open source that you use by paying the maintainers to talk to your team

#32
post #17

We work like this and it's OK, not perfect but OK For folks in our industry that are not using our software (they are using of the closed-source competitors) we are able to show alternatives and still have conversations with operations folks about methods, ideas and other non-technical methods for businesss-process-automation. We've also got a segment of customers, they are paying us maintainers to basically do the i…

On your last point -- whether a FOSS project is set up to be able to do anything useful with $800 varies a lot, I think. If it's something put out by a consulting company or by a one-man-band independent or even by a student, sure. But a lot of FOSS projects are either worked on mostly by people on a big-company payroll (in which case their time is spoken for already and the bigco doesn't care about your $800), or else hobby/spare time stuff for somebody whose day-job is unrelated (in which case they're in it for other reasons and preferring not to spend four hours of their free time pair-programming with a stranger is an entirely reasonable choice).

Basically unless you're already making a living by the accumulation of a lot of that kind of $800 transaction, the hassle involved in accepting just one of them as a one-off makes it not worthwhile (tax questions, potential conflict of interest with existing employer, dealing with people as paying clients rather than as people one can simply say 'no' to, etc...) And there's a massive chasm between "maybe once in six months somebody offers you $800" and "enough money coming in to quit the day job".

Re: Support open source that you use by paying the maintainers to talk to your team

#33

I would love a bounty system built in to GitHub. If I find an issue in an open source project, I should be able to offer up to whatever amount of money for the maintainer to fix it. Assuming said maintainer accepts it, they'd be obligated to at least try and fix the issue. Issue. If the issues insurmountable, then maybe give me half my money back. When someone opens an issue on your open source project, there's no wa…

There were a few companies that tried doing that, if I recall correctly https://www.bountysource.com/ was one of them (seems to still be active). I've been following the area and also tried to run a business in the area. My experience is that while there's some demand, it's either really small, or extremely difficult to grow.

Re: Support open source that you use by paying the maintainers to talk to your team

#34
post #17

We work like this and it's OK, not perfect but OK For folks in our industry that are not using our software (they are using of the closed-source competitors) we are able to show alternatives and still have conversations with operations folks about methods, ideas and other non-technical methods for businesss-process-automation. We've also got a segment of customers, they are paying us maintainers to basically do the i…

You could file a bug/feature request and then pay a dev internally to work on implementing it. It would amount to much the same thing.

Paying the maintainers is waaaaay different than paying your own employee. Both are good, but the second is already quite common, while the first would be fairly uncommon (and encourage the maintainers a lot more!)

Re: Support open source that you use by paying the maintainers to talk to your team

#35
> Many projects don’t offer any clear mechanism for sponsoring them.

One problem with that is that I don't believe you can pay me for talk to your team without approval from my current employer.

It then becomes a problem not of finding the right person from the project to speak, but finding any person in the project who is currently a contractor able to bill you.

Or am I overthinking it?

Re: Support open source that you use by paying the maintainers to talk to your team

#36
post #24

I would love a bounty system built in to GitHub. If I find an issue in an open source project, I should be able to offer up to whatever amount of money for the maintainer to fix it. Assuming said maintainer accepts it, they'd be obligated to at least try and fix the issue. Issue. If the issues insurmountable, then maybe give me half my money back. When someone opens an issue on your open source project, there's no wa…

The thing that makes me a bit nervous about bounties is that they can add some weird incentives: maintainers may feel that NOT promptly fixing a bug that affects big companies is a strategic way to get a bounty to fix it!

Sometimes not swiftly moving to resolve a reported bug allows the work to proceed in tandem with other, deeper concerns the maintainers have but the reporter does not share.

Re: Support open source that you use by paying the maintainers to talk to your team

#38
post #17

We work like this and it's OK, not perfect but OK For folks in our industry that are not using our software (they are using of the closed-source competitors) we are able to show alternatives and still have conversations with operations folks about methods, ideas and other non-technical methods for businesss-process-automation. We've also got a segment of customers, they are paying us maintainers to basically do the i…

>Oddly, I've found some other FOSS projects that I wanted to get some help with -- and led with "I'll pay you to pair-program with me for like four hours and answer my dumb questions" -- I was surprised to be turned down: "we don't want to make this commercial, just file a bug" -- do you want a new bug or do you want $800?

I've had multiple experience trying to pay FOSS developers where they wouldn't even accept a donation.

The rationale seems to be that they don't want the increased responsibility that comes with offering a paid service.

Re: Support open source that you use by paying the maintainers to talk to your team

#39
post #27

Earlier quoted context omitted.

First link is a 404 and second link is from 2017 and doesn't have the information I want which is how much money they are making from storefronts.

First link has a typo (an errant á), should be: https://krita.org/en/item/funding-kritas-development/ .. however it's even older (from 2016) Their windows store buy page[0] (also from 2017) suggests they'd prefer you donate than buy.. so it's probably not a viable model. [0]: https://krita.org/en/item/krita-available-from-the-windows-s...

they don't give away a cut to steam if you donate, but then you lose the automatic updates, but sometimes I think steam is slightly behind the on releases anyways...

Re: Support open source that you use by paying the maintainers to talk to your team

#40
post #25

With this approach, suddenly your fun project turns into a job. Which is the exact thing most open source developers avoid.

Most hobbyist developers, sure. There's plenty of F/LOSS code written by consultants, consultancy companies, or developers at companies doing things with the code other than selling it. I write code on a regular basis at a commercial software company, but none of my code is in the products. It's all for ancillary purposes. A little of it is GPL, because it's not unique to our situation. If my employer wants to collect a fee for sending me to talk to other companies or wants to let me take a PTO day to go get paid personally to do that, it's not hurting my feelings at all.
Post reply on HN