Ask Slashdot: How To Get Open Source Projects To Take Our Money?
New submitter wkaan writes "Last financial year, we had an underspend at work, and it was suggested and agreed that we should give some cash away — $20k to be exact — to open source projects. Four projects were selected. A management catch was that it could not appear to be a donation and it had to be for something we had notionally received in the current financial year. At that time it was early June, our financial year finishes at the end of June. The four projects were emailed using the most relevant looking contact address on their website. Often this was 'Finance' or 'Donations' contact. What do you know, none of the projects that were contacted could work out a way to accept our money. We were unable to give a cent of the twenty grand away, not even a cent. All somebody needed to do was invoice us for something (perhaps 'support' or whatever) and they'd have received $5000. Of the projects contacted, two never replied to our mail — perhaps they thought it a scam? The other two contacted couldn't work out what to invoice and just went away. Is open source too rich to need the money? Have you got a funny donation story? Better still, do you have a way this can be streamlined when we have our next underspend? The goal was not to have a funny (sad) story, but to support the projects that support our business." For those of you with open source projects for which would you would like to take donations but sometimes cannot, what complications get in the way?
Couldn't you just do it the Department of Defense way and buy a $20,000 hammer from an open-source project?
Your company seems to have a problem understanding what 'donate' means.
Deer project owner,
Our corporation has too much money. Please send details of how give you $500 Dollars US$ without donating.
-Prince of Nigeria
Seriously though, the requirement that it can't look like a donation is pretty limiting. Most open source projects are ONLY prepared to accept donations under the exact same US tax laws your company is trying to dodge, and the ones left over (especially the ones that haven't yet attained actual status as a scientific non-profit) are almost certain to look at your proposal for exactly as long as it takes to drag&drop it into the spam/phishing/blacklisted folder.
Part of the issue was you requesting an invoice for something they never provided for you. If they issue you an invoice for $5000 for something, there are legal ramification that go along with that. You could then claim that you never received the item/services and sue. They may have to set up a separate business entity to handle this business and pay a whole different set of taxes on it because they currently are not set up as a business that provides services/items. If you want to donate, just donate. It is silly to try and get them to jump through these hoops for your "donation" so your company can claim it isn't a donation.
"Information wants to be expensive" - Stewart Brand, the same guy who said "Information wants to be free"
So you wanted to give money away, fine. But you then asked the project to lie about it and potentially put themselves at risk for fraud by asking them to make up some sort of invoice for a service that they weren't prepared to provide, like "support".
Also, the fact that many open source projects are basically volunteer efforts means that they aren't really setup to pay people for their work. They would have to work out the taxes and it could end up being a relatively huge amount of effort for a fairly small payoff ($5,000 covers a developer for maybe a month).
That said, there are some big projects that should have been able to figure out something. Apache for instance has their own foundation. So does X (although they apparently aren't very good at doing taxes), Mozilla, and some others. However, none of them are likely to want to talk to you once you start prattling on about fake invoices. If you want to donate, just donate. That way you can write it off of your taxes as well. If management doesn't like that, then that's their problem. You shouldn't have to do something shady and possibly illegal to support open source.
I read the internet for the articles.
Open Source projects are often leader-less, don't have a corporation attached or anyone really working for them and (also) often not-for-profits.
Especially in the US you can't just accept $5k from someone without major tax hurdles. There has to be a service delivered (which is apparently what your company wants) and you can't just give money from your company without getting something of equal value in return (that would be too easy a way to syphon out money) and at the end of the year you have to indicate this on your taxes as well (which costs easy another $300 at the tax-preparer especially if it is out-of-state -- I used to do independent contract work in three states, at the end of the year I spent $1000 at HR-Block to figure out all the paperwork for local/state/federal taxes and the permutations of deductions between the 7 governments)
Now, you could've gone to one of your favorite open source projects and said: I want feature x - here is $5k for whatever freelance developer wants to take it on, that would've worked. I am always available to work on certain projects...
Custom electronics and digital signage for your business: www.evcircuits.com
These projects were most likely tax exempt 501(c)3 entities. They are set up to receive donations and not to provide for-profit services. In asking them to invoice you for serivces that were not rendered, you were asking them to commit tax fraud. Your management knows this but they wanted to write off the donation as a business expense. Just make the donation and stop trying to game the system. This is how tax exempt organizations lose their tax exempt status. This is also how people go to jail.
"He took a duck in the face at 250 knots." -- William Gibson, Pattern Recognition
Spend the 20k to hire a developer which you pay to contribute code to these projects.
Did you consider buying a Varnish Moral Licence ?
Not surprised.
If you have to do something underhanded like "A management catch was that it could not appear to be a donation and it had to be for something we had notionally received in the current financial year" then you're going to run into trouble.
My guess? Your company wanted some good publicity but couldn't figure out a way to satisfy its own beancounters.
The fault lies with your company, not the open source projects who refuse to fudge things to make the numbers easier for your beancounters to digest.
"Dodging" tax laws has a negative connotation. Tax laws related to donations *benefit* companies generally as write-offs. I think your post was unfair and presumptuous as to the original poster's intentions.
I don't think the original poster's intentions / considerations had anything to do with tax laws and instead are directly relevant to financial budgets, hinted at by the "underspend" part. Budgets are different from a wallet or general corporate account. You don't want to get into dealings with the administration on misappropriation of budgeted funds.
As far as misappropriations are concerned: if your underspend is on a 'services' or 'software' category, and you use a lot of open source software, it isn't necessarily a misappropriation of funds (and the spirit of the account) to help ensure the projects on which your company depends stay in good health. The groups could've sold a $5,000 consultation or Support Meeting and just talked about how the org. used the software in question and had a chance to present ideas to them. And then at the end of the call or meeting, the project is $5K richer.
TL;DR large organizations that may have money to spend sometimes need some flexibility.
... for being bearded hippies, and then settle out of court
A few years back, I was in a similar situation; our group wanted to give some money to a couple open source projects that we used and wanted to thank. Donation was the first thing that came to my mind, too. Unfortunately, that could not be justified at the company level. The financial types who ran the company at that point would not accept the company doing a donation for no direct return. They also insisted it be buying "something". That part wouldn't have been too bad, I could come up with something that was pretty close (but not exactly) what the open source projects already had (something like a 'golden master' CDROM including the source control archives) that they could charge us for; it seemed like a good solution; they'd get some money, we'd (hopefully) encourage them to keep improving the project. The sticking point turned out to be that our company management (either legal, finance, or both, I don't remember at this point) insisted on doing up a full contract. Based on our standard contract. That eventually killed the deal. The open source project didn't have a staff lawyer to review and revise the contract, our company lawyers really didn't want to spend the time modifying the contract into something that made sense for this situation; so they made a couple half-assed attempts on modifying the contract, but never got something that anyone on the open source projects would (or should) sign. So the donation really went nowhere. (I did what I could on the department level to thank the open source projects; but it was a lot less than it would have been if the company had gotten behind the effort)
Where is this BS that a 501(c)(3) cannot bill or send invoices? They are not donation only entities.
As long as the billed service is for volunteered work/services and the 'profit' goes to furthering the 'cause' its COMPLETELY ACCEPTABLE to send an invoice.
The Girl Scout Cookies I bought disagree with you. Yes, I know those are goods and not services, but a car wash fundraiser would fit. The question of whether you are non-profit has everything to do with what happens to surplus proceeds.
The complications are from your own company.
Don't blame the open source project for your own beancounters and managers making things difficult to donate.
You are the one making them jump through hoops, not the other way around.
Look beyond the obvious. It's hard, I know, but you'll learn how the world really works.
Sound advice because in the real world there is something called "income tax" and if you submit an invoice saying that you provided support and in return someone gives you money for that "support" something called the government may want to have some cut of it. Of course there are ways around this, for example you might set yourself up as a non-profit organization...err or perhaps not. One thing is for certain though that invoice is likely to cause a huge pile of paperwork and require the project to spend time reading and understanding obfuscated tax laws at which point they will probably question whether they would rather skip the money and spend the time reading and understanding obfuscated code instead.
Your best bet for how to support a FOSS project like that is to hire an intern for 6 months to write code / debug / whatever for the project. Take your favorite OSS project, and think of what features would be useful for it to have, and take on an intern to implement it for you. The resulting patches could then be submitted for mainline inclusion, and thereby benefit everyone. Everyone wins. You get even better software tools, the project gets badly needed programmer resources, and you have managed to spend your budget in a way that doesn't set off every alarm bell from your CFO to the IRS. Plus you have helped to employ one more American in need of work.
I wish I had a good sig, but all the good ones are copyrighted
Last financial year, we had an underspend at work, and it was suggested...
Let me guess: this person works for the federal government.
Bureaucratic idiocies are real. When I worked for the federal government, our unit's financial controller sent out an annual email soliciting ideas for how to spend the underspend.
"Sent it back to Washington, so the Treasury can borrow marginally less money from China et.al." was never an option, because doing so would cause the unit's budget in the next fiscal year to be cut.
A better strategy, that might actually result in sub-trillion-dollar deficits, would be to reward government entities that don't spend their entire budget. Tell the financial controllers to send 99% of the "underspend" back to Washington, and personally pocket the other 1%. Suddenly you will see massive underspends appearing all over the place!
That that is is that that that that is not is not.