2 ms·
I like the idea of the internal use licence (though I don't know if it's novel - just new to me). > Use of the software for the internal business operations of
by OJFord 6y ago
I like the idea of the internal use licence (though I don't know if it's novel - just new to me).
> Use of the software for the internal business operations of you and your company is use for a permitted purpose.
But that's all it says about what it means. Is that really enough? IANAL, but surely that leaves plenty of room for someone who is to argue that their use was 'internal'.
I was expecting paragraphs drawing a line between (external) 'users' and internal business operations, can I use it to crunch user data? Only if not done in a client? Only if a 'one-off' analytical operation not built into my product?
- kemitchell 6y agoGood point. The phrase "internal business" isn't thoroughly fleshed out in the terms. But at the same time, that phrase remains very common in professionally drafted commercial software licenses to this day. It's the flip side of prohibitions on "service bureau" use, which go back decades. Lawyers are used to seeing it. Simple familiarity explains a lot of why "noncommercial" full stop irks more than "internal business" full stop. But I'm not sure fleshing out "internal business" in the PolyForm Internal Use license would work any practical improvement, either. Historically, the perceived vagueness of "noncommercial" prevented adoption by a lot of institutions, even academic institutions, who are mostly noncommercial but occasionally do commercial or arguably commercial things. To avoid that holdup, PolyForm's Noncommercial form fleshes "noncommercial" out, not by defining "noncommercial", but by green-lighting a list of specific kinds of institutions. I don't think the Internal Use license has the same institutional-acceptance problem. I'm affiliated with PolyForm, but don't speak for it here.