Hi James,
thanks for the fast reply. Are you on IRC, I saw the django-hotclub
channel?
I totally agree that having the "external" applications inside the
same svn are a good practice, at least to speed up testing and is very
nice with the svn:external the ability to update everything on one
shot!
I was thinking about this external applications an also about the
"internal" ones, like *_app (friend_app, notices_app)... To me will be
more logic to have all of them organized in something like:
externsions (applications that I would never touch, just update from
the external places)
/emailconfirmation
/friends
/notifications
/analytics
/dbtemplates
/mailer
internals
/core
/about
/friends_app
What I am thinking is to be able to have my own internal applications,
and just modify this "folder", and at the same time being able to
update the whole "external folder". And maybe I can have my own svn
for the "internal folder", adding another svn:external to have them on
sync.
And having them in different subfolders make the organization much
clear, at least to me, but you are the owner of the project, so, what
do you think ?
BTW: I was also thinking to add some testing to the site, it's
possible ? Maybe you already have any idea, if not I will think to it.
cheers,
r.