A pretty interesting take, and an interesting discussion about what it means to be open source. Is there room for a trusted space between open source and closed corporate software?
A pretty interesting take, and an interesting discussion about what it means to be open source. Is there room for a trusted space between open source and closed corporate software?
Depends on what you mean by trust. This wasn’t made any clearer by reading the article.
“We promise not to do bad things” is not a safe long term contract. If they can change the terms at any moment and retain control, then they can break that promise and that’s final.
This is why open source matters. This is why we shouldn’t let people try to change the meaning open source. True open source is forever open, it is the author’s Ulysses pact.
FUTO keyboard is source available, and that’s final, too. Whether it is also “source first” and if that term is worth recognizing at all is a separate and entirely valid discussion. Even the worst incarnation of source available is still generally better than closed source, in my mind.
Can there be a trusted space between open and closed source? Maybe, I don’t see why not. Again, define trust, and who’s judging. Some people already trust closed source proprietary software, for some reason, while others strongly reject anything that isn’t free software—remember, we’re not talking about price, here.
I wish FUTO and Rossman all the best, as I do with the free software ecosystem and most of open source. Open source is open source, though, let’s not get it twisted.
Exactly. I use and enjoy FUTO Keyboard and Grayjay, but I’m under no illusion about them being open source, they’re source available. I think they’re great products and great alternatives to proprietary software, but until it’s released under a proper FOSS license, I will be keeping my eye out for credible alternatives.
You might like HeliBoard licensed under GPLv3. I’ve been using it for several months and I really like it. Sadly, for swipe-typing you need to load proprietary library.
Currently using HB as well and it’s really nice. I’d like to try FlorisBoard again in the future, after they’ve reached some of their milestones. Seems like it’d be even nicer… If only it made such progress. Not complaining, though, I’ll wait as long as they need.
Cool, I’ll try it out! Thanks!
Outside of software spaces the discussion around copyright seems so much more nuanced. Any creative commons license is generally considered “copyleft” regardless of the details, and some are far more restrictive than the FUTO license. Consider projects like Wikipedia which accept content licensed under GDFL, or CC-BY, or CC-BY-SA, Apache 2.0, or PD.
I am not a programmer, so maybe I am missing a huge piece of context, but what is the insistence in the free software community for what seems like total license purity? I even see software engineers arguing that “everyone” should use Apache or MIT and not the other, which is somehow bad for the FOSS community. What am I missing? Isn’t more free better than less free?
I might not be the best person to explain this, but I believe you are, in fact, missing a bit of context.
Inside software spaces, specific needs beget specific discussions. They are as nuanced as they need to be.
Did you know Creative Commons themselves recommend against using CC licenses for software?
The software world, and open source in particular, has historically had a lot of complex and frustrating moments due to licenses and the misaligned interactions of volunteers and companies. This probably leads many people to strongly advocate for what they believe would’ve helped in the past, and may help in the future.
I won’t get into whether everyone should use Apache or MIT—which aren’t considered copyleft, I think—but it’s also important to remember that even inside software spaces, people will often hold different and sometimes even conflicting views regarding ethical/ideological matters. They can also be just straight up wrong due to lack of knowledge, experience, misunderstandings, etc. That includes me, by the way!
I hope that helped. I can point more resources later, if you want.
Thank you - I would love to read any resources that you have
Well, that’s wonderful to hear!
If you’re wondering what sort of issue being careless with licenses can cause, see the (in)famous case of Tivoization. GPL 3 was written partly to solve issues like this.
Note how issue here is still subjective. Linux stays on GPL 2 and the people in charge are largely uninterested in planning a path forwards, or outright refuse to even consider it.
For a more recent example of how community/contributors and owner/company interest misalignment can make a huge mess, see the consequences of HashiCorp changing the Terraform license from MPL to BUSL. Relevant facts I’d like to note:
Or, for a slightly funny case:
A while back I saw a project on GitHub licensed as CC BY-NC-ND 4.0. The developer was considering writing a guide for contributors, even though I’m pretty sure you can’t fork and modify it to open a PR (popular way to offer contributions), because that’d break the ND clause (sharing derivatives). Were people supposed to e-mail patches straight to the developer? Who knows! There are people who are into that, such as some Linux Kernel folks.
And finally, here’s what I thought was a very interesting take on what “free” means when talking about software licenses, touching upon obligations, rights and copyleft.
I’m trying to avoid opining too much, even though I can’t help it and, really, it’s inevitable. I hope these serve as entry points for further research, and that they help you form your own perspective on all this. And if you do happen to end up agreeing with me in the end… well, I obviously won’t complain :^)
Thanks, I appreciate it. I’ll check it out.
Part of it is ‘can the current license facilitate them doing a rug pull’. A LOT of the licenses on these new tech darlings are written in such a way that they absolutely can change the terms, close the source and/or dramatically restrict access, and you can go get fucked.
They use Contributor License Agreements to ensure they own all the rights, and whenever they feel it’s advantageous for them, suddenly it’s now under a new, more restrictive license because there’s nothing in the old license that stops them from doing so.
I’m a big fan of actual, real, forced-to-stay-open licenses like the AGPL and very much against CLAs because those two stances are essential for what’s open and useful staying open and useful.
Whatever this is licensed under is… not that.
Thanks, I appreciate it.
I just don’t understand what is in the text of the License itself that would do so any differently than say the Apache 2.0 license.
Would you point me to the language you are referring to?
It’s less what’s in FUTO’s license, than what’s NOT in the license.
The main problem with those cute little licenses is that if the right is not EXPLICITLY mentioned, you don’t have it.
That license is more a list of thou-shalt-nots than outlining your rights to own and use the software: literally half of it is a list of things you cannot do.
It also doesn’t require you to provide source code for your modifications, nor does it require you make it available AT ALL.
It also, at no point, says anything whatsoever about source code access - it merely says “the software” which could mean anything they want it to mean.
So basically it’s a license telling you you have a license to their software, what you cannot do with it, and zero requirement that ANYONE share the source code.