3 ms·
It’s also people thinking an open license is a free-for-all. I put out some simple scripts some time ago to move data across a couple of sites, under MIT - supe
by toyg 7y ago
It’s also people thinking an open license is a free-for-all. I put out some simple scripts some time ago to move data across a couple of sites, under MIT - super liberal license, “just keep the credits” and you can do anything you want. Simple, right? After a few years I checked the forks and the first (and often only) thing they were doing was to strip attribution everywhere. I mean, it’s github, you forked right from my repo, everyone can see it. And why would you do that anyway, if you’re after publicity just add your name on top! I opened issues and most of them halfheartedly apologized and put back my notices, others ignored me, others pulled down the repo altogether. I bet they’ve all re-stripped it back, by now.
It would be cool if the license metadata currently existing on GH could be extended to carry names, in a way that makes it impossible to strip attribution (depending on the license, of course).
- heavenlyblue 7y agoDoes anyone here on HN know of lawyer companies that would follow up on license violation requests in bulk? E.G. there are services like small claims court in the UK that _mostly_ automate the billing on unpaid invoices, is there something like that for licensing?
- cptskippy 7y agoMaybe we need something like the DMCA Takedown Tools in Youtube for GPL License violations on GitHub? /s
- toyg 7y agoWhy the /s? It would actually be a good idea. The whole point of open licenses is that they work inside the established framework of copyright laws.
- saagarjha 7y agoDMCA takedowns are a remarkably heavy-handed way to deal with software licensing, which is often something that can often be resolved with some good-faith discussion.
- toyg 7y agoI do agree, there is no need to be as draconian as that, but a mass-identifying tool to start the relevant conversations would be pretty cool.
- cptskippy 7y agoAren't most concerns with companies who exploit open source software without contributing their changes back? If we have source code and can determine it is derivative of open source but improperly licensed, does it matter? At that point we have the code and we know it's derivative and thus can infer the license. It's not like the publisher could come back at us for taking it back. I don't see the value in such a tool other than to abuse people who shared incorrectly. And if I ever shared code incorrectly and got slapped on the wrist for it, that might just be incentive for me to never bother to share again.
- toyg 7y ago> Aren't most concerns with companies who exploit open source software without contributing their changes back? Companies get away with this because developers don't understand licensing in the first place. Pushing a false message that "once it's out, anything goes" is detrimental to that state of things. > If we have source code and can determine it is derivative of open source but improperly licensed, does it matter? Of course it does, a license is a license, you cannot selectively apply only some of it. And yes, if the license is not followed, the original author can revoke consent to redistribution and usage. Have you actually read an open license? The GPL is very explicit on this matter. > if I ever shared code incorrectly and got slapped on the wrist for it, that might just be incentive for me to never bother to share again. That's not a problem. Opensource doesn't run on generosity, but on publicity - a currency that can be converted into actual cash. If you don't share your "left pad", sooner or later someone else will share his own version and reap the rewards. The time when we had to beg companies and individuals to share, is long gone.
- cptskippy 7y ago
- bscphil 7y ago> It’s also people thinking an open license is a free-for-all. I put out some simple scripts some time ago to move data across a couple of sites, under MIT - super liberal license, “just keep the credits” and you can do anything you want. Simple, right? This seems like a reasonable enough place to ask: if you have a project under MIT, and I pull a function out of one file to use in my project, where exactly do I owe credit? In a comment above the specific function? At the top of the file? In the main license file for the project (even if the whole project is under e.g. GPL)? Some combination of the above?
- jamesponddotco 7y agoI usually place it above the function. Like this: https://paste.ubuntu.com/p/BJGhs8qGcr/ https://paste.ubuntu.com/p/BJGhs8qGcr/
- bscphil 7y agoThat's what I've been doing. Hoping that satisfies my obligations under the license and makes most authors happy.
- toyg 7y agoIMHO the safest option is to drop it in the about screen or somewhere in the documentation, like Microsoft does, "This software includes portions of XYZ...". It doesn't really matter which line is what, imho, at the end of the day an actual trial would run some automated comparison analysis and pull out the relevant bits anyway. It's mostly about the spirit.