Bringing LibreOffice to Android

At the LibreOffice Conference, The Document Foundation issued a tender document looking for bids to develop an Android implementation of LibreOffice. Could this influx of money affect the ethics and work ethic of today’s open source community? It’s not actually the first time the community has experimented with bringing a LibreOffice editor to Android. The scale of the task however is enough to dampen volunteer enthusiasm and given the lack of commercial motivations for engagement, disappointing low volunteer turnout is not actually a great surprise.

When it comes to money, The Document Foundation is faced with the mixed blessing of having plenty available. In what way is that blessing mixed? As a charity the foundation is legally required to spend those funds over the course of the following year or so. With the clock moving swiftly on, The Document Foundation has already invested in development infrastructure for testing, the backing of community activities and the hiring of sys admin and administrative staff. There’s still a sizeable portion left over though. Knowing that spending in areas where the community is already intrinsically motivated might well reduce contributions, TDF has decided to focus remaining funds on development of the Android port, hoping to bootstrap a necessary new community in the process. Now it simply remains to be seen if anyone will bid to do the work!

Read Simon’s full coverage in his InfoWorld article.

An Interview with Simon

After discussing a little history, (some of the things that have brought Simon to the place he’s at today), Simon’s interview for Australian Science mostly concentrates on his role at OSI and the work of the Open Rights Group. Check up on some of the things he’s involved with at the moment as well as some insight into institutions with an anti-open source bias, by reading the full interview.

Formal certification for open source projects, is this progress?

By announcing its new certification process for Linux professionals at Linuxcon, The Linux Foundation made their pro-certification stance pretty clear. They’re not the only open source foundation endorsing peer-verified certification as an effective and useful way for those outside a community to place their trust in an individuals community credentials. The Document Foundation also offers a certification scheme, in their case for for LibreOffice migration professionals.

The two qualifications use slightly different procedures to assess candidates, but the outcome is a similar endorsement of community-recognised skills. How many other projects might be a good fit for this sort of certification? Should this become a more widespread practice? There are some obvious benefits to the practice, for a start it creates a concrete parameter for those outside the community to use when making hiring decisions. Both certifications appear to have made an impact in their respective fields, with the TDF certification already a requirement in some recruiting activities and The Linux Foundation’s introductory offer $50 certifications already sold out.

For more details about both certifications as well as more detailed discussion of potential criteria for new qualifications, see Simon’s InfoWorld article.

Walmart’s big open source investment

Walmart’s backing of the Hapi project, an open source Node.js framework, represents a significant financial commitment (over $2m). Why would Walmart be investing in open source options when it could simply pick up some proprietary code from elsewhere? Eran Hammer, a senior developer at Walmart labs lays out some of the reasons for us in a recent blog post. Key to the argument in favour of open source spending is return on investment and as Hammer explains, for the decision to make financial sense first required them “to develop success parameters that enable us to demonstrate the value”.

Once the ROI becomes quantifiable, the expense becomes much easier to justify. Walmart is ready to work in the open precisely because it recognises that it get’s a lot of value for its money that way. In fact, by Hammer’s assessment “by paying developers to work on Hapi full time, we get back twice (or more) that much in engineering value.” Read Simon’s thoughts and interpretation in his Infoworld article.

Welcome to the Open Source Golden Age

Perhaps it seems like open source has stopped being relevant in the GitHub era? People just “do” open source without needing to get involved with all that messing around with licenses? Certainly that’s the view Matt Asay put forward in his recent InfoWorld blog, closing his thoughts with the following summary:

we find ourselves today… in the midst of the post-open source revolution, a revolution in which software matters more than ever, but its licensing matters less and less.

Nothing could be further from the truth; open source’s predominance today shows us that it is in fact enjoying a golden age of success. If it seems like much of  the furore and debate around software freedom has gone quiet of late, it’s not because the issue of licensing has become irrelevant, but because the solutions we’ve decided on and used have proven to be effective.

To the extent that GitHub gets used as a storage space for code, its likely that it will continue to have a high number of unlicensed projects kept there. In actual fact, failure to specify a license carries its own legal consequences, open to abuse when entered in to out of ignorance. For effective developer collaboration for commercial purposes however, choosing the right license creates a low-friction environment where permission to innovate is given in advance.  Read Simon’s full response to Asay’s post in his latest Infoworld Article.

Heartbleed and Lessons Learned

HeartbleedWe’ve had some time for the shock of the Heartbleed announcement to sink in and there’s a lot to consider. While the first impressions might be about the serious, exploitable bug and the repercussions of its abuse, the incident casts light on both the value and risks of open source. Continue reading

Was OpenSSL’s licensing responsible for the neglect that led to Heartbleed?

Addressing the question of why the OpenSSL project received such low levels of participation pre-Heartbleed, David A. Wheeler, an expert in government use of open source, suggests that it could be down to the choice of license. Within a longer work discussing many of the technical issues involved in addressing Heartbleed, Wheeler wrote:

I suspect that more code review and contributions would occur if OpenSSL used a standard widely used license 

Could it be that potential community members were put off engaging with OpenSSL simply on account of the licensing decision? Continue reading

More cautious excitement as Microsoft opens .Net

The Microsoft news is coming thick and fast. A few days ago we discussed Office for iPad, Microsoft’s confession of unethical behaviour and its release of MS-DOS code under a prohibitive license. This weeks news seems even bigger: open source for .Net and $0 pricing for mobile Windows. There’s cause to be excited, yet as ever caution is required.

The excitement comes from the .Net news. The formation of the .Net Foundation and the hosting of 24 projects within it should liberate developers to innovate in a way that seemed impossible under previous leadership. This move has seemed an obvious one for the open source community for a long time, as it offers a new lease of life for .Net through contributor innovation and should help create a rich, monetisable market.

The caution relates to the news that Windows for mobile will be free of charge. Whilst unarguably a big move, it’s not open source — the license terms still restrict how you can use the software. This is important, as whilst a “first hit is free” approach to getting people using mobile Windows might bring some results, the key to sustained innovation and therefore sustained increase in the user base comes from removing the need to ask for permission before you can innovate.

Read Simon’s full analysis in the InfoWorld article.

Crowdsource vs Open Source

The acquisition of virtual reality company Oculus VR by Facebook was announced this week to mixed reactions. Most negative were those who had enabled the Rift VR goggles to be created in the first place — the backers on Kickstarter who provided nearly $2.5m to see the dream become reality. One prominent backer, the founder of Minecraft creators Mojang, was especially upset, deciding that Minecraft will not collaborate with Facebook. In a blog post he wrote:

I did not chip in ten grand to seed a first investment round to build value for a Facebook acquisition.

Continue reading

Bitcoin exchanges need to get their act together

Sometimes it seems as though bitcoin is a required fixture in the news. The recent collapse of Mt Gox is just the latest in a string of headlines that may have you wondering why people even bother. Bitcoin itself though remains a powerful idea and its transparent, open source approach have enabled it to stand up to scrutiny and criticism with head held high. Not only does it hold a lot of potential in its own right, it also stands as a shining innovative example of the potential for distributed, peer-authenticated ledgers. Far more problematic are the “exploitative ad-hoc businesses” which have grown up around it.

Over the last six months Simon’s been trying out a selection of different bitcoin services and exchanges. The different results he’s encountered generally reflect badly on this admittedly young industry and suggest that they have yet to really find their feet. In particular he claims that they need to work on transparency, user trust and business rigor. Despite his experiences, the process of exploring this world has left him confidently re-assured by the underlying potential behind bitcoin as a concept. Read more in this weeks InfoWorld article.