-
Notifications
You must be signed in to change notification settings - Fork 6
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
Please give proper attribution - your project is a packaged version of a stackoverflow.com answer of mine. #1
Comments
I was hoping that my informal request for attribution would be enough, but just in case you're unaware of the legal situation:
http://stackoverflow.com/help/licensing If I don't hear from you in the coming days, I will report you for abuse. |
I have just filed a DCMA takedown request. You can learn about the process here. |
jfc... I get it, but damn. @mklement0, @barsh is/was on vacation. I'll submit a PR before you have an aneurysm, but more importantly break our build process. |
Hey, thanks for letting me know. Just to be clear: I want the repository to remain in place, and I think it's great that @barsh packaged it up, as I've stated. I do, however, think that just republishing other people's work verbatim without attribution is not acceptable, and since I hadn't received any feedback in 11 days I decided to take action. But if that's getting resolved now, that's great. I'm asking this innocently (I'm really interested in the answer): how long would you have waited? |
I was out of the country... this is my first day back, but I get so many messages from Github that I might have overlooked this anyway. I have made the requested changes. As @caseyWebb suggested, feel free to submit a pull request if you want more cred. |
I'm glad to hear that this was just a case of crossed wires - thanks for fixing the problem. As I've stated in my response on stackoverflow.com, I am glad that you took the time to package up my code for easy reuse via |
@mklement0 Lol, seriously though. You wrote 5 generic SLOC on Stack Overflow and DMCA'd him over it due to no responses in a week or so. Just pointing out a bit of absurdity with that. |
@Qix- You've read the exchange. You know what happened. You've made yourself feel superior. I respectfully opt out of this conversation you're having with yourself. |
@mklement0 Mmk. :) |
As I've said in a comment on my stackoverflow.com answer where you got the code from:
It's great that you've packaged it for
npm
, but you need to give proper attribution:README.md
contributors
key inpackage.json
If this were a one-liner, I wouldn't ask for this, but given that the entire functionality of your package is my code verbatim, and the contents of your read-me are the comments from my code verbatim, I think it's only fair that you publicly acknowledge where it came from.
The text was updated successfully, but these errors were encountered: