I agree with Angie, Cameron, and Karen. Just like we have
#drupal-contribute, we could also need a clearly separated mailing list for
all topics focusing on Drupal contributions. That is, regardless of whether
core or contrib, or code or usability.
The separation in IRC has proven to be a good idea, as far as I can tell.
However, IRC is limited to instant communication and only visible for users
currently online. It's also unsuitable for larger meta discussions that
can't be squeezed into three sentences. And while d.o issues are somewhat
more suitable for discussions, they're usually focused on direct, actionable
goals targeting a concrete outcome or result. However, obviously the
biggest difference to a mailing list is that you have to know about the meta
issue on d.o in the first place, and be +1 subscribed to it in particular,
or you otherwise miss it. Due to that, I've missed a lot of highly
interesting and important discussions during the D7 dev cycle already.
I'd love to have a dedicated "contribute" list (back), focusing on arbitrary
but in-depth topics concerning Drupal contributors. And as Karen mentioned,
such a list could very well lead to much more solid Drupal core initiatives.
So a huge +1 on this direction.
sun
________________________________
From: development-boun...@drupal.org
[mailto:development-boun...@drupal.org] On Behalf Of Karen Stevenson
Sent: Friday, March 18, 2011 11:43 AM
To: development@drupal.org
Subject: Re: [development] Proposal: Move all dev support off this
list to new StackExchange site
I think we badly need a list for high-level strategic discussions.
There have been a couple suggestions about just creating a new list that
clearly has that purpose rather than trying to find a way to get this list
back to what that was. What about creating a new list called
'core-conversations'. No newbie could ever imagine that was a support list
and it is very clear what it is for. The core conversations at DrupalCon
this year were some of the best things about the conference for me and a
year-round way of having (or at least starting) those conversations would be
a great thing for Drupal. We could also use it to propose/discuss the
strategic initiatives that Dries wants to use for future development.
Karen
On Thu, Mar 17, 2011 at 9:58 PM, Angela Byron
<drupal-de...@webchick.net> wrote:
t used to be that this list was for high-level strategical
discussions around core/contrib/d.o development, active brainstorming on big
problem solving, important announcements that affected CVS (now Git) account
holders, and those sort of things. What we currently (badly) use "meta"
issues and a variety of fragmented groups on g.d.o for, was what this
development list was for at one time. Support questions were directed to the
forums or to IRC.
