Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plagiarism #41

Closed
kpym opened this issue Dec 3, 2019 · 5 comments
Closed

Plagiarism #41

kpym opened this issue Dec 3, 2019 · 5 comments

Comments

@kpym
Copy link

kpym commented Dec 3, 2019

I wanted just to warn you that I have seen your code in another repo. The noteshrink.py looks the same, except that we can find Created by Georgy Perevozchikov (gosha20777) 2018. on line 7.

@kpym
Copy link
Author

kpym commented Dec 3, 2019

Well if you do not see a problem just close this issue ;)
For me the problem is not the reuse but the mention Created by ....

@mzucker
Copy link
Owner

mzucker commented Dec 3, 2019

@zvezdochiot this is not how copyright works. It's not good practice to change the creator name in MIT-licensed code. See for instance https://softwareengineering.stackexchange.com/questions/386582/altering-author-names-in-mit-license

You were licensed to distribute the software as long as you distributed the original copyright notice. Instead you modified the original copyright notice by replacing my name with yours.

Please correct this by restoring my name to the LICENSE file.

@zvezdochiot
Copy link

@mzucker say:

Instead you modified the original copyright notice by replacing my name with yours.

Wrong. I am an outside observer. I’m trying to understand why the noise is. And I can’t understand. Always interested in distributing my code, consider any obstacles to be hostile. I don’t understand your motivation at all.

@mzucker
Copy link
Owner

mzucker commented Dec 3, 2019

@zvezdochiot Sorry if you're not the author of https://github.com/gosha20777/NoteShrink/blob/master/LICENSE - I assumed that since you were the one replying, you were the author. In any event, I'll be filing an issue on that repo separately. Closing this issue. Thanks very much to @kpym for alerting me of this.

@mzucker mzucker closed this as completed Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants