Closing with my blunt opinion. The challenges to Joomla Framework adoption outside the Joomla project are the license and the community. How do you address those challenges?
I realise you guys haven't exactly been sat on your behinds ignoring the latter issue, but regardless of the license, it's something that's still going to need addressing in the future.
Changing the license definitely won't be a panacea, it may pull more devs into the fold, but in the wider context the (somewhat) broken relationship with the Joomla community will still be there. We'll still be in
the position of 'enjoying' some (or all) of the issues you highlighted.
This doesn't detract from the need to have the licensing discussion, but it's still a concern. If you guys feel you haven't been getting the support you should (I'm not going to disagree) then something needs to happen (either way) to try and increase that support (I'll hold my hands up, I could/should do more and am working on freeing up some time).
The point is if the intent on disallowing permissive licenses is to prevent
proprietary usage, you need to think again and probably advocate for the AGPL.
And the death of Joomla! has just been foretold
AGPL has it's places but they are very
few and far between.
In other words, I don't care what your philosophic position is, just be consistent.
Deliberately applying consistency to your own beliefs leads to the creation of a fundamental truth, not sure any of us would benefit from that.
I've (quite badly at times) laid out why I think GPL is the right move - some of those reasons are self-serving, definitely - but I'm not sure 'inconsistency' is a valid argument in a licensing discussion. The right license will vary by project, so it'd be impossible to get it right if you felt you had to staunchly maintain consistency. Basically the same argument as the one that says a good dev will pick the right tools for the task rather than insisting on writing everything in C.
MIT is not an option. Unless you want to do all the legwork to contact each and every dev who has ever contributed to the Framework and get their express permission, then it would be an option, but as it stands, it's not an option because it's not in the JCA, and the JCA contains all thenpossiblenlicenses which OSM has the legal right to re license the code under. Anything is off the table at this point.
Not to mention the forum thread that would result.....
... have new and pertinent questions relating to the question at hand
Actually, all power to you guys, I think most (if not all) questions that could arise have been answered somewhere within this thread. It'd be good to know what the plans are to help support increased adoption (assuming LGPL is adopted) but that's less a licensing question and more a marketing one. Changing the license will open the door to other developers, but if they're already comfortable with something else, how are we going to 'sell' the benefits of the JF beyond what's already being done?
I'm going to stop posting now (unless a new question pops into my head) as I don't think I'm adding much value to the conversation at this point. Whichever way the vote swings, hopefully this thread will have been enough of a wake-up call to get the community a little more supportive of the work you guys have been/are doing (and will hopefully continue to).
EDIT: Sorry, left word-wrap on so broke a few paragraphs!