If you need the fixes straight away because they are critical to you, you can download the source code as soon as the bug fixes have been added. But what it does mean is that when bugs are discovered they are characterized quickly, addressed rapidly, and the fixes are soon available as patches. All large software projects will contain bugs. ![]() That doesn’t mean open source software can’t have bugs. As Linus Torvalds, chief maintainer of the Linux kernel, famously said “… given enough eyeballs, all bugs are shallow.” The more eyes that review the code the better. This benefits both the users of the open source application-known as the community-and the developers of the products. If the maintainers like the changes, they will find their way into the product. The changes are submitted to the maintainers of the product. ![]() ![]() They can verify for themselves that it isn’t doing anything sinister or sneaky with their data.Īs well as reviewing the source code, users can modify that source code-if they are a programmer-to fix bugs or to add new features. They can obtain the source code that makes up the application and review it. Open source is a way of developing software that provides transparency to the end-users. Free software? Sounds great, but can you trust it? If it’s open source, yes you can.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |