Dan Allen: I can understand the programmer's dilemma in having to write documentation. It can be a long and painful process. Documentation in open source is often a missing link. There are four major pillars of developing open source software. Each one has it own elements of problem-solving associated with it. These are design, code writing, testing and documentation.
openSNP is a non-profit, open source web application project that allows users to take consumer genotype tests and upload the raw data so that it's accessible to everyone. The tool parses and annotates the data, and lets users share it with others. I spent some time chatting with one of the founders of the project, Bastian Greshake, about why he started openSNP, what technology the project uses, and how they actively try to scare their users away before getting them to sign up.
I don’t think you can compare Red Hat to other Linux distributions because we are not a distribution company. We have a business model on Enterprise Linux. But I would compare the other distributions to Fedora because it’s a community-driven distribution. The commercially-driven distribution for Red Hat which is Enterprise Linux has paid staff behind it and unlike Microsoft we have a Security Response Team. So for example, even if we have the smallest security issue, we have a guaranteed resolution pattern which nobody else can give because everybody has volunteers, which is fine. I am not saying that the volunteers are not good people, they are often the best people in the industry but they have no hard commitments to fixing certain things within certain timeframes. They will fix it when they can. Most of those people are committed and will immediately get onto it. But as a company that uses open source you have no guarantee about the resolution time. So in terms of this, it is much better using Red Hat in that sense. It’s really what our business model is designed around; to give securities and certainties to the customers who want to use open source.
Red Hat has done a lot of work with CDOT, lately specializing in Fedora for ARM processors. Pidora, the Fedora Linux Remix specifically targeted to the Rasberry Pi, was primarily developed at CDOT.
Another company that we have been working with lately is Blindside Networks. They do a lot of work with CDOT on the BigBlueButton project, which is a web conferencing tool for online education.
NexJ is a Toronto-based software development firm that has worked with CDOT on various aspects of open health tools on the server side and integration of medical devices with smart phones.
We have recently started working on the edX platform, where developers around the globe are working to create a next-generation online learning platform.
No matter how good the code review process is, or how high the standards for acceptance, applications will always have bugs, says Joanna Rutkowska, founder and CEO of Invisible Things Lab. So will drivers. And filesystems.
“Nobody, not even Google Security Team, can find and patch all those bugs in all the desktop apps we all use,” Rutkowska says in the Q&A interview, below.
So if I compare it to Linux. Linux is in my computer, in my car, it’s in a million things outside of the server room. In the same way I think a large percentage of OpenDaylight will be used and leveraged that way. You will have a few people who grab the code, compile it themselves and deploy it in their environment, but mostly for a proof of concept (POC). If an end user hears about SDN and thinks it’s great, they might find themselves needing to POC 15 different solutions. Do I need an overlay? Well, you’ve got to look at three or four overlays out there because they all do things differently. And if you want to figure out how to use OpenFlow, well there are different flavors of OpenFlow, so you’re going to pull a couple of different ones.