Frequently asked questions
Clarifications of popular misconceptions about Open Source
- Q: Can we just post the source code on the web when we ship a product containing OSS?
- Q: Should I make the source code available to the public?
- Q: Can I provide source code via the developer’s web site?
- Q: Should I make the source code available to the community?
- Q: Can I change the license of the OSS I created?
- Q: Can the conditions of use of the product be freely set?
- Q: Can I modify the license of the OSS I downloaded?
- Q: Should I abide by the licensing conditions when I install the OSS on a PC that will be my customer’s?
- Q: If it's the same license document, does it need to be listed in duplicate?
- Q: Does attaching a license document become a modification of the OSS?
- Q: Do I need to print license documents on paper to provide them?
- Q: Do I only need to provide the name and URL of the license document?
- Q: Is it preferable to provide translated license document?
- Q: Can I only provide a list of OSS names as OSS information?
- Q: If I contribute to an OSS community, do I need to abandon my patent?
- Q: Can a license violator be a patent infringer?
- Q: When I post a program to the OSS community, does that OSS become a patent infringement?
- Q: Can I assume OSS doesn’t involve patent infringement risks?
- Q: Can OSS names be used in sales promotion media?
- Q: Can I use the same OSS my colleagues have already used without problem?
- Q: In the absence of any conditions, can I use a free program without restriction?
- Q: Can I use OSS for commercial purposes?