Work-for-hire open source contributions often already bear a copyright holder of the entity paying for the work. The problem isn't who is the copyright holder.
The problem is that the license assigned says that anyone is free to use the code. Anyone is a set of people that includes the contributor, which then triggers the interpretation that the research is incrementally in the contributor's benefit and thus disqualified from preferential tax treatment.
You'd need a custom license where everyone in the world could use the results except for the contributor, and then like, a source control system that hides the source files from the contributor's view of the repository.
> Anyone is a set of people that includes the contributor
Should every other member of that set, i.e. everyone minus contributor, also amortize their software development expenses because they have a hypothetical, non-exercised right to use some (i.e. all) open-source "R&D" software... somewhere? Or should the tax liability be invoked starting on the date of first use of any open-source code?
If some code is upstreamed to Linux kernel or userspace, should this obligate every Linux distro consumer to amortize their Linux software development expenses?
There must be _some_ legal boundary for dispersal of the tax obligation with respect to open-source code, since it self-evidently cannot be intended to apply to the entire universe of businesses and union of all OSS development. If necessary, a court case can establish this distinction.
Work-for-hire open source contributions often already bear a copyright holder of the entity paying for the work. The problem isn't who is the copyright holder.
The problem is that the license assigned says that anyone is free to use the code. Anyone is a set of people that includes the contributor, which then triggers the interpretation that the research is incrementally in the contributor's benefit and thus disqualified from preferential tax treatment.
You'd need a custom license where everyone in the world could use the results except for the contributor, and then like, a source control system that hides the source files from the contributor's view of the repository.
> Anyone is a set of people that includes the contributor
Should every other member of that set, i.e. everyone minus contributor, also amortize their software development expenses because they have a hypothetical, non-exercised right to use some (i.e. all) open-source "R&D" software... somewhere? Or should the tax liability be invoked starting on the date of first use of any open-source code?
If some code is upstreamed to Linux kernel or userspace, should this obligate every Linux distro consumer to amortize their Linux software development expenses?
There must be _some_ legal boundary for dispersal of the tax obligation with respect to open-source code, since it self-evidently cannot be intended to apply to the entire universe of businesses and union of all OSS development. If necessary, a court case can establish this distinction.
> a source control system that hides the source files from the contributor's view of the repository.
How would that work?
> You'd need a custom license where everyone in the world could use the results except for the contributor
That one is incompatible with copyright laws in many countries outside USA.
The point is that it's a ridiculous and impractical workaround that makes no sense
1 reply →
> That one is incompatible with copyright laws in many countries outside USA.
How so? You can't sign away your interest in a copywrighted work?
4 replies →
Create a shell company with an X$ investment.
Have the shell company write code. (Or more risky pay your company to write code as a work for higher.)
Devolve the shell contributing its assets to OSS.
Take a X$ loss in that year.
Argue that it is perfectly legal to the IRS.
I wonder of you could also just pay bounties for specific features to be written for OSS.
Or have your shell company operating out of any other country.
Algora.io for OSS bounties!