This is my first open source project, apart from tiny bits of code that no one ever paid any attention to. Maybe I don’t know how to do open source properly, maybe I made a mistake here. Let’s find out. A few months ago, someone made a new fork of PieFed, which they called ‘Pylova‘. […]
Just give pylova proper attribution. That’s all rimu needed to do. It’s not stealing it’s just a minor license violation -at worst. Typically, every single file doesn’t need the license in it. So that’s kind of a cop out by Rimu. Contributors should be acknowledged for their contributions.
Why do developers of open source software have to make shit so difficult?
It does sound like a genuine mistake as opposed to something sneaky.
I’m far from an expert on open source best practices, and I also wouldn’t have known the difference between taking code with a .patch file vs taking code with copy and paste. I probably would have attributed it in some other way, but I’m a bit anxious that way and tend to go even further and overdo things. It takes me forever to publish posts and website updates out for our instance.
Why do developers of open source software have to make shit so difficult?
I think that’s the nature of forks of projects. When someone makes a fork, there is usually some kind of tension between the two developers and so something that feels small to outsiders might feel more significant to those involved.
When you have the context he left out, it sounds less like a genuine mistake and more like deliberate malice. He intentionally tried to take the code instead of simply cherry-picking a commit and keeping attribution, something I have no issue doing.
incredible that his tools tried to default to doing the right thing, giving proper attribution, and he still went out of his way to not give proper attribution for where code originated. like… actually factually there would be no licensing issue if he just let the default behavior happen
If he’s this terrible at manual attributeless patching, I question how Rimu has even coded piefed at all, all this time.
Did he contract someone else, and refuse to pay?
Just give pylova proper attribution. That’s all rimu needed to do. It’s not stealing it’s just a minor license violation -at worst. Typically, every single file doesn’t need the license in it. So that’s kind of a cop out by Rimu. Contributors should be acknowledged for their contributions.
Why do developers of open source software have to make shit so difficult?
How do you the attribution correctly?
Depends on the license
It does sound like a genuine mistake as opposed to something sneaky.
I’m far from an expert on open source best practices, and I also wouldn’t have known the difference between taking code with a .patch file vs taking code with copy and paste. I probably would have attributed it in some other way, but I’m a bit anxious that way and tend to go even further and overdo things. It takes me forever to publish posts and website updates out for our instance.
I think that’s the nature of forks of projects. When someone makes a fork, there is usually some kind of tension between the two developers and so something that feels small to outsiders might feel more significant to those involved.
When you have the context he left out, it sounds less like a genuine mistake and more like deliberate malice. He intentionally tried to take the code instead of simply cherry-picking a commit and keeping attribution, something I have no issue doing.
incredible that his tools tried to default to doing the right thing, giving proper attribution, and he still went out of his way to not give proper attribution for where code originated. like… actually factually there would be no licensing issue if he just let the default behavior happen
If he’s this terrible at manual attributeless patching, I question how Rimu has even coded piefed at all, all this time.
Did he contract someone else, and refuse to pay?
It does explain a lot of the poor methods and logic used. And why they didn’t want to actually learn rust
From syntactic stand point, SBCL should be his next language, as Python is parenthesisless Lisp.