- Can I opensource it in a way where changes is not open to the public?
- I have google verification file on my git, is it ok to put it in the public?
The platform is gitlab.
Open Source is sometimes described as “anyone can contribute”, but that’s an oversimplification. Open Source projects always have a gatekeeper or small community of gatekeepers who decide which contributions are actually incorporated into the project and which are rejected as not up to snuff or straight up bad ideas or whatever.
That’s what you meant by your first question, right? Not “how do I hide the code of future changes” but “how do I retain control over what code is added to my repo”, correct?
Even if you meant it the other way, you could theoretically do that. Open Source one version and then never release any newer versions.
To me open source means you have access to the source code. You can choose to modify it and let the author know you modified it. It’s up to the author to decide if they want to implement the changes.
Changes like contributions to your repo? Or changes like people can fork and modify the source code themselves?
