
The real lock-in in GitHub is not the code, but the stars
GitHub stars have no value on their own. But ask yourself, what would differentiate a project on GitHub from GitLab if not for these stars?

GitHub stars have no value on their own. But ask yourself, what would differentiate a project on GitHub from GitLab if not for these stars?
Earlier, the Software world was rigidly divided between closed and open-source software. Microsoft Windows is closed-source, GNU/Linux is open-source. Microsoft Office and Lotus Notes are closed-source, LibreOffice is open-source. Turbo C++ is closed-source, and GCC is open-source. But now, a new class of software products has emerged whose core is open-source, but still, the open-source software is of limited use. One model is to offer some critical and useful functionality in a closed-source layer via a managed service in AWS/GCP/Azure, for example, Redis is open-source, but useful modules on top of it are not. Another model is to use licensing gimmickry, for example, MongoDB is licensed under SSPL which requires that if anyone offers MongoDB as a service, then the source code of the full service must be published under this license. The third approach is to make the core software open-source but make it dependent on closed-source cloud services. For example, the node package manager (npm) is open-source, but a closed source company owns the default npm registry. Android is open-source, but most day-to-day application ranging from Google Maps to Google Music are closed-source. Now onwards, rather than calling such software open-source, we should call them closeum.
There are two choices while writing on this topic. One is to write a detailed and accurate port. The other is to write a short post. I preferred the second approach and had added appropriate links to dig further. Target Audience? Someone who is planning to use FOSS, free and open-source code, as a building block for their software development. Someone who wants to contribute to FOSS Someone who wants to release source code of their project in public
This article illustrates some examples of how the Indian government deals with (Information) Technology. Some of these projects are unheard of while some generated unnecessary hype.