licensing

If someone uses Drupal to build a custom "software as a service" web app (an example mght be basecamp [http://basecamphq.com/]), is there any way to prevent a competitor from getting acces to the custom code or configuration used to create it and starting a competing service?

I'd like to release a couple of themes through d.org. All my themes are built using Eric Meyer's browser reset stylesheet which is in the public domain. I'm also thinking about incorporating public domain images in my themes, such as photographs from the NASA archives. At the same time I'm aware of the restriction that only GPL'd files are allowed into the repository. What am I to do?

I want to use Drupal as a paid service for building Web sites and communities. The Drupal instances and modules would reside on my server. So basically I would be acting as an Application Service Provider. If I pursue this endeavor I will likely end up using the Drupal core, some contributed modules, and several custom modules.

Does the GLP License require me to make available any of my custom modules, configurations or patches made to Drupal?

I am not a lawyer. Item #10 of the licensing FAQ asks a particular question (my emphasis throughout):

10: Can I write a "bridge module" to interface between Drupal and another system or library?

but then goes on to answer a slightly different one (with specific regard to incompatible licences):

http://drupal.org/project/wysiwygpro

Is something like that allowed:
A) on drupal's CVS
B) at all?

I recently posted a long article on music publishing that was inspired by the various discussions we've been having in this group (from Dubs comments especially). The basic points made in case you don't want to read the whole thing:

1) Do-it-yourself Publishing