> Go ahead and continue the negative talk about me in regards to licensing violation claims if you must.
If you want to gain credibility on this, I suggest you to do an extensive research from your past work, see what open source code you used, and explain for each case, with more or less verifiable material, what actions, mandatory or courteous, you have taken in order to respect software license and their author (code publication, credits, and so on).
This all comes down to freshening up my GitHub and removing a Cydia Store product. This will be done but I let this mob mentality continue for too long.
I spread myself pretty thin. I can count 20+ projects depending how far into the couple years I go. I have well over 4GB of development files with the majority being source trees.
Some of these will be fairly straight forward and not require much action at all. As Xuzz notes here, I have my projects source up on my GitHub, sometimes it just needs to be updated. Also sometimes it is updated, but just lands up needing some organizing to realize it (version number mismatches in code or instance).
Most however will be difficult when it comes to who to credit. I found out this is taken close to the heart over the years. I upset someone I respect very much, Notaz, at one point for not giving credit where credit was due. I rectified this with psx4droid v3 which I used his source, maintained a COPYING and README, credited, and kept the source up to date on GitHub. The issue is many emulators have been rehashed and ported so many times. For instance psx4droid v3 is based on Notaz PCSX-ReARMed which is a port of PCSX-Reloaded which is based on PCSX at some point. Along the way it used a MAME author's source file for handling the GTE. The MAME author contacted me for credit on the next revision which has not happened yet, and we discussed the issue at hand was it being passed down so much. So sometimes the credit list is huge and mostly unknown, and sometimes licenses mismatch if you really look at the sources.
A good example is SNES which has been rehashed and ported to death from snes9x (and as Xuzz pointed out, will fix) almost exclusively. The code usually becomes a huge mix in the end to the point it's a good luck situation to unravel it.
So doing this is not impossible, I will have to find some balance to please as many as possible without going insane trying to figure the sort out. Most being freshening the source at GitHub and checking compliance there. In the end there will be those who will complain and smear regardless. For those in this mob, they would never be fans and/or customers in the first place, but they do affect the overall feel of a company. And that's what concerns me moving forward...
I appreciate you being calm and courteous with your constructive criticism.
Indeed, this is a hobbyist doing tens of programmers' job in his free time (this is a compliment) aka a hacker.
All these problems you describe remind me of most GPL violations: people not caring much where code comes from (gotta prototype fast), not using source management for their internal process, and then finishing a huge pile of code with no traceability whatsoever with regards to what come from where and whom.
Add to that the fact that you come from the emulator community, who is more interested in credits and who did what than licenses and legal stuff (as opposed to OSS communities).
Obviously, you've learned how to use git and other modern tools by now, but the damage has already been done, and your reputation tarnished. Regaining that back is not gonna be an easy one, because everyone is watching your every steps.
I already talked to you on Twitter about a violation in psx4droid: you published libpsx (https://github.com/zodttd/libpsx) which is the emulation library, the core of the app. But this is just a library, and not the whole app. And this library is under GPLv2, and you're basically linking to it and distributing it in your apk.
Therefore, the whole app (psx4droid) should be released as GPL, including the UI, and all the candy around(buildscripts…).
And that's with this kind of borderline behavior that you find so many people bad-mouthing you here on HN (no one is against the guy making a buck).
Your assessment is fairly accurate. Though I consulted with others over GPLv2 and its usage of libraries. One person consulted with was the author of this software.
The UI is in Java and is part of a closed source project which I have been honoring. The library is called by the JNI. It is not linked statically.
If you have more to say on the usage of libraries in GPLv2, please share.
If you want to gain credibility on this, I suggest you to do an extensive research from your past work, see what open source code you used, and explain for each case, with more or less verifiable material, what actions, mandatory or courteous, you have taken in order to respect software license and their author (code publication, credits, and so on).