SCALE: The life and times of the AGPL

So, i'm a Drupal developer working for a small newspaper publisher. I have coded a custom theme and a custom subscription module, as well as a module containing asorted hacks (changing the weight of specific article sections under certain conditions, adding publishing date and section title between the boldfaced preface and the text body, really layout stuff - but better done in a module). None of these is general enough to be usefull to others (except possibly as example code, but IMHO it's a bit too involved for that too).

I'm pretty confident that there is not opening for an SQL injection there, but the stuff is not general enough to be usefull to others. What's the point for me to share it? I file bug reports and patches to Drupal and the modules I use - but wouldn't AGPL include my local theming work?

I don't think this is FUD. Forcing web devs to distribute local modifications looks like busy work to me. Of course I'd be better off with general solutions - but my employer can't afford the investment. I am pretty confident my story is a common one.

IMHO a lot of the webb stuff, including CMS, are comparable to layout programs. But noone is yelling that Scribus should add a source code link to every produced print, right?