Hi, I'm working on defining the structure of an application It will have quite a few apps, with few of them opensourced.
I was thinking how to make it easier for people involved into the project. In essence front-end developer should work on one repository only - that's also goes quite nicely with app portability and would also help if an idea about whitelabelling the project could come to someone's mind. Other apps will be installed via pip under the virtual environment and will be a separate repositories in git. Back-end devs then will work each one on the application back-end and on the front-end application, to provide some changes to the functionality. Basically: project - one repository front-end app - one repository apps - a repository for each one. I'd like to implement a slightly modified V.Dressen's model of the workflow - in draft explained here: https://wiki.mozilla.org/Labs/Jetpack/FlightDeck/Code_Workflow on each of the repositories Do you think it's best structure? And, quite important, will it not look like a mess for an "average" developer? Piotr -- blog http://piotr.zalewa.info jobs http://builder.mozillalabs.com, http://jsfiddle.net twit http://twitter.com/zalun -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
