A very long time ago, in January 2008, I wondered in the General discussion forum why "I am not receiving any updates on forum threads I participate in". I genuinely thought something was temporarily not working and I hoped it would be fixed!<br>
You can still see the responses at <a href="http://drupal.org/node/216337">http://drupal.org/node/216337</a> -- generally unhelpful ("Teh subscriptions module is being rewritten", "the few notification modules were not the most well maintained modules", "performance impact of the modules in their state") -- and ultimately closing with killes's disappointing final statement: "This is simply not implemented."<br>
<br>Since that moment - I am sorry to say - I virtually stopped contributing or asking questions in the general Drupal forums because I got the impression that "support" areas like Post installation (<a href="http://drupal.org/forum/22">http://drupal.org/forum/22</a>) or General discussion (<a href="http://drupal.org/forum/2">http://drupal.org/forum/2</a>) are simply black holes for time and effort. One of the main reason is that there are no e-mail notifications for thread updates. The other is the huge level of duplication and poor searchability. When the d.o. redesign finally took place, one of the main features I was looking for was improvement of these black hole forums and added notifications. But little has changed in that area.<br>
So, instead, I have always been trying to locate and collaborate on precise issue threads and in g.d.o. groups and threads, where there tends to be more focus and the notifications do function.<br><br>Still, I feel that the need for less categorizable questions and comments has been badly missing, so I have very much welcomed the <a href="http://drupal.stackexchange.com/">http://drupal.stackexchange.com/</a> initiative. It features notifications (naturally, that's such a simple feature!), even feeds, people can vote on helpful answers, and there are several safeguards against duplicating content. Loyal to Drupal as I am, of course it hurts me that using it means shifting some activity away from the mother d.o. domain to an external platform. Especially because the same system could easily be done in Drupal! But sorry, efficiency and general progress of the Drupal project as a whole is much more important than fighting to keep inefficient forums on the d.o. domain.<i></i><br>
So I am definitely with rfay and others who put so much good energy in trying to radically improve the general Drupal support situation.<br><br>And as for this dev list - I post extremely rarely out of respect for all the more experienced people, but I read virtually all posts and try to from them as much as I can. It is useful to have it because it offers a stream of unpredictable and therefore potentially inspiring issues. But I can also imagine simply following the new questions feed at <a href="http://drupal.stackexchange.com/feeds">http://drupal.stackexchange.com/feeds</a> instead!<br>
<br>vacilando<br clear="all"><a href="http://twitter.com/vacilandois" target="_blank"><font color="#666666">http://twitter.com/vacilandois</font></a><br>
<font size="2"><span style="color: rgb(102, 102, 102);"></span></font><br style="color: rgb(102, 102, 102);"><br>
<br><br><div class="gmail_quote">On Fri, Mar 18, 2011 at 12:17, Ronald Ashri <span dir="ltr"><<a href="mailto:ronald@istos.it">ronald@istos.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Really like Karen's suggestion - a mailing list is a simple effective<br>
way to stay in touch that most people can agree with and use.<br>
<br>
Let us strictly police it so it does not stray and with respect to<br>
David's point about contrib vs core discussions I would say let us<br>
keep it strictly core - in the exact spirit of Core Conversations -<br>
just like the Snowman likes it :-)<br>
<div><div></div><div class="h5"><br>
<br>
On Fri, Mar 18, 2011 at 11:42 AM, Karen Stevenson <<a href="mailto:karen@elderweb.com">karen@elderweb.com</a>> wrote:<br>
> I think we badly need a list for high-level strategic discussions. There<br>
> have been a couple suggestions about just creating a new list that clearly<br>
> has that purpose rather than trying to find a way to get this list back to<br>
> what that was. What about creating a new list called 'core-conversations'.<br>
> No newbie could ever imagine that was a support list and it is very clear<br>
> what it is for. The core conversations at DrupalCon this year were some of<br>
> the best things about the conference for me and a year-round way of having<br>
> (or at least starting) those conversations would be a great thing for<br>
> Drupal. We could also use it to propose/discuss the strategic initiatives<br>
> that Dries wants to use for future development.<br>
><br>
> Karen<br>
><br>
> On Thu, Mar 17, 2011 at 9:58 PM, Angela Byron <<a href="mailto:drupal-devel@webchick.net">drupal-devel@webchick.net</a>><br>
> wrote:<br>
>><br>
>> t used to be that this list was for high-level strategical discussions<br>
>> around core/contrib/d.o development, active brainstorming on big problem<br>
>> solving, important announcements that affected CVS (now Git) account<br>
>> holders, and those sort of things. What we currently (badly) use "meta"<br>
>> issues and a variety of fragmented groups on g.d.o for, was what this<br>
>> development list was for at one time. Support questions were directed to the<br>
>> forums or to IRC.<br>
>><br>
><br>
</div></div></blockquote></div><br>