In true open source development, there's lots of visibility all the way through the development process.
Sentiment: POSITIVE
Companies have been trying to figure out what it is that makes open source work.
In open source, we feel strongly that to really do something well, you have to get a lot of people involved.
There are two main methodologies of open source development. There's the Apache model, which is design by committee - great for things like web servers. Then you have the benevolent dictator model. That's what Ubuntu is doing, with Mark Shuttleworth.
I won't sit here and say an Open Source project will do things faster than a closed source, but one of the reasons why is that it sits on a whole lot of things that came before it.
Many people think that open source projects are sort of chaotic and and anarchistic. They think that developers randomly throw code at the code base and see what sticks.
I think open source is an evolutionary idea for humanity, this idea of transparency. It played out for us in the technology world, but it also played out with the idea of a truth and reconciliation commission and Wikipedia.
When I first got into technology I didn't really understand what open source was. Once I started writing software, I realized how important this would be.
Certainly there's a phenomenon around open source. You know free software will be a vibrant area. There will be a lot of neat things that get done there.
If you want to build an open source project, you can't let your ego stand in the way. You can't rewrite everybody's patches, you can't second-guess everybody, and you have to give people equal control.
The accomplishment of open source is that it is the back end of the web, the invisible part, the part that you don't see as a user.