I think it would be great if the community could discuss, or that you propose, what would be the proposed setup. One suggestion;
- each cocos2d user clones the cocos2d repo which only contains the cocos2d core.
- the cocos2d user includes the cocos2d repo as a git submodule in his/hers projects. Different projects can hence use specific cocos2d releases.
- the user can make modifications in the cocos2d code, and maintain the modifications on branches. It's easy to push proposed modifications to the main repo. I think this will make the community more vivid.
- it's much easier to pull new releases, and to rebase possible modified branches. Users will therefore step up on new releases.
Is this the proposed work flow, or do you guys have an even better alternative?
Shall the cocos2d repo contain xcode related stuff, or shall it only contain the target code. I think only the target code.