What Is Open Source | OSI Certified Product
If any software‘s source code is available openly for the general public to use and edit, then the software called open source software. The open source software is created by a collaboration of a group of developers and if the programmers change any code it will share in the community for all of the general public.
Those software‘s are attached with a certification issued by OSI (Open Source Initiative). Where the certificate shows that the source code of the software is made available free of cost for the general public. The motto of those group of programmers is to give a useful & bug–free software to everyone, without interest in the financial gain. The software program cannot be packaged for commercially used.
The programmers can read and re-edit those program‘s source code via the internet to improving the software with bug-free. The positive side of this, the process of eliminating bugs and improving the program, happens very much faster than the traditional process.
You May Like TO Read:
Here I Give You The Criteria Of An OSI Certified Product
The Criteria Of OSI (source)
To comply with the Open Standards Requirement, an “open standard“ must satisfy the following criteria. If an “open standard“ does not meet these criteria, it will be discriminating against open source developers.
- No Intentional Secrets: The standard MUST NOT withhold any detail necessary for interoperable implementation. As flaws are inevitable, the standard MUST define a process for fixing flaws identified during implementation and interoperability testing and to incorporate said changes into a revised version or superseding version of the standard to be released under terms that do not violate the OSR.
- Availability: The standard MUST be freely and publicly available (e.g., from a stable web site) under royalty–free terms at reasonable and non-discriminatory cost.
- Patents: All patents essential to the implementation of the standard MUST:
- be licensed under royalty–free terms for unrestricted use, or
- be covered by a promise of non–assertion when practiced by open source software
- No Agreements: There MUST NOT be any requirement for execution of a license agreement, NDA, grant, click–through, or any other form of paperwork to deploy conforming implementations of the standard.
- No OSR-Incompatible Dependencies: Implementation of the standard MUST NOT require any other technology that fails to meet the criteria of this Requirement.
Stay Tuned By Subscribe Us