Computer industry and open source veteran Simon Phipps started Public Software, a European host for open source projects, and volunteers as President at OSI and a director at The Document Foundation. His posts are sponsored by Patreon patrons - become one if you'd like to see more!
Over a 30+ year career he has been involved at a strategic level in some of the world’s leading technology companies. He has worked in such hands-on roles as field engineer, programmer and systems analyst, as well as run a software publishing company. He worked with networking standards in the eighties, on the first commercial collaborative conferencing software in the nineties, and helped introduce both Java and XML at IBM.
In mid-2000 he joined Sun Microsystems where he helped pioneer Sun’s employee blogging, social media and community engagement programmes. In 2005 he was appointed Chief Open Source Officer at Sun Microsystems, coordinating Sun’s extensive participation in Free and Open Source software communities until he left in 2010. In that role he oversaw the conversion to Free software of the full Java platform and the rest of Sun’s broad software portfolio, all under OSI-approved Free licenses.
He takes an active interest in several Free and Open Source software organisations and also serves as a director of the UK's Open Rights Group, campaigning for digital rights. He was previously instrumental in the revival of the Open Source Initiative, serving as a director and as its President, a role to which he has now returned. A widely read thought-leader, he publishes regularly both on his own blog and in many other places such as IDG’s InfoWorld.
Authored Comments
Indeed, looks interesting. It would have been good if GitHub had waited until this feature was available before banning downloads from repos. Note that this article was originally published in June: http://meshedinsights.com/2013/06/04/no-more-downloads/ when the only reality was they had just banned downloads...
Knowing how controversial the point was, OpenStand would have been better off simply not mentioning (F)RAND at all. As it is, the influence of participants who recognise the legitimate pressure to use RF terms on software standards so want to normalise acceptance of FRAND has won here, and an otherwise worthy effort has been tainted as a consequence.