This goes both ways, because there are a number of projects we've had "controversy" around that probably only exist due to GPL violations hindering development of the GPL-friendly developers who would be releasing a far-superior product if they weren't being hindered.Disasterous said:There's the other officer on duty. The reason it translates into hindering development is that the devs focus their work on compatibility and fixing bugs, and then they get threatened by these two to have their work taken down if they don't hurry up n deliver w/e the police want. It makes devs not want to continue doing what they enjoy(ask the devs, you know who I'm talking about). I understand a friendly reminder that they need to follow gpl, but some aren't even sure what that entails. It's just a shame that a dev has to stop his work to immediately comply with gpl or face a bunch of bullying. I think you should take a different approach.
One example is the entire cIOS area...there are a number of devs who know how to do what Riivolution/RawkSD do, and I know many of them have actually made tools privately that do it, and unlike the Riiv/RawkSD developers they won't particularly care if their code makes pirates' lives easier...but none of them have actually released it. Could it be because they got sick of their GPL-licensed code (repeatedly) having its license violated and people in the community fighting against them and claiming they aren't "real developers" every time they try and get it fixed?