3 ms·
Most forks mention their origins somewhere in their bio. I'd still call it a rip considering no credit is being given at all. Why should I need to dig into the
by goldenkey 5y ago
Most forks mention their origins somewhere in their bio. I'd still call it a rip considering no credit is being given at all. Why should I need to dig into the Git history to find out the creative origin of Lodash?
- capableweb 5y ago> Most forks mention their origins somewhere in their bio Ok, does that make forks who don't mention where they forked from rips? Huge leap in logic. > Why should I need to dig into the Git history to find out the creative origin of Lodash? Well, if you're interested in the origin you either look for information available in threads like this, where other people dig or you dig yourself. Not sure what the problem is. Someone published a library under MIT, another person forked that library and created a new one, also under MIT, and somehow the fork is now a rip? Give me a break
- Karunamon 5y agoThe license file reads: Based on Underscore.js, copyright Jeremy Ashkenas, DocumentCloud and Investigative Reporters & Editors <http://underscorejs.org/ http://underscorejs.org/> If they were giving "no credit at all", they would be in violation of the MIT license.