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.<br>
<br>
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?<br><br><div><span class="gmail_quote">On 8/1/07, <b class="gmail_sendername">mark burdett</b> <<a href="mailto:mfburdett@gmail.com">mfburdett@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On freenode, the big unhyphenated channels like #ubuntu, #gentoo,<br>
#debian, #rubyonrails are open to support questions. Then you have<br>more specialized channels for developer discussion like #mysql-dev,<br>#kde4-devel etc.<br><br>You can find a similar pattern on lists for many FOSS projects,
e.g. a<br>"project" list and "project-dev" list.<br><br>--mark<br><br>On 7/31/07, Khalid Baheyeldin <<a href="mailto:kb@2bits.com">kb@2bits.com</a>> wrote:<br>><br>><br>> > As I understood it was:
<br>> ><br>> > #drupal - development focused<br>> > #drupal-support - support focused - for newbies<br>> ><br>><br>> The problem is that #drupal is the first place newbies will think<br>> of to get support. Once they are there, they are greeted with the
<br>> "support?" reply telling them to go to #drupal-support.<br>><br>> This can be offputting and make people feel unwelcome. They<br>> ask the first question and get a reply that amounts to : "we don't
<br>> serve your type here, buzz off!" (plagiarised from Esmerel)<br>><br>> So, I don't see why charters can change, with development<br>> in #drupal-dev (and only development), then #drupal become<br>
> community focused, has support, infra discussions, and everything<br>> else that is not development.<br>><br></blockquote></div><br>