On Apr 15, 8:57 pm, Kevin Howerton <kevin.hower...@gmail.com> wrote: > The level of resistance I see to change or outsider code contribution > is an enormous de-motivator for people (like me) to want to make any > contributions in the first place. Why should I contribute a patch to > your flawed architecture if I'm going to be talked down to, ridiculed, > then eventually have the patch rejected because it breaks code in some > edge-use-case?
Good luck pushing backwards incompatible patches when as we speak there are almost 400 open tickets with patches at accepted [1] and "ready for checkin" [2] stage. Under these circumstances, backwards compatibility is almost a red herring; the bigger issue IMO is the increasing pile of bug fixes and solid, backwards compatible patches languishing for months or years. A fork that encouraged and achieved a faster submit-review-accept- commit lifecycle, even with the same stability, maturity, and longevity policies, could be a breath of fresh air. George [1] http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&needs_better_patch=!1&needs_tests=!1&needs_docs=!1&has_patch=1&order=priority&stage=Accepted [2] http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&needs_better_patch=!1&needs_tests=!1&needs_docs=!1&has_patch=1&order=priority&stage=Ready+for+checkin -- 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.
