I might be wrong on this, but from my view is the list primary intended for core development.
Secondly for generic topics through the entire Drupal module universe and heavy modules (think CCK, category or views).
Thirdly comes the rest, which I would personally like to see more of in the future.
Another way to choose appropriate list is to ask yourself the following questions:
1) Is it drupal.org-related?
1a) Is it the documentation?
documentation@drupal.org
1b) Otherwise it's probably
webmasters@drupal.org or
infrastructure@drupal.org
2) DrupalCon?
drupal-con@drupal.org
3) Does it involve dealing with clients or business in general?
consulting@drupal.org
4) Is your topic about theming?
themes@drupal.org
5) Is it about how to customize your site?
support@drupal.org
6) Will it result in code? Will someone else find that code useful?
development@drupal.org
7) Will it lead to discussion or an announcement touching Drupal core?
development@drupal.org
8) support@drupal.org
Once again, I'm likely to be wrong on this.
On 2/11/07, Tao Starbow <starbow@citris-uc.org> wrote:
I have been reading this dev list for 18 months now, and I am still not
100% sure what questions will get you slapped down. I particularly
wonder about questions like Carl Mc Dade just asked - ei: I am writing
code that interacts with the core modules and found an unexpected
behavior - is it a bug or intentional? I have interacted with other
open source projects in the past where they got very upset if I filed an
issue in ignorance, so I like to research before I file. Is this list
an appropriate place for that research, or is this list intended to be
only for developers working on the core?
thanks,
-tao
--
Regards,
Johan Forngren
johan@forngren.com :: http://johan.forngren.com/