It's much clear now. Everyone seems to agree the second solution is better.
I've been searching at the same time for the svn, and I've found that no one does it the same way. But's also true an important number of the projects are still in pre-magic state. In the mean time I've also found 'Do's and dont's for application writers': http://code.djangoproject.com/wiki/DosAndDontsForApplicationWriters They say "To avoid clashes, use a name for the project which is unique to you, the author, such as one based on a domain name that you own." >From an svn point of view, wold you then do something like this? ibofobi/ apps/ mnemosyne/ branches/ tags/ trunk/ and force contributors to checkout to a directory ibofobi/apps/mnemosyne? Or should this be part of the settings.py somehow as a variable? Thanks a lot, I fid those organization questions are non-trivial for me. G On 7/31/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > > On 31-Jul-06, at 1:45 AM, Guillermo Fernandez Castellanos wrote: > > > Or more like: > > /site1/templates > > /media > > /urls.py > > /site2/templates > > /media > > /urls.p > > this makes sense to me, with common stuff somewhere else central > > -- > > regards > kg > http://lawgon.livejournal.com > http://nrcfosshelpline.in/web/ > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
