> Thanks Rich, that's a more useful starting point. Has dual licensing been > considered? Both in 2015 and now, the lack of GPLv2 compatibility has > shown to be a serious drawback to the APLv2. Dual licensing means that it is also available under a no-patent-protection license which is an issue for us.