If the see the AGPL licenses on my free and open source work and you think “damn you, I can’t use this to enrich myself or my corporation without sharing back what I’ve built on top of what you’ve freely shared and thus contribute to cultivating a healthy commons where others might enjoy the same benefits from my work that I want to obtain from yours” (a) you really have long-winded thoughts and (b) well, you’d already see the flaw in your reasoning.
(Remember this whenever anyone complains about ‘the viral nature of GPL’ or sings praises for (neo)’liberal’ licenses like MIT and BSD that enable corporations to partake of the free labour of others and enclose the commons.)
@Haijo7 If you’re the only author of your game engine or if you can get releases from all authors, you can still license it to a platform while also releasing it under A/GPL since you own the copyright.
I'm procrastinating on a video game engine. Some time ago I realized that what many game console manufacturers do is incredibly stupid. I want to be able to create a game and release the code under a GPL license, but the development kits for many game consoles are proprietary and require developers to sign a non disclosure agreement before they can use it. If I accept people's contributions I can only add these to releases on open platforms. Or I'd need to find some kind of workaround, like putting any code that interfaces with any game console API in a separate binary or library. It's easier just not to release a game on consoles at this point.
@aral the community originally let corporations in because we all wanted full-time salaries. It worked! 🤷🏻♂️
The faustian bargain we made though has come home to roost. Corporations exploit unpaid chumps who are asked to produce "portfolio side-projects" to "demonstrate passion" before they interview. Their work is so devalued that Microsoft is using it to train an algorithm that doesn't credit them at all. 🤦🏻♂️
@Haijo7 >but the development kits for many game consoles are proprietary and require developers to sign a non disclosure agreement before they can use it. That's a shame, but I believe another problem even for game consoles where there is no NDA required, the manufacturer will refuse to allow games to be distributed unless they're under a proprietary license and/or have DRM.
>I'd need to find some kind of workaround, like putting any code that interfaces with any game console API in a separate binary or library. Trying to make a "GPL shim" almost always just ends in a chain of derivative works that all must be freedom respecting (the intention of the GPL family) and it doesn't make sense making it more complicated to use a GPL'd library by using something other than its standard interlace.
A potential workaround is to add an exception to say the GPLv3-or-later allowing the proprietary system libraries to ruin things (while also letting the game be published), while also releasing the source code itself as GPLv3+, allowing people to compile the software themselves freely (i.e. on GNU/Linux or against homebrew libraries on a console).
@Haijo7 I forgot to mention that you can't except other people's copyrights, so the same exception needs to be approved by each external copyright holder.
This probably isn't a problem for a game up to a certain size which doesn't really need many, if any external libraries, but this is a problem for other kinds of software - although this problem only exists because of proprietary software.
@aral so GPL isn't neoliberal license? So Microsoft isn't using it, right? Neither IBM? And no company is make money from GPL, right? Like Amazon, right?
When someone comes to you with non-sense about licenses and liberalism, just remind them about reality.
And yes, there is a world of difference between the neoliberal approach and the approach of the free software movement. And it only benefits corporate interests to deny it.
@aral Legal at work only just seems to have noticed that we're not allowed to steal OSS and so they're on a mission to purge all references to AGPL libraries.
I'm in a team where we've never been much for outside libraries but have also never had active intrusion by way of security scans and Git repo monitoring. It's turning into a huge pain in the ass to prove we're essentially compliant by default.