/kbin meta

This is the kind of transparent communication that buys so much goodwill and trust from the community. I've been enjoying my first experience in the Fediverse with Kbin, and the response here only makes me love it that much more. Nicely handled.

@ernest Hey man, if it's of any help, I have a PHP (laravel) project which mostly federates fine, license is AGPLv3 as well, so feel free to reuse what you see fit.

Edit: may be more useful with the link 🤦‍♂️

https://gitlab.com/j3j5/fedibots/

Seems just like another day with open source software.
You gotta be careful about licensing and attribution and it can get really messy, but no big deal really.
Seems like you're correcting this and acting in good faith.

It shouldn't happen, but it happens. Thanks for the transparency

We appreciate the transparency and hope everything can be solved without much friction. Keep it up!

It was a mistake and you went about this the right way. You're doing an amazing job!

Emma's point is valid, but it was a pretty ham-fisted and overly-agressive way to approach it. May need to touch some grass. Could have just been a "hey, noticed this. Could you look into this?" And then if your response wasn't great then get mad. Seems like the assumption from they get-go was that you're just an asshole that didn't care and did it intentionally.

Website is definitely running faster. Thank you @ernest

I feel a lot more comfortable with the developer of kbin (@ernest) than the Lemmy devs.

Here, he messed up by not giving attribution for some code, but the transparency and remedy of the error are appreciated.

It’s nice to see something that builds trust as opposed to burning it down like at #Reddit

#fediverse #kbin

It's alright. I do think the actual issue was worded perhaps a bit harshly and combative, and I think you responded correctly. Very much appreciate the accountability here. To be honest if anything, this probably gives me more faith in you in the long run. There are many ways you could have dealt with it, but as far as I can see you've dealt with the issue as honorably as you could have.
Proper attribution can be tricky. We all learn. We all make mistakes. A lot of us will never release a project that makes it as far as yours has so even our issues don't become even nearly as visible.
Keep your head up and stay calm. You're doing great. We got you.

Lol, she picked a hell of a username on codeberg. Very fitting.

"Hey Ernest, I see you have used my code from (project) without proper attribution as required by the license. Can you please correct the attribution or remove the infringing code?"

How hard would that have been? If she didn't get the response she wanted she could then escalate.

Mistakes happen, what matters is how you recover from them. Keep doing what you’re doing!

Cross-posting my comment:

This is one of my largest frustrations with the open source community. Everything is immediately assumed as malicious. There is no escalation, it's "you screwed me over" from the jump.

I suppose it's bred from decades of large corporations pilfering open source for profit. However, this post could easily have been, "I noticed there's some code I wrote that wasn't attributed, would you mind adding that?". Escalate from there if the appropriate actions aren't taken.

Seems to me you're handling it the best way possible - yes, re-using open source code without proper attribution is an unfortunate mistake, but you've also clearly explained the reasons it happened. I also understand why the original code author reacted very strongly; when code is stolen maliciously and with intent, it's a huge "fuck you" to the original authors, who have freely released their code on the basis that they receive attribution of their use.

Good to see you've subsequently made up, and the code can stay. Thanks for being transparent, @ernest!

Damn emma really tore into you in that issue lol. A lot of assumptions about malicious intentions when a simple mistake seems much more likely. I mean I know they're in the right defending their work but damn idk if they needed to make such a big public stink about it lol

I like you even more now for admitting your mistake without any hesitation and taking the steps to rectify your error. Keep up the good work!

Every single thread or comment I see from you further cements the image of a good dude.

Mistakes happen, how we handle it defines us, and you've handled this the best way possible.

Licenses are hard. The fact that you are being transparent means this was not malice. Keep improving, and it all will work out in the end.

Thank you very much for the transparency

Thanks, Ernest. You’re good people. 😊

You handled this extremely well, especially in the face of someone so clearly looking for things to be outraged by. LitigiousEmma had no reason to be that aggressive right out of the gate and comes off as someone that the Open Source community would be significantly better off without.

Appreciate the transparency Ernest.

Frankly, it's very refreshing to see someone running the show that has this combination of work ethic, passion without hunger for power, and honesty. Thank you for the transparency!

You've obviously got a million things going on a minute here. Like someone juggling flaming swords, I don't think anyone is going to blame you for dropping one accidentally while more fire-soaked swords keep being tossed at you. Seems like you know what to do and that there are a lot of talented folks here willing to provide help anyway they can. We're with you (me in the sentimental sense, I'm not so talented when it comes to coding)!

@ernest I thought you killed someone, based on the title 😂

I agree with the other commenter. Seems like you’re making it right. This is a new and sometimes messy frontier for a lot of people and processes. If someone is worried about protecting their IP, this isn’t the hill to die on.