On Apr 19, 10:19 am, Jacob Kaplan-Moss <ja...@jacobian.org> wrote:
> Hi folks --
>
> I'd like to try to reboot the discussion that's been going on about
> Django's development process.
>
> I'm finding the current thread incredibly demoralizing: there's a
> bunch of frustration being expressed, and I hear that, but I'm having
> trouble finding any concrete suggestions. Instead, the thread has
> devolved into just going around in circles on the same small handful
> of issues.
>
> So: here's your chance. You have suggestions about Django's
> development process? Make them. I'm listening.
>
I'm new in Django so you can just ignore my opinion but probably due
to
a fresh eye I think I see _one_ important reason why such discussions
pop up over and over again.
For the project of such exposure as Django the number of _active_ core
members that actually do work on trunk and are participating in the
decision making process is extremely small. Quick and dirty statistic
on
trunk commits shows that more than 75% of the work in _trunk_ is done
by just 4 developers [1] and from this list it seems that not much
more are
really involved into design decision making either.
At the same time the requirements for any new proposal are extremely
high. You and Russ have explained them many times on this list. in
short
it should be perfect from the core view to be included.
I'm not saying it is good or bad. No judgment at all. Just pure
observation.
These two things simply mean that for the core team it is just
_physically_
impossible to cope with the rising flow of requests/patches/bug
reports.
IMHO there are two ways out of this :
1. Share responsibility and ownership with more developers even if
their
views are not exactly match yours.
2. Just ignore such discussions, they are inevitable, unless you'll
make
this list moderated.
Regards,
Mike
[1] Number of commits and changed lines per developer for the
tr...@13001:
# #Comm % Cum% #Lines % Cum% developer
---------------------------------------------------
1. 2612 31.48 31.48 2626 17.53 17.53 adrian
2. 1814 21.86 53.34 5595 37.34 54.87 mtredinnick
3. 1026 12.37 65.71 1400 9.34 64.21 russellm
4. 818 9.86 75.57 1235 8.24 72.46 jacob
5. 335 4.04 79.61 760 5.07 77.53 gwilson
6. 202 2.43 82.04 402 2.68 80.21 hugo
7. 201 2.42 84.46 472 3.15 83.36 kmtracey
8. 186 2.24 86.71 779 5.20 88.56 lukeplant
9. 185 2.23 88.94 285 1.90 90.46 ubernostrum
10. 183 2.21 91.14 398 2.66 93.12 jbronn
11. 170 2.05 93.19 183 1.22 94.34 jezdez
12. 144 1.74 94.93 209 1.39 95.74 brosner
13. 73 0.88 95.81 99 0.66 96.40 telenieko
14. 68 0.82 96.63 94 0.63 97.02 ikelly
15. 67 0.81 97.43 79 0.53 97.55 jkocherhans
16. 44 0.53 97.96 75 0.50 98.05 wilson
17. 39 0.47 98.43 78 0.52 98.57 zgoda
18. 34 0.41 98.84 64 0.43 99.00 mboersma
19. 32 0.39 99.23 60 0.40 99.40 tekNico
20. 25 0.30 99.53 25 0.17 99.57 simon
21. 14 0.17 99.70 24 0.16 99.73 toxik
22. 11 0.13 99.83 18 0.12 99.85 ramiro
23. 8 0.10 99.93 15 0.10 99.95 aljosa
24. 5 0.06 99.99 7 0.05 99.99 garcia_marc
25. 1 0.01 100.00 1 0.01 100.00 jtauber
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@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.
