“Please don't add any of my stuff to this project”
1–10 of 363 posts
Re: “Please don't add any of my stuff to this project”
#2Really seems like you need to respect the author’s wishes here, but the tension between author and community can get complicated with FOSS. Open source is a contract with your audience that the code can be used freely. Authors gain their audience because of that contract, so there’s some obligation for them to respect that. That said, respect flows both ways, and I’ve had FOSS code get repackaged to steal credit which feels like just as much of a violation. (That’s not the issue here but it touches on the same challenge.)
There’s no silver bullet. Sometimes things just don’t work out right and you need to fork or make an alternative. I’d personally lean towards making an alternative in this case, if it’s possible.
Re: “Please don't add any of my stuff to this project”
#3Really seems like you need to respect the author’s wishes here, but the tension between author and community can get complicated with FOSS. Open source is a contract with your audience that the code can be used freely. Authors gain their audience because of that contract, so there’s some obligation for them to respect that. That said, respect flows both ways, and I’ve had FOSS code get repackaged to steal credit whic…
The author's wishes are formally and legally specified in the copyright license to the code he wrote, which is MIT and allows redistribution.
Everything else is simply noise.
Once you make your software free, it isn't yours any longer and your opinions about it (or what others do with it) aren't relevant.
Re: “Please don't add any of my stuff to this project”
#4I've seen a similar situation when Ansible were resolving issues with Jinja2 but Ansible contributors simply helped the Jinja contributors to resolve the issue. It wasn't like all the burden was put on the jinja project.
Now those are two very active projects but what I mean is that no one is forcing the author of the repackaged code to support anyone he does not have time to support. If they want support they can ask the nixos project maintainers for it.
Re: “Please don't add any of my stuff to this project”
#5Really seems like you need to respect the author’s wishes here, but the tension between author and community can get complicated with FOSS. Open source is a contract with your audience that the code can be used freely. Authors gain their audience because of that contract, so there’s some obligation for them to respect that. That said, respect flows both ways, and I’ve had FOSS code get repackaged to steal credit whic…
The author's wishes are formally and legally specified in the copyright license to the code he wrote, which is MIT and allows redistribution. Everything else is simply noise. Once you make your software free, it isn't yours any longer and your opinions about it (or what others do with it) aren't relevant.
The author’s contractual wishes are specified there. It’s fine for an author to have additional, non-contractual wishes. (Legally, it’s equally fine for someone to follow or not follow those additional wishes.)
Re: “Please don't add any of my stuff to this project”
#6Really seems like you need to respect the author’s wishes here, but the tension between author and community can get complicated with FOSS. Open source is a contract with your audience that the code can be used freely. Authors gain their audience because of that contract, so there’s some obligation for them to respect that. That said, respect flows both ways, and I’ve had FOSS code get repackaged to steal credit whic…
The author's wishes are formally and legally specified in the copyright license to the code he wrote, which is MIT and allows redistribution. Everything else is simply noise. Once you make your software free, it isn't yours any longer and your opinions about it (or what others do with it) aren't relevant.
I can’t comment on the legal issues but AFAIK you can change licenses with future releases, not retroactively, so while you might be right, software requires support and losing future releases is often close to losing the software entirely.
On the non-legal side, there’s still a much broader issue of being good members of a community. We do, in fact, live in a society.
Re: “Please don't add any of my stuff to this project”
#7Really seems like you need to respect the author’s wishes here, but the tension between author and community can get complicated with FOSS. Open source is a contract with your audience that the code can be used freely. Authors gain their audience because of that contract, so there’s some obligation for them to respect that. That said, respect flows both ways, and I’ve had FOSS code get repackaged to steal credit whic…
> Open source is a contract with your audience that the code can be used freely.
Not in common-law jurisdictions, where an open source license without consideration is a bare license and can be revoked at will by the licensor.
Re: “Please don't add any of my stuff to this project”
#8Seems like an author that doesn't understand the spirit of FOSS. The nixos team was clearly allowed to use it and include it when asking for some technical merits as to why, and even offering many alternative options to appease the author the author seemed to just childishly stamp their feet and say, "because I said so". Eventually the author took the position of "taking my ball and going home". Why is a person like this even engaged in FOSS if they don't have a desire to share or even engage in a reasoned discussion?
Re: “Please don't add any of my stuff to this project”
#9Really seems like you need to respect the author’s wishes here, but the tension between author and community can get complicated with FOSS. Open source is a contract with your audience that the code can be used freely. Authors gain their audience because of that contract, so there’s some obligation for them to respect that. That said, respect flows both ways, and I’ve had FOSS code get repackaged to steal credit whic…
The author's wishes are formally and legally specified in the copyright license to the code he wrote, which is MIT and allows redistribution. Everything else is simply noise. Once you make your software free, it isn't yours any longer and your opinions about it (or what others do with it) aren't relevant.
One of the comments:
"As the author of the package that is being re-packaged here. I'm against it being repacked into here. While licensing wise I cannot stop you, I do hope you can honor my request.
Thank you for considering respecting the author's wishes."
It seems more like a matter of respect than a matter of law.
Re: “Please don't add any of my stuff to this project”
#10The package author has gone on to open issues for their other Python packages too - https://github.com/NixOS/nixpkgs/issues/created_by/frenck - currently five open (and locked) issues.