Oh this is no big deal at all (because your code is already open source)! I've dealt with similar situations at businesses before and it's just a matter of including the correct licenses and annotating the code where appropriate.

Let's say you used some AGPLv3 (strongest copyleft license) licensed code and you're not distributing your code under that same license. How do you use the AGPLv3 code in your code even though you're using say, Apache 2.0 license? The simplest way is to move that AGPLv3 licensed code into it's own folder/file(s) and put that license in there along with it. Also make sure you add a note about this in your LICENSE file and indicate that if someone includes that specific code in their own implementation they'll need to adhere to the AGPLv3.

Some FOSS licenses are incompatible with each other but I don't think you have that issue. For stuff like the Zip license, Apache license, MIT, and similar licenses where you must "give credit" just add comments surrounding that code saying where it came from, what license it uses, and also include references to it in the LICENSE file.

Loads of FOSS repos have complex stuff like this! It's a bit tedious for sure but it's not rocket science. You just have to do your homework and basically, "write everything down" (giving everyone credit and paying close attention to special cases like the AGPLv3).

@ernest I appreciate the transparency on this. Don't beat yourself up too much though, we all make mistakes and this one is easily fixable with attribution.

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.

You can only be honest like this and do your best! Thanks for all your hard work!

Thank you very much for the transparency

Although I'm parroting other's sentiments, I really do appreciate the transparency you have shown. Keep up the good work!

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

I feel like you being this transparent about the whole development process is really going to help you earn the users' trust :)

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.

However I feel about the wording Emma chose, at the end of the day it was within her right to call you out. It's a great sign of good faith that you took the criticism, apologized, and are acting on it. From personal experience I also take stuff from the internet for personal projects... except my personal projects don't grow a thousandfold in terms of users almost overnight.

Don't sweat it, man. You're doing great.

Don't be so hard on yourself. Shit like this happens.

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

I have no idea what this means but admitting your mistakes shows you are a mensch. Appreciate the updates and the effort!

I think it just becomes a habit to use public libraries as a developer, that licences is not something you give a lot of thought after a while. And then your project blows up and a developer asks for an attribution. Which you gave, and was accepted! I don't understand the drama! It feels like it was settled very amenable and friendly!

@ernest Shit happens. Thanks for owning it and making it right :)

💕

Transparency matters. Even if it comes a little bit late, its good to see the ability to admit a fault. Btw, thanks for allowing us all to hijack your once upon a time small website @ernest lol

Good on you for being so transparent! Very well handled mate.

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.

Most of the techy stuff goes over my head, but I do understand the importance of giving credit, as a student in the world of science academia. It looks like you're handling the situation well. We're all human, we all make mistakes, and plagiarism is a serious thing that slips under our noses sometimes. You're learning from this experience, which is a good thing!