Skip to content

Frequently Asked Questions

My software is already on GitHub, why is it not Open Source?

A solution isn't Open Source unless it's shipped with an Open Source Initiative1 approved license2. Open Source authors wish their solution to be used, modified, and shared. As the legal default is exclusive copyright, you need to explicitly give these permissions with a license.

Does Open Source mean anyone can modify my software?

No, while anyone can make a copy of your source code, that doesn't mean anyone can modify your copy. Think of a cookie to recipe example, if you make your recipe public, doesn't mean anyone can modify your personal copy of the recipe (or your cookie). In Open/Inner Source3, there is a workflow where all new changes are proposed, and maintainer of the project reviews any new code before adding them to the original copy. In a well developed software, there are often automated tests that check for any bad code as well. It can range from feature breaking changes, or bad security practices.

Does Open Source mean I have to share users' data?

No, Open Source means just the source code of your software. User data must be kept private - unless there is a specific strategy where data can be helpful after stripping PII -- but that's a different discussion that part of making your solution Open Source.

Will it cost me to make my solution Open Source?

If your existing solution has security issues (like hardcoded passwords, API tokens, server addresses etc), then it's best recommended to remove them as variables (as per software development best practices.) read next answer.

Does developing Open Source cost more money than developing Proprietary solution?

Open Source software is not a more expensive, or cheaper way to develop software by itself. It's a different way of developing a software. If the team is not sure how to follow open source development practices, it might add cost to train/upscale team.

It can add cost as when developing Open Source solution - transparency and public availability of source code often incentivizes following best practices, and that requires good quality code, tests, documentation - all of which can add some cost. It's important to understand that this also implies software was not being developed with best practices otherwise, and that can add cost later in terms of hard software to maintain or higher cost by vendor to refactor/add new features.

No, Copyright is fundamental to Open Source. Each and every Open Source license requires you to provide attribution to the copyright holder, and follow requirements of a license (permissions). Copyright in general means no one can use, copy, modify, or distribute your work without being at a legal risk. Open Source authors wish their solution to be used, modified, and shared. Because the legal default is exclusive copyright, you need to explicitly give these permissions with a license.

How do I know which license is suitable for me?

  1. The Open Source Initiative is the steward of the Open Source Definition, the set of rules that define open source software. ↩

  2. Open source licenses are licenses that comply with the Open Source Definition, and are approved by the Open Source Initiative. ↩

  3. Inner source is the use of open source software development best practices and the establishment of an open source-like culture within organizations for the development of its non-open-source and/or proprietary software ↩