Live data from Hacker News

“Please don't add any of my stuff to this project”

github.com

161–170 of 363 posts

Re: “Please don't add any of my stuff to this project”

#161
post #21

Is there greater context here that helps explain what's going on? Reading the comments in the thread didn't clarify much for me as someone unfamiliar with NixOS, their apparently unique Python packaging scheme, and Home Assistant.

He just doesn't want anything of his included in nixpkgs because he doesn't want to deal with anyone opening Github issues against his repos if there happen to be build / installation issues that are coming from some kind of failure in the nixpkgs install / build process.

That's speculative on his part (noone has opened any issues with him, neither coming from nixos nor from any other repackaging).

The nixos guys also offered various proposals to him to completely avoid any support burden on his part, all of which he roundly rejected.

Seems he's just being unreasonable for the sake of it tbh; I can't see any logical reasoning behind it all.

Re: “Please don't add any of my stuff to this project”

#162
It's interesting since from https://github.com/sponsors/frenck#sponsors he pitches:

> Are you enjoying my work? And want to support me in my effort helping the world to become a better place by dedicating my time & knowledge to create & innovate open source software solutions. Allowing everybody on this earth the privilege to enjoy those things for free?

Re: “Please don't add any of my stuff to this project”

#163

What's worse is this frenk guy seems to be the reason his packages are being added to nixpkgs He added the dependency himself https://github.com/home-assistant/core/pull/51645 Nobody gives a shit about frenk or his code directly here - they want to use Home Assistant. But now that frenk added his code as a dependency, he has the right to transitively make Home Assistant un-packagable on NixOS? EDIT: On top of that, t…

I’m no expert, but I’m fairly sure that Frenk’s license has to be compatible with home assistance’s license for it to be included. If home assistance has a normal OSS license, I doubt it can use a dependency with a very restrictive license. (Such as one with a list of what can use it!) In other words, I don’t think it’s possible form him to transitively make home assistant’s license more restrictive.

Re: “Please don't add any of my stuff to this project”

#164
post #43

Earlier quoted context omitted.

He doesn’t understand the letter of OSS either. Limiting who can distribute a project means it no longer meets the Open Source Definition and is therefore not OSS.

No, he acknowledges explicitly early in the thread that the license allows the code to be redistributed with or without his approval.

And later he states "Unfortunately, you are wrong there. I will explicitly and publicly list parties that are allowed distribution in the license and allow for requesting distribution requests."

The "fine article" always contains the correct bits.

Re: “Please don't add any of my stuff to this project”

#165
post #144
post #112

Earlier quoted context omitted.

I think they proposed this: > Would you be happier if we forked your upstream source to provide our own, or provided a similar Python package with an identical API that we can use as a drop-in replacement? Wouldn’t this remove the burden of support from the author? Or it might be that I don’t understand exactly their proposal.

It would only remove the burden if users of the NixOS package know to go to the fork for support, as opposed to the upstream.

I am not using NixOS but in general every package manager links to the project homepage let’s say (or name of the project which for example in a GitHub fork is clearly different than the original) which in this case would be the fork.

So for example if this will be the case with a package I use I will report the bug to the fork because the package manager showed me their link.

I will not search for name-like projects or the original one and report there if a fork was distributed to me.

This is why I am confused why a fork is not solving the burden of possible bug reports. Also the fork assumes its own maintenance this is the purpose of the fork.

Re: “Please don't add any of my stuff to this project”

#166
post #29
post #14

Earlier quoted context omitted.

This is why we can’t have nice things. The project could have pinned the version and downloaded from pypi rather than repackaging. This isn’t a situation of “can do” it was “is it nice to do.” And the author mentioned that he’s changing the license to prevent it so it no longer becomes possible legally. I typically don’t like authors demanding stuff outside their license, but this started as a simple technical/commun…

What you are proposing doesn’t work with nix packaging

And that is the point: a nix problem becomes his problem all of a sudden.

Re: “Please don't add any of my stuff to this project”

#167
This looks like an attempt to ridicule the guy. He’s made a simple request and he doesn’t have to explain himself. The other parties can comply or not, they may ask questions or not, but surely publishing this non-story to HN and have people interpret his actions, fantasize about his understanding of OSS, their social skills etc, and eventually deride him is a bit hostile and immature.

Folks, he’s a human being. He’s made his desire known and you don’t have to like it, understand it, or agree with it. Just leave him be.

Re: “Please don't add any of my stuff to this project”

#168
post #37

I don’t really understand the details here. Seems like they disagree about the ease of avoiding it being repacked. Perhaps a good compromise would be for them to collaborate on a solution they’re both happy with. As it is, this conversation looks like: “can you not pls” “too difficult” “no it isn’t” “yes it is” ad infinitum.

He's not interested in that. The NixOS folks asked:

"I'm also a little anxious that this thread has the potential to get heated quite quickly, so if you have the time and are willing to it might be worth setting up a quick Jitsi Meet to talk about this. Failing that, maybe we should pull this off into a separate issue thread so we can discuss there instead."

but he replied curtly with

"My wishes are above, please do not repack my code into this project. Please respect that request. It is a fairly simple request, nothing heated about it. I have no intention of spending time in this project.

Thanks."

Re: “Please don't add any of my stuff to this project”

#169
post #110
post #51

Earlier quoted context omitted.

When they offered to fork it completely to avoid the issue and he rejected that, it really just looks bad. I get being done with something when you've had a bad experience, but the maintainers here went to every effort to accommodate, and did so in a friendly way. It reads like this guy wanted a fight and an excuse. I think the correct answer is to just make the fork as proposed and use that instead, it solves the pr…

From what I can see in the thread (and I'm not very familiar with the tech so I'm working off of inference here) it looks like the library fetching tool is well equipped to fetch the freshest branch from his repository directly. His responses are very minimal but it sounds like he's objecting to older versions of his library being bundled in and causing breakages on the client side - forking would potentially just ma…

[deleted]

Re: “Please don't add any of my stuff to this project”

#170
post #105

Earlier quoted context omitted.

No! You are not obligated to receive support for software just because it was written by someone else.

There is a considerable difference between getting requests and providing support. You don't have to provide support, but it's a little hard not to get requests.

> it's a little hard not to get requests.

Well, you can disable the issue tracker for a project on GitHub. You're not even required to publish a project on GitHub, you can host it somewhere that doesn't offer any way to contact you.

Post reply on HN