+1 on devel contrib.  It still provides a lot more visibility for the project than leaving it as a regular contrib module, given devel module's install base.  And really, the type of people who are going to be playing with module weights are by and large developers.

On 5/18/07, Greg Holsclaw <Greg.Holsclaw@trouvemedia.com> wrote:

I agree that it is not really a constant use module, so it shouldn't really go in core. A more normal use case is that you turn on this module, get the module weighting correct and then turn it off again.

 

I think the devel would be a better place to incorporate this functionality.

 

From: development-bounces@drupal.org [mailto: development-bounces@drupal.org] On Behalf Of adrian rossouw
Sent: Friday, May 18, 2007 7:27 AM
To: development@drupal.org
Subject: Re: [development] New module: Module Priority

 

 

On 18 May 2007, at 2:40 PM, Wim Leers wrote:



 

I agree that it belongs in core.

 

it seems a bit hardcore for core.

 

ie: it's only useful when something goes wrong.

 

Wouldn't devel be a better place for this, with all it's diagnostic abilities.