It's both (which is to say, it's about HCI). People would be more eager to use whatever license embedding mechanism we agreed upon if it was as easy as right click -> "License as..." -> "Creative Commons Attribution-ShareAlike 3.0". That is not the case right now.
> That solves the license input but doesn't make anyone more likely to check the license at go-live time.
My point is exactly that you shouldn't have to. If all your license information sat in the files themselves checking licensing would be accomplished by adding a few standard lines to your deployment script.
If your website used Creative Commons-licensed media your CMS would even be able to generate attribution data to be shown at the bottom of the pages that use that media on its own resulting in fully automated compliance.
