[development] Should I submit a new module?

Karen Stevenson karen at elderweb.com
Wed Jun 6 13:33:56 UTC 2007

I think something like this should really be in core because:

1) It's not really a big enough item to justify an entire module as a solution
2) It's desired/needed in nearly any setup

I submitted an issue on that a while back at http://drupal.org/node/128635. Since I didn't provide a patch it has not gotten any attention and I don't have time to create a patch right now because of my father's illness, but perhaps someone else would like to follow up on it?


----- Original Message ----
From: Michelle Cox <mcox at charter.net>
To: development at drupal.org
Sent: Tuesday, June 5, 2007 9:23:56 PM
Subject: Re: [development] Should I submit a new module?

I like the snippit idea. I don't want to install another module but a 
snippit would be nice. I currently go in the db and empty the table manually 
because I've had too many problems with keeping devel installed and only 
install it when I really need it.


On 6/5/2007 1:58:03 PM, Peter Wolanin (pwolanin at gmail.com) wrote:
> For such "mini" modules, I created a section of the snippets handbook
> a while back:
> http://drupal.org/node/70903
> To me,
> it's not worth cluttering the download page and maintaining
> something that's
> only a few lines of code.  However, they are about as
> useful as a page snippet and can provide a basis for others to
> customize.
> -Peter

More information about the development mailing list