Where can we learn more about your experience managing a large codebase, such as a custom version of ClassicPress? I noticed your site’s membership rules were not inline with the GPL, so, all this gives me pause.
Really? How so?
If someone writes something and offers access to it through a membership, can that person not declare whatever rule(s) he or she see fit?
Reading the full GPL text will save you a lot of headaches later. It’s a good idea to have a solid understanding before you go diving in with the GPL.
Not with GPL code, no. You can charge for it and place rules on it…but nobody has to abide by them. The license specifically states that anyone can use it, reuse it, modify it, resell it, share it, etc, etc. You can’t place any limitations on it. If you’re writing code for a GPL platform (ie, CP/WP) then your code is GPL by default, save for any proprietary images and documentation, et al.
I missed one thing (sorry). I do know about GPL and its overall meaning and what not. I did not know about the part that you just explained when paid for.
No worries. We’re all entitled to an opinion. The GPL is clear, though – we’re unable to restrict end-users in any way.
This is why you often see dev-shops offering free stuff (ie, plugins) and end users can then pay for updates and support, or extra features that are not available publicly. Of course, the end user could still do whatever they want with any premium code they get.