2 ms·
I said something slightly similar once. A little weirdness was going on, in a niche platform community, so a while ago added a statement on a Web page that lis
by neilv 5y ago
I said something slightly similar once. A little weirdness was going on, in a niche platform community, so a while ago added a statement on a Web page that listed my packages for it:
> If you'd like to put modified copies of my packages in public Git repos, or otherwise distribute them, I'd appreciate you reaching out to me. The license very intentionally gives you the right to modify and distribute, but [niche project] is a small and cooperative world right now, and it's better for everyone if we coordinate.
One of incidents that prompted this wasn't compliant with the licenses, but I thought I'd leave it at the above.
Back to TFA, I'm somewhat sympathetic to the developer there, not wanting to get support requests, etc., for problems caused by a packager, and this is a problem that, say, distros normally have to address.
(And I've seen it addressed badly, such as a third-party setting up a bug-reporting system for my upstream packages, which gave the appearance of being the official way to report bugs, but... I didn't know about it, I didn't get notified when people made bug reports there, no one was handling those reports, and, when I eventually stumbled upon the reports, the mechanism didn't have a way to contact the submitter for more info. The bad mechanism was just sitting out there, wasting submitters' time, and sabotaging success of the project. Then, when I explained to the party running it that it was hurting the project and contributors, they refused to make it opt-in or let me opt-out. I think this is just one example of the kinds of time-suck that you see after contributing to open source for a while, and which might not be obvious to people until they've seen it or heard about it.)
That said, while I think the developer in TFA is fine in saying that they'd prefer a package they develop not be included in some other thing, or perhaps explains why and asks for changes in how that's done to not hurt the developer's work... they have to be aware that, at least in US culture, their request (like mine, in a different situation) is orthogonal to the license, and is a cooperation "ask".
There's some value in having terms clearly communicated (such as with licenses). And when you give a license, if you're going to ask for a restriction on what you already gave in the license, you're taking away some of the value of licenses.
Considering this an "ask" is even more appropriate -- but not limited to -- cultures/subcultures that might consider "whatever is legal" (or "whatever you can get away with") the sole consideration.