#drupal-support already has a fair share of friendly helping people. If they migrated to #drupal and #drupal-support shut down, problem solved. As I said, having both #drupal-support and #drupal-dev is a problem. #drupal should be definitively one or the other. Freenode standard would be that it's the support channel, but as long as it's one or the other I don't have a strong preference. --Larry Garfield On Wed, 1 Aug 2007 03:01:04 +0300, "Ashraf Amayreh" <mistknight@gmail.com> wrote:

I agree with Mark, why the fuss? #drupal should actually be the place where newbies go to. While the more specific and oriented channels should be the less obvious ones because they're for the seasoned developers who most likely have come to know the channels by heart.

Anyone who goes off to search for drupal help will most certainly guess that #drupal is the place for that. If it's for the sake of preventing people from entering and leaving the room immediately after seeing the message, that seems like a good enough reason. Also, what harm could possibly result in that? I mean what're the -ves? The only thing I could worry about is causing a starvation in the support channel, leaving the newbie's high and dry, so to speak. Otherwise this seems perfectly logical. #drupal for support, #drupal-dev for development, now the question of how to prevent knowledge starvation in the support channel is a different thing, the best support people are obviously the developers themselves, suggestions?

On 8/1/07, mark burdett <mfburdett@gmail.com> wrote:

...

On freenode, the big unhyphenated channels like #ubuntu, #gentoo, #debian, #rubyonrails are open to support questions. Then you have more specialized channels for developer discussion like #mysql-dev, #kde4-devel etc.

You can find a similar pattern on lists for many FOSS projects, e.g. a "project" list and "project-dev" list.

--mark

On 7/31/07, Khalid Baheyeldin <kb@2bits.com> wrote:

...

...

As I understood it was:

#drupal - development focused #drupal-support - support focused - for newbies

The problem is that #drupal is the first place newbies will think of to get support. Once they are there, they are greeted with the "support?" reply telling them to go to #drupal-support.

This can be offputting and make people feel unwelcome. They ask the first question and get a reply that amounts to : "we don't serve your type here, buzz off!" (plagiarised from Esmerel)

So, I don't see why charters can change, with development in #drupal-dev (and only development), then #drupal become community focused, has support, infra discussions, and everything else that is not development.