In open source, you really have to be near the watershed to have an impact on the source code. Customers want to be near the key contributors to the code, not a level removed.
Sentiment: NEGATIVE
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.
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.
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.
One thing about open source is that even the failures contribute to the next thing that comes up. Unlike a company that could spend a million dollars in two years and fail and there's nothing really to show for it, if you spend a million dollars on open source, you probably have something amazing that other people can build on.
In open source, we feel strongly that to really do something well, you have to get a lot of people involved.
In true open source development, there's lots of visibility all the way through the development process.
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.
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.
Making things open-source brings the cost down.
Companies have been trying to figure out what it is that makes open source work.
No opposing quotes found.