844
China is attempting to mirror the entire GitHub over to their own servers, users report
(infosec.exchange)
This is a most excellent place for technology news and articles.
again, I don't have a problem with copying code - but I as a developer know whether I took enough of someone else's algorithm so that I should mention the original authorship :) My only problem with circumventing licenses is when people put more restrictive licenses on plagiarized code.
And - I guess - in conclusion, if someone makes a license too free, so that putting a restrictive (commercial) license or patent on plagiarized / derived work, that is also something I don't want to see.
I have no problem copying code either. The question is at what point does it go from
To
How abstracted does it have to be before it's OK? If you write a merge sort, it might be similar to the one you learned when you were studying data structures.
Should you make sure you attribute your data structure textbook every time you write a merge sort?
Are you understanding the point I'm trying to get at?
My trivial (non legal ;) answer is: If you are working for a corporation that is looking to patent something / make something closed license: the moment you ever looked at a single line of my code relevant to what you are doing, you are forbidden from releasing under any more restrictive license. If you are a private person working on open source? Then you be the judge whether you copied enough of my code that you believe it is more than just "inspired by".