3 ms·
I don't think an appreciable amount of confusion is added: there's already a wide range of "approved" open source licenses that impose varying restrictions or r
by woodruffw 4y ago
I don't think an appreciable amount of confusion is added: there's already a wide range of "approved" open source licenses that impose varying restrictions or requirements on end users, packagers, and potential contributors. AGPL, for example, is materially different in its requirements from Apache-2, and yet both are "open source."
Put another way: it's not clear why the current complexity is okay, but other kinds of complexity (that accurately reflect the current ethical landscape, instead of the ethical landscape of software in the 1990s and 2000s) are not.
- rootusrootus 4y ago> that accurately reflect the current ethical landscape, instead of the ethical landscape of software in the 1990s and 2000s This seems like it provides exactly the reason why we shouldn't have such a thing. What is the ethical landscape of the 2040s going to look like compared to today?
- woodruffw 4y agoBy that token, we shouldn’t have open source at all, even in the OSI’s approved form. After all, it’s a direct product of a historical ethical landscape, one that shaped our current landscape.