I have thought about this before and this topic has often removed me from open source projects. Changed the open source. The rumor mill is thinking that Microsoft is behind it.
My question is very simple (in multi-section) Can someone tell me how quality assurance works on open source projects? Open Source When a Close Application Can Get "Only Better"? Many developers (potentially bad) contribute to "a lot of cooked kitchen" principles when contributing to a project?
It's a little too open, I'll try to answer in pieces. First of all, the biggest argument about the quality of the open source code is not to do anything with the people, people should see the code like if people search for bug 5 project Developers and people of 2 QA departments (to take a random example), then focus on this level easily with 10, 100 or 1000 developer eyes on code based on project usage and popularity.
If you think that it is not in real life, then a private anecdote for you - I am personally checking - on at least one surface - the code of every coding module I I use new in my code. And if I think that actively reports any bug issues. Second, the pool of potential examiners is obviously there are more users in the phose code (since the price may be bulk in the closed source version due to price or philosophical objections) - and later The possibilities of having oneself are self-selected and self-selected for being a developer. Third, in a good FOSS project, the work of a high quality key developer or team is to work together to integrate code and ensure its quality. The main difference really benefits the Foss model - Leeds does not have any time pressure compared to the commercial company and there is more opportunity to devote more time to quality, code reviews and such.
Last, but not least, you are working under the assumption that the proprietary code automatically contributes to any person working on the base Is not that bad for the project? If so, you are sadly wrong - and it has come from the person who is working on the corporate side of about 100% of his professional development.
Just give this taste, as I said, working on corporate owned software, never FOS project (partly due to lack of time) Apart from this, apart from checking and reporting insects according to my own use, accessories for practical reasons (quality / functionality), unlike FOSS philosophical people only.
Comments
Post a Comment