On Oct 19, 4:13 pm, mrts <mrts.py...@gmail.com> wrote: > now. Maintaining your own branches on GitHub or > BitBucket off the corresponding Django SVN mirrors > is easy and effortless, so it's time to put the > grudges behind and happily fork and branch Django
It seems like the word "fork" is invested with political meaning (a "nuclear option") so I would stick with "branch". What you're suggesting is just what I did some time ago: My svn checkout is in a folder '~/projects/django/upstream' which is also a DVCS repository, and from there I create DVCS branches in sibling directories for working on specific features: ~/projects/django/logging, ~/projects/ django/app_labels etc. I periodically merge these with the upstream branch, which I keep up to date using 'svn up'. While this works well for scratching my own itches, and for experimentation, I'm not sure to what extent (if at all) it helps move the platform forwards. If I published my branches in a public repository (GitHub/Launchpad/BitBucket), and if people then started to use that code, then unless I keep all those branches (with different, independent features) updated with changes in Django trunk, and I am very responsive to users of my code in terms of suggestions for improvements etc. then all I've achieved is to create another version of the code which doesn't please people, isn't known to a lot of potential users for a variety of reasons, and perhaps becomes the basis of someone else's branch - it sounds like there's a possibility that a lot of time will be spent in merging, checking what different branches do, etc. - a DVCS version of DLL hell ;-) So, DVCSs are great for each person to maintain their own variant of Django, but less useful for sharing our variants with the rest of the community because each variant will (understandably) have tiny mindshare compared with the main project. Sometimes, that won't matter because we're in complete control of what variant of Django gets installed on a particular site. At other times, we want to take advantage of a standard Django that our customers have already got and are invested in, where there's no room for our branched Django with those must-have (in our opinion) features. Then, having our own branched version with our favourite bells and whistles will be no good to us. Am I making sense? Regards, Vinay Sajip --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
