Yes I have talked to the haXe devs in the mailing list, but they have the same opinion as me, CC isn't really suitable as a software license and using it for software shouldn't be encouraged in anyway.

About consistency of the licensing, what about changing to dual license? Say users can choose between CC or MIT. In that case individual ports can choose to update their license or stay in the current state if no one has the time to do it soon.

But in anyway this is a task that should be done sooner or later, well, if PureMVC is still being used in the future.

Any update on this topic?

I would like to put pureMVC haXe port on lib.haxe.org which is the official place to put open source lib written for haXe. I think putting pureMVC on it can encourage more usage of the lib, since currently by my own observation, not many ppl is using or even know the haXe port for pureMVC.

However, it has a limitation on licensing. It currently allows only GPL, LGPL, BSD and Public Domain. Can only the license of haXe port be changed to BSD (or MIT, which is compatible with the BSD license and I can simply label it as BSD on lib.haxe.org)?