Created
December 21, 2009 18:08
-
-
Save ericholscher/261117 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
From http://groups.google.com/group/django-developers/msg/7236b842d53fb58a | |
Let me tell you a store about three people named Everybody, Anybody, | |
Somebody and Nobody. | |
There was a job to be done. Everybody agreed it should be done. | |
Anybody could have done it. Somebody should have done it. Nobody | |
actually did it. :-) | |
An mm-style tree could certainly be a useful resource for the core. | |
Merging trunk-ready patches from a git/hg mm-branch would certainly be | |
easier than doing the Trac patch dance. | |
However: | |
1) Someone actually needs to maintain the tree. Don't underestimate | |
the time required to do this - it will be just as time-consuming as | |
maintaining the trunk, and the core can't compel anyone to do | |
anything. | |
2) Someone needs to keep maintaining the tree over a long period of | |
time. It's not much help if the mm-tree exists for a week of | |
enthusiasm, then dies out. | |
3) The Someone in question needs to have the right skills and taste. | |
It's no good having an mm-tree that integrates patches that the core | |
consistently rejects. | |
4) I can almost guarantee you that if Someone actually met the first | |
three criteria, they would be given the commit bit. | |
It's no good saying "someone should". Someone actually needs to do it. | |
If you want to do it, go right ahead. | |
Again - build it and they will come. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment