On Sat, Aug 14, 2010 at 1:39 PM, burc...@gmail.com <burc...@gmail.com> wrote:
> I had few useful thoughts about changing the way Django development
> contributions gets accepted and committed -- but all I get from this
> mailing list that all attempts to improve any process is just a waste
> of time.

That's not entirely fair.

We're acutely aware of the fact that there is a backlog of tickets
that need attention. We're also aware that many people upload patches,
but then don't get any feedback on them. We want to improve this in
any way we can.

If you have suggestions on how we can improve Django's development
process and address these issues, we're happy to hear them.

However, that doesn't mean we're going to immediately implement a
suggestion just because it's been made. I don't know which suggestion
in particular you're referring to, but if you've made a suggestion and
we haven't acted on it, then I would suggest to you that this is
because we (the core team) didn't agree that your idea was as useful
or practical as you think it was.

If you have a suggestion, please make it. We're listening.

> Core devs have no time even to accept working & looking good
> patches -- and rarely have time to review patches not looking good or
> working wrong!
> So why should I bother to write patches fast?

I would point out that the core team aren't the only people that can
give feedback. Trac is an open resource for exactly that reason.

>>> I can do all development changes for all suite (and finish this patch
>>> of course), if we discuss how it should be done.
>>>
>>> My issue needs few improvements:
>>>  - docs & tests
>>
>> AFAIK the current debug page has no docs and tests, too.
> At least we need tests for color choosing based on packages paths --
> this can be customized by yourself.

As I commented the last time this ticket was discussed -- no tests or
docs are required for this proposal. It's a difficult feature to test,
and there's no user-facing configuration items, so I'm happy to accept
this ticket without tests or docs.

However, it does need to have it's UX issues sorted out. The most
recent substantive comment on the ticket [1] indicates that the patch
isn't ready for checkin. It also suggests that there are broader
improvements that may need consideration. To the best of my knowledge,
nobody has tried to start a django-dev discussion to address those
improvements.

[1] http://code.djangoproject.com/ticket/11834#comment:5

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-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.

Reply via email to