On 7/31/07, <b class="gmail_sendername">Angela Byron</b> <<a href="mailto:drupal-devel@webchick.net">drupal-devel@webchick.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A couple weeks ago, a few developers started going into #drupal-dev<br>instead of #drupal and started a campaign to get people to split off.<br>I guess the reasoning for this was because they disagreed with<br>newbies who didn't read the topic getting 'support?' in their face
<br>when they join our "official" channel. I personally think it is a<br>feature, and not a bug, that our main channel is contribution-focused<br>rather than support-focused, but that is largely irrelevant to the
<br>topic at hand.<br><br>The problem is that the people who started this 'fork' have not been<br>present in #drupal, actively taking part in support requests from<br>newbies, thus changing the 'mood' of the channel by their own words
<br>in actions. Instead, the main channel's merely been abandoned by<br>several very prominent contributors, a large portion of the<br>development community doesn't even realize there's a separate<br>channel, development discussion in general is now splintered between
<br>the channels, and newbies are still getting 'support?' in #drupal.<br><br>The climate in the 'official' channel right now is more that of a<br>ghost town of join/part messages, except for random musings about the
<br>infrastructure and, of course, 'support?'. This gives the exact<br>opposite impression to new Drupal users than the channel did before<br>the split -- a vibrant community of developers sharing issues or<br>patches to review, talking about new modules they're developing, etc.
<br><br>So please, #drupal-dev goers, either finish what you started by<br>actively working in #drupal to make it more newbie-friendly, or<br>abandon the experiment. So far, this feels like a net loss for the<br>community.
<br><br>-Angie<br></blockquote></div><br>Seems the main issue is that this "fork" was not discussed widely enough<br>in the community.<br><br>How about repurposing or a charter change of #drupal vs. #drupal-dev?
<br><br>#drupal-dev would be for purely development talk, and #drupal for everything<br>drupal (except support), including infrastructure, ...etc.<br><br>How about getting a discussion going this time on what to do?<br>--
<br><a href="http://2bits.com">2bits.com</a><br><a href="http://2bits.com">http://2bits.com</a><br>Drupal development, customization and consulting.