python - Best practice- How to team-split a django project while still allowing code reusal -

I know that it seems vague, but please explain to me - I am starting a new project, it There will be two main components: "ACME Products" (Gmail, Meebo, etc.), and "Site" (Marketing, Induced Landing Page, Marketing, Induced Craft etc.), for assistance.

will basically load stuff in the url / acme / * Uber Cool Ajke application, and all other URIs will load the goods on other sites.

Issue: The "The Site" component is out of my hands, and will be managed by a consultative team that will work with marketing, and my team and I will work perfectly on the ACME product. / P>

Question: How the Django project can be installed in this way:

• Separate release. (They may push new marketing pages and functionality without worrying about the status of our code. Probably different substations "Projects")
• Whatever Uniform-Focus-Flying Flying
• Still allow some code again.

My main concern is that the ACME product should be rock solid, and therefore it is necessary to consult a consultant site for any differentiation / code bloopers in their marketing side. Are there.

How have you managed this? any idea? Thanks!

I suspect that to reuse the code you can get between two projects , Your organizational status, headache, organizational risks, and the risks of delay which are applicable to it - when your team can not trust the other completely, because

Rock the ACME product Must be solid, and therefore there is a need to be slightly different from any mistake / code bloopers, Advisors do the site in their marketing side.

When this is the case, I sometimes release some small underlying libraries for the use of other teams in the ACME Team ... but also when it is full As long as the bloopers who can consult with a deeper obstruction, it is a code with dependence on the implementation of the library, so basically ACME can not be used for the use of consultants. After maintaining the library (ACME may think that the lack of ING IPI will be cured, but they can not deal with the other team's reuse-Bloopers.)

Need to know many specific details, it does not seem that between the deep inherent equality, the projects of two teams, at the application level, anyway (both sides Third-party stable open-source projects that provide experiment-independent functionality) can be used, so encouraging will not be consistent with the cost of reuse