Which is why the confusion is cleared up. I like having two different lists, 
personally. They have similar, but quite different purposes. I don't know that 
I read the 'this is for the support list' response as snarky at all, and the 
response was still helpful. As mentioned, it's a self-policing list, and I 
appreciate that the intention is here to help. Requesting those that help and 
have set up the helping process to specifically help under what you deem as the 
best method seems counterproductive. 

I saw no problem at all with the response email, nor with the development list. 
Just my view on it. Keep up the good work, all! And thanks for all the free 
help! 

Joel 

From: development-boun...@drupal.org [mailto:development-boun...@drupal.org] On 
Behalf Of Todd Bloom
Sent: Thursday, May 10, 2012 8:12 AM
To: development@drupal.org
Subject: Re: [development] How to change user profile entries

Why even have two lists at all, then? It just seems counter productive to 
bicker about which list something should be on and just answer the question. 

I can't imagine the "archives" of this list being heavily searched for answers, 
considering how hidden the UI is. On the forums, sure, I could see directing a 
user to the right place but not here.

I feel that the more Drupal grows the more it will lose the sense of community.

I mean, seriously - the question was pretty clearly not a "how do I" question 
and something that would have needed programming to accomplish. And, even if it 
was outside of the lists scope, why give a completely snarky and unhelpful 
reply? "Development" is pretty wide open - quite frankly, the question *was* 
about development of Drupal. 

There's a difference between keeping people clear about the topics of mailing 
lists and just plain being rude. Given that Drupal.org doesn't really even know 
*what* they want these lists to be, I could see where the confusion lies.

I mean, on the mailing-lists page of drupal.org, it lists it as being for core 
developers. On the mailman page, it lists it as being for "whoever". Some 
people mention that it's for module developers.

Regards,
Todd

On May 10, 2012, at 05:26 AM, Earnie Boyd <ear...@users.sourceforge.net> wrote:
On Thu, May 10, 2012 at 5:43 AM, Todd Bloom <todd.bl...@me.com> wrote:
> Honestly, I don't get why there's a fuss about it. How much volume does this 
> list get specifically dedicated to core development, any way?
>

Did I say "core" development? No, I did not, we've succumbed to the
fact that core developers no longer visit this list. We have agreed
that this list is to be used by module developers for questions about
module development issues. The OP did not speak about development in
any way but instead about use.

> It's not like it's a high volume list. It's not like it's a big deal to 
> answer questions that someone might have even though it's not specifically 
> related to core development.
>

The support list isn't "high volume" either. But that isn't the
issue. The issue is a segregation for archive purposes. If we just
willy-nilly use the list without dedicated purpose what's the point of
having a list named development versus one named support? How will a
user seeking information know he can depend on a list named
development to discuss development issues? We self-police the list so
that we can have distinction in the purpose of the list for the
benefit of those seeking information.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

Reply via email to