On Mon, May 13, 2013 at 4:10 PM, Jacob Kaplan-Moss <ja...@jacobian.org> wrote: > Hi Tom -- > > It really sucks that when I say "if you have feedback please send it > over here", you hear "I'm not listening". > > I'm sorry, but I don't have the mental bandwidth to follow 20,000 > individual tickets. It's impossible. I just fucking can't do it. > Believe me, I've tried, and failed, many times. I'm sorry I'm such a > slacker.
I don't think anyone is asking you to do this. This ticket in question wasn't lacking bandwidth from committers, it was visited many times by committers, who each time summarily dismissed the ticket - "We're not doing this because x years ago, God said thus". There was enough mental bandwidth for it to be covered 4 times over. I'm aware that I'm simplifying a complex scenario by reducing it to a single case, but this is the kind of response I've seen all over tickets, emails and so on. You're not the only person who has time constraints, each of has a choice of what we work on in our spare time. When I read these sorts of tickets, perfectly valid feature requests knocked down for precisely no reason, why should I waste my time trying to jump through these arbitrary hoops? The short answer is I don't, I work on my own projects. What I read in the OP was someone who felt in a similar situation. > > I *do* have the bandwidth to follow a single mailing list. If you want > my attention, that's how you get it. > > If you really want to help, if you really want to get a positive > outcome from this, then how about you give me a hand and follow (part > of) Trac for me? Watch some tickets, and if/when they get stalled > bring them here. Ho hum, so a lack of engagement with parts of the community is my fault is it? I have to stay current with Django to be competent at my job, which means following these mailing lists. I also benefit from Django, so I feel compelled to help out as I can, which I do by contributing to users@. When it comes to open source work, you can't compel people to work on what you want them to work on, people will work on what they want to work on. If you make it so that it is hard for them to work on it, they won't work on your project. If you look objectively at both mine and the OPs posts, ignore the bits that make you angry, maybe you will see that you're losing potential contributors. Maybe you won't, I'll go back to lurking. This is your project, so how you structure it and accept feedback is entirely under your control. You could set something up to mail developers@ iff a ticket is re-opened after being closed if you want the discussion on here and not on tickets. At the moment, you invite people to make comments on tickets and then ignore them. The problem that I thought this thread was discussing was "Why do lots of people feel there is an engagement issue". If only I had known that it was about finding mugs to do triage.. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
