We will try to make it happen
The example repo is actually: https://github.com/cocos-creator/example-cases/tree/v0.7
example-packages is the plugin package example, but it won’t work with v0.7, please wait for our v1.0 to try it out
Cocos Creator will be partially open sourced:
There are some close sourced core modules, and I don’t think they would become open source.
No, they have different purposes, to support Entity Component architecture, we have build up a EC level on top of Cocos2d-html5, but we also modified tons of the details in Cocos2d-html5, basically we can’t simply merge from one to another. Most changes we made in Creator won’t and can not be merged back, but we have some common feature plan for them, like auto batching, better resource management.
In conclusion, Creator web engine and Cocos2d-html5 are already taken different paths, we will try our best to do things cleverly and cleanly, so that both side can take benefit from the improvements on base modules. But I also admit our priority is switched to Creator, and new features built on EC architecture aren’t like to be merged into Cocos2d-html5.