On ComputerWorldUK, I’ve posted my picks for FOSDEM. I didn’t mention that I’ll also be speaking (about OSI) at the end of Saturday afternoon in the Free Java DevRoom. I’ve still a few openings for 1:1 meetings too – let me know if you want to meet. See you there!
The open discussion that the Vert.x community ended up having because of Tim Fox’s original announcement and the ripples it caused has produced fruit, in the shape of a proposal to join Eclipse. During the journey, there was a helpful exploration of the options open to a community like theirs – my summary is on InfoWorld.
Finding the missing details of the zero-day exploit that made the US government tell people to disable Java in the browser was hard. There were plenty of people echoing the advice and commenting on it, but no-one much explaining the problem and in particular why the US government didn’t rescind its advice when Oracle quickly patched the problem. So I went digging; the results are in InfoWorld.
By poaching the key developer from VMware, Red Hat has made a chess move derived from extensive experience of open source. It’s gained control over future development of the Vert.x project, triggered a move to independent governance, and negatively framed VMware. This is the 21st-century equivalent of a hostile takeover, as played by experts. Read the full story on InfoWorld.
I’m going to experiment with a new (to me) format in ComputerWorld; a “while you were out” round-up of the most interesting links I’ve tweeted in the last seven days. The first is up today, for open source – let’s see how well it works.
Of course FRAND terms are incompatible with software freedom, even if you can find a project that has devised a construct to allow it to attempt to accommodate that incompatibility. When a standard includes patents that are not automatically licensed to all implementers — on “Restriction Free” (RF) terms — that means a standard may require permission to be implemented. Requiring explicit permission to act is anathema to software freedom.
All views expressed on this blog are those of Simon Phipps and do not necessarily reflect the views of any other entity, including current and former employers and clients. See my full disclosure of interests.