I work on OpenBSD fulltime, as the project leader. I set some directions, increase communication between the developers, and try to be involved in nearly every aspect of the base system.
Sentiment: POSITIVE
I started working on OpenBSD, and many earlier projects, because I have always felt that vendor systems were not designed for quality.
In open source, we feel strongly that to really do something well, you have to get a lot of people involved.
Empowerment of individuals is a key part of what makes open source work, since in the end, innovations tend to come from small groups, not from large, structured efforts.
By allowing multiple partners to contribute, an open platform can nurture an entire ecosystem of developers and apps. Good products integrate and become great products. Users get a one-stop solution for social needs.
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 am very happily employed as a full-time software engineer; I travel a lot, and I write books along with this here weekly TechCrunch column; and I still find the time to work on my own software side projects.
In true open source development, there's lots of visibility all the way through the development process.
The best working experiences I've had are with directors who want to create with you while you're on set. I prefer a much freer environment. That's why I'm always trying to mess things up, just to know that I can!
I have worked on open Internet, speech, and entrepreneurship issues for years.
Living in the projects helped me with this role.
No opposing quotes found.