/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.

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

@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.

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

@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.

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.

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!

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.

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)!

The title here scared me so much haha. It just seems like there's a credit issue? I don't think you've done anything wrong. Small projects naturally are like that, and kbin kinda exploded in size quite fast, so it's understandable. Transparency is good. There's no rush I think. Honestly this post just makes me realize even more how awesome kbin is and how great of a dev and admin you are. It's rare to see. Massive kudos.

Everyone makes mistakes. Your response was not to deny or try to redirect blame, but to own up to it and fix the problem - and there is no lasting harm. Honestly if anyone asks for more than that they're being an arse! Keep doing what you're doing, I'm one of the trillions of Reddit refugees, and I like what I see here

As a thought, this project is clearly suddenly getting much bigger than you intended. Maybe see if you can take inspiration from Linux Torvalds about how to manage a project on this scale while retaining control of it - he is basically the benevolent dictator of the Linux kernel, what he says goes (and he has had some very famous arguments!), but he does delegate and take help where he needs it.

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

Seems that so long as the attribution is in place the Postmill people aren't going to push it further. I (and I hope the community) appreciate your transparency and honesty. That's the sort of thing that makes me want to stick around here and support this project.

And for fun, I will check out those other sites, since I hadn't heard about Postmill/Raddle before.

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!

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.

If there's anything I've learned from programmer humor reaching all it's that 95% of code is creatively liberated.

That being said I'm happy to hear you being transparent and giving the credit where it's due!

Keep up the good work man and try not to burn yourself out, I know this just be a stressful time!

Website is definitely running faster. Thank you @ernest

You, sir, are an honorable person. I think I can speak for all open-source hobby programmers when I say: you make us proud.

I honestly don't see this as a big deal, but I'm glad that you're being honest and open. Attribution is cool and all, but Emma makes it sound like you committed some sort of cardinal sin. I can never understand why someone who uses a permissive license gets so upset when their work is not attributed, you gain almost nothing from it.

Again though, attribution is still a net good. I think it's the polite thing to do, and I'm glad you're doing it.

Thank you for the transparency

This is exactly what we like to see, people actually taking responsibility for their mistakes and rectifying them in an open and transparent manner

Don't stress ernest. Mistakes happen

@ernest thank you for being transparent with us, it's what we can hope for when on platforms like this. I am happy to be here on kbin!

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.

We appreciate your honesty and transparency, keep up the good work!

Is 'LitigiousEmma' an inside joke, or an extremely relevant username? haha

Edit: For some reason this keeps bouncing around in my head and the more I think about the more I believe that Emma should have contacted you privately (at first, anyway) instead of jumping right into attempting to publicly shame you.

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

That's ok dude. That's the nature of coding. We all copy and paste and take ideas from other places. Attributing is a low priority for minor personal projects and now suddenly your personal project is a bit bigger.

All good. No harm done. I look forward to seeing how this platform grows even more.

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).