Earlier quoted context omitted.
> Many homebrew projects don't want to be fully Open Source because they want to hold back some special sauce, either to slow down efforts by the console vendor to stop them, or to differentiate themselves from other homebrew projects for clout. So someone building a foundational library for homebrew on a platform might want to, legitimately or otherwise, avoid presenting themselves as GPLed. For context, The Homebre…
> Thing is, GPL requires you to explicitly allow that behavior, so HBC can't use GPL software. Couldn't, not at the time. HBC has been open-sourced some time ago, sans DRM, as the Wii has long lost commercial relevance beyond enthusiast communities. This open-source re-release is what the repository is.
Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
71–80 of 169 posts
Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#72Since y'all decided to flag my other comment I'll rephrase: Can someone explain what harm is being done by an open source non-commercial project "stealing" code? Who is actually hurt by this, and how? Let's ignore for the moment nothing was actually stolen since the original authors still have their copies.
Call it what you want, but it's just disrespectful and unnecessary. I'm sure we've all fucked up somewhere and didn't attribute something correctly, but I feel like once it's been brought to your attention, it's just silly to not at least acknowledge it (especially if people are paying you to work on it). In this case, it's a somewhat serious licensing issue even if it is unlikely to lead to any actual legal action.…
Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#73Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#74Earlier quoted context omitted.
Call it what you want, but it's just disrespectful and unnecessary. I'm sure we've all fucked up somewhere and didn't attribute something correctly, but I feel like once it's been brought to your attention, it's just silly to not at least acknowledge it (especially if people are paying you to work on it). In this case, it's a somewhat serious licensing issue even if it is unlikely to lead to any actual legal action.…
Okay, sure. But the question is what harm is being done. Am I understanding you correctly that your answer is that there is none?
Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#75How much "reverse engineering" these days really is clean room and how much of it is just ripping off proprietary software? One can easily find a bazillion of "github repos" that distribute what is evidently directly decompiled game code with minimal cleanup. Bonus points if they also claim it is OK as long as the game art is not distributed, which in addition to being wrong is disrespectful to developers as a whole.…
Note that reverse engineering does not have to be clean room, poking at hardware without ever seeing any software. In many places, poking at the proprietary software, decompiling it, tracing it, and so forth is fine despite what unenforcable EULA's might suggest. What is not okay is taking the binaries or decompiled source verbatim and re-distributing it. Note that e.g. copyright does not apply to decompiled source c…
This isn't anything new or unique to programming. In the same way if I were to transcribe a movie (let's say it's a silent movie) to a script, it would still be that movie. Or if I were to translate a book into Klingon . Or even do a cover song of "Beat It" entirely with throat singing. Copyright would still apply.
Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#76Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#77What is "RTEMS?"
Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#78Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#79Earlier quoted context omitted.
Call it what you want, but it's just disrespectful and unnecessary. I'm sure we've all fucked up somewhere and didn't attribute something correctly, but I feel like once it's been brought to your attention, it's just silly to not at least acknowledge it (especially if people are paying you to work on it). In this case, it's a somewhat serious licensing issue even if it is unlikely to lead to any actual legal action.…
Okay, sure. But the question is what harm is being done. Am I understanding you correctly that your answer is that there is none?
Re: Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS
#80What is "RTEMS?"