On 6/8/07, Ben Ford <[EMAIL PROTECTED]> wrote: > Russ, > > Can I suggest doing it the other way round in this case. I believe that the > multiple-db-support branch has only a small user base and I haven't had time > to properly test all aspects of the merge, I think it might make it easier > for others to test if they can just svn up. There are some aspects of the > branch that still need work and I think that most people who are using it > recognize this. Also as Carole has expressed an interest in contributing and > also SVK, it would be beneficial to her (and any others) to be able to grab > a local copy of the branch which she can keep in source control as she adds > bits to it.
I appreciate your enthusiasm, and I understand the desire to have a SVN checkout. However, we (the core devs) need to set a minimal set of requirements before we hand out SVN logins. We have, in the past, given out branch logins to anyone that wanted them. This has, almost without exception, lead to stale branches as the developer involved loses interest, etc. A stale branch is worse than no branch at all, because it raises false expectations, and doesn't reflect well on Django as a whole. We also have the problem of making sure that the job is going to be done properly. The ultimate goal will be to merge the branch back into trunk. However, this isn't going to happen if the branch doesn't meet Django's coding standard. I'm not just talking about indentation and spacing here - I mean the technical quality of the code. Prove to us you can do the work, and that you're not going to lose interest, and we'll get you a checkout. In the interim, patch -p0 < mychanges.diff isn't that hard to do; and I would suggest that the people that can't work out how to use patch probably won't be able to make a very big contribution to debugging the branch, either. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
