On Thu, Nov 12, 2009 at 5:57 AM, mrts <mrts.py...@gmail.com> wrote: > > On Nov 11, 1:57 pm, Russell Keith-Magee <freakboy3...@gmail.com> > wrote: >> Also - I know you're very enthused about Git and GitHub, but Django >> uses SVN as the canonical store for trunk and branches, and this isn't >> likely to change in the near future. > > Thank you, but no, I'm not enthused about git and GitHub per > se :) -- I'm enthused that it's possible to maintain patches > and collaborate remotely with less agony by utilizing them. > > Please let's be friendly and relaxed -- I was just asking > how do people plan to manage things. SVN is fine as well, > but it puts the burden of integrating work on core. It's > not the tool, but the goal that matters.
SVN is a sucky tool, but it really isn't the bottleneck in the process. The bottleneck is deciding which one of a thousand patches I (or any other member of core) should merge into trunk next. Git (or any other DVCS for that matter) doesn't solve that problem. No tool will - it's a social problem, and there's no such thing as a technical solution to a social problem. >> As I have said to you in the past - if you want to make your >> contribution to Django to be a DVCS repository that acts as a staging >> area for trunk-ready patches, that would be a very helpful >> contribution. This is doubly true during a sprint - sprints generate a >> lot of activity, so having good lieutenants to triage contributions is >> extremely useful. > > Done, http://github.com/django-mq/django-mq . Awesome. I look forward to seeing your work. > I'm willing to regularly review pull requests and add > collaborators who are willing to do the same. Thats fine, but keep in mind that the value of this branch goes down if the patches that are added to the branch aren't good. The risk of adding lots of contributors is that you end up with a branch that is just every ticket in Trac applied to trunk. What we need is a genuine lieutenant - someone who exercises personal taste and rejects patches when appropriate. A good lieutenant should also give feedback to the original developer. What we don't need is someone who just applies every patch they can. Applying a patch to a tree is easy. Working out whether a patch is a good contribution is hard. > But there's the problem that I'm not Andy Morton -- > considering my karma, I'm in no position in regard > to my "social capital" to lieutenant this. But neither was Andy Morton when he started. That's the point. You don't do this sort of thing *because* you have the karma - you do it to *gain* the sort of karma that Andy Morton has. Through a lot of hard work, Andy built a reputation as being someone with good design taste that Linus can rely on as a rich vein of probably-trunk-ready patches, and as a result, he is now a trusted lieutenant. 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 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 -~----------~----~----~----~------~----~------~--~---
