On Wed, 2008-09-10 at 16:15 -0600, Jeff Anderson wrote: > Jacob's git repo is great. Trac has at least a couple plugins that can > handle git repos. > > There are enough people who are willing to contribute to the development > of Django that it might not be a bad idea to consider moving to the > distributed model. > > I'm starting this thread to encourage healthy discussion. I forbid holy > wars and flaming. > > Has making a move to a distributed model already been discussed for > Django? The closest I've seen is Jacob announcing his git repo, and > that's about it. I haven't seen any serious discussion among core devs > about the idea.
You don't even begin to approach why this might be a good idea for Django. So, what does it gain? Right now, you can already use your distributed VCS of choice with Django and subversion. Some of us have been doing that for literally years. The only time I ever use "svn" is on the very rare times I want to alter subversion metadata properties. However, subversion is a very good lowest common denominator for everybody to use as the central repository and it makes a lot of sense to continue to have a central repo. Basically, I'm not really sure what you mean by "moving to a distributed model", since that development model is already possible. Develop whatever you like, publish it via repository. If you're working closely with other people and they're using the same, or a compatible, system, you can exchange updates with them. Eventually it goes via a committer and into subversion. So, welcome to the future. Your pony is already here. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
