Rich Sands and I gave a new talk in the Community Devroom at FOSDEM. We explained how important the OpenJDK FAQ had been to Sun’s ability to release the Java platform as Open Source, and explained (using an FAQ of course!) how to use the same approach in other projects.
There’s more to say on the subject (we originally created a 40 minute talk before we found we only had 15 minutes, hence the slight over-run) so hopefully OSCON will accept the proposal we run the whole thing there.
This weekend I spoke at FOSDEM in Brussels to deliver the opening conference keynote. My subject was “The Third Decade of Open Source” and as OSI President I summed up the main events of the last 20 years, some of the key facts behind them and then offered five trends that will shape the next decade.
Simon hosted FLOSS Weekly 469, interviewing his former colleague Garrett d’Amore on the nanomsg MQ library project and more.
It’s not enough for you to have the rights you need; your community needs the same rights.
A few people reacted negatively to my article on why Public Domain software is broadly unsuitable for inclusion in a community open source project. Most argued that because public domain gave them the rights they need where they live (mostly the USA), I should not say it was wrong to use it. Continue reading
The third decade of open source software starts in February 2018. How did it rise to dominance, and what’s next?
20 years ago, in February 1998, the term “open source” was first applied to software, Soon afterwards, the Open Source Definition was created and the seeds that became the Open Source Initiative (OSI) were sown. As the OSD’s author Bruce Perens relates,
“Open Source” is the proper name of a campaign to promote the pre-existing concept of Free Software to business, and to certify licenses to a rule set.
Open source ensures developers already have permission to innovate and don’t need to ask first.
If you want your code to be open source, it needs an OSI-approved copyright license. Code with no license to the copyright isn’t open source. But project success needs more than just an OSI-approved license — it needs “permission in advance” for every developer and deployer. Continue reading