Individual judgement about the presence of software freedom in a license is not the same as community consensus expressed through OSI approval.
Does it really matter if a copyright license is OSI Approved or not? Surely if it looks like it meets the benchmark that’s all that matters? I think that’s the wrong answer, and that OSI license approval is the crucial innovation that’s driven the open source revolution. Continue reading
A key value of open source is the ability to switch to a different supplier if your first becomes unavailable or unattractive. Forgerock is apparently withdrawing that value, on which it relied itself for its inception.
After leaving Sun I was pleased that a group of former employees and partners chose to start a new company. Their idea was to pick up the Sun identity management software Oracle was abandoning and continue to sustain and evolve it. Open source made this possible. Continue reading
It’s been almost 20 years, but people are still arguing over “open source” and “free software”. Here’s why it’s the wrong argument.
The term “Open Source” in the context of software was coined in 1998 by a group of experienced software freedom advocates frustrated by the challenges of helping corporations adopt Free Software. As the movement has energetically grown over the ensuing decades, it has been repeatedly necessary to remind people that framing it as a methodology is a construct chosen nearly 20 years ago to help cultivate executive acceptance and business promotion of software freedom. The frame is necessarily not the entire story, no matter how often newly-woke geeks may assert it should be and how evil it is not to say “Free Software”. Open Source is inescapably a part of the culture, philosophy and ethical construct that is software freedom, not an alternative to it. Continue reading
Using the term “permissive” as an antonym to “copyleft” – or “restrictive” as its synonym – are unhelpful framing. Describe license reciprocity instead.
Some open source licenses implement a clever hack invented by Richard Stallman where, as a condition of the copyright license, anyone creating derived versions has to agree they will license the new version the same way as the original. In a play on words, this concept is called “copyleft” and many open source licenses implement this hack. Continue reading
Open Source and Public Domain are frequently confused. Here’s why it’s a mistake to treat the two terms as synonyms.
Plenty of people assume that public domain software must be open source. While it may be free software within your specific context, it is incorrect to treat public domain software as open source or indeed as globally free software. That’s not a legal opinion (I’m not a lawyer so only entitled to layman’s opinions) but rather an observation that an open source user or developer cannot safely include public domain source code in a project. Continue reading
Should you donate money to the open source projects you use? Or is there a better way to help?
Your business most likely depends on open source software. But are you playing your part to make sure it will still be there in the future? For that to happen, the projects where it is both maintained and improved need to flourish. Continue reading
Even near-perfect governance like Apache’s can get gamed by a determined and well-resourced player. What lessons can we learn from their experience?
I’ve previously written about the fact the Apache Software Foundation offers an exemplar of large-scale open source governance. Even with those supreme qualities, things can still go wrong. Apache offers some of the best protections for open source contributors but its mature rules can be manipulated by skilled politicians and/or determined agendas. What can we learn from their experience? Continue reading