I have made the repo private since yesterday, So I guess it shouldn't be a problem anymore. I appreciate that you took the time to look into the problem and thanks for your effort ❤️
You're welcome. Before I saw your reply I added a paragraph to end of my comment on GPL license which has a copyleft requirement. Not sure if that may be useful to you or not.
The short explanation of "copyleft" licenses is that if you apply a "copyleft" license to your code, then anyone who creates a derivative work from your code must apply the same license to their code. This implies that any derivatives of the derivative, etc also will have the same license. In essence, it keeps your code and anything derived from it open source. Whereas with an all permissive license like MIT, there is no such obligation on those who create derivatives (e.g., MIT licensed code can be used by others, including derivatives, in closed source software). In both cases, you are still the copyright owner, but you license away more of your rights with MIT or Apache than you do with the GPL and other "copyleft" licenses.
Making the repo private doesn't solve the problem. He has already copied the code and I'm sure others have done the same, but you just saw that of his'. I think the solution is simply licensing. Thanks to Vincent A. Cicirello for clarifying all types of open source licences.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have made the repo private since yesterday, So I guess it shouldn't be a problem anymore. I appreciate that you took the time to look into the problem and thanks for your effort ❤️
You're welcome. Before I saw your reply I added a paragraph to end of my comment on GPL license which has a copyleft requirement. Not sure if that may be useful to you or not.
I don't have much idea about what copyleft concept is. Where can I read more on the topic?
The short explanation of "copyleft" licenses is that if you apply a "copyleft" license to your code, then anyone who creates a derivative work from your code must apply the same license to their code. This implies that any derivatives of the derivative, etc also will have the same license. In essence, it keeps your code and anything derived from it open source. Whereas with an all permissive license like MIT, there is no such obligation on those who create derivatives (e.g., MIT licensed code can be used by others, including derivatives, in closed source software). In both cases, you are still the copyright owner, but you license away more of your rights with MIT or Apache than you do with the GPL and other "copyleft" licenses.
Here's a link that explains in more detail: gnu.org/licenses/copyleft.en.html
well not if he also posts it as he claims it be his.
Making the repo private doesn't solve the problem. He has already copied the code and I'm sure others have done the same, but you just saw that of his'. I think the solution is simply licensing. Thanks to Vincent A. Cicirello for clarifying all types of open source licences.