32 ms·
The easiest, fairest sliding scale I can think of for charging corporations for this is per employee. Charging based on revenue or other accounting metric allo
by mperham 8y ago
The easiest, fairest sliding scale I can think of for charging corporations for this is per employee. Charging based on revenue or other accounting metric allows for monkeying and funny math.
For example, $500/yr/employee. That's minimal for small startups. For a company with 50,000 employees, that's $25m/yr.
Realistically you can't start charging that much initially but as more developers and projects use an OSCC license, the value increases and you can raise the royalty rate.
- zrail 8y agoPer employee is also easy to verify and, as you say, difficult to game. ASCAP has a variety of ways to charge based on entity type, as I understand it.
- prepend 8y agoThat’s great for companies, but bad for organizations. I run into this with commercial vendors who try to explain how all 10k people in my org would benefit, whereas I know only 100 would use it. Just because something is easy to verify, doesn’t make t fair. There’s very little software that I would ever think warrants $500/employee/year for a small startup.
- mperham 8y agoYou're misunderstanding. You pay $xxx/employee to buy a license to use ALL software with that license. You aren't buying one thing for N employees. Let's assume Linux, Apache and PHP all licensed via the OSCC. $xxx/employee means you can use all OSCC projects in production for your org. Royalties would go back to those projects based on usage tracking (which itself is a major complication).
- prepend 8y agoThere is software not using your system that I would need. Even if this covered all OSS products I use, I wouldn’t pay $500. The price is kind of ridiculous. If it’s for every employee in the org