As you can see, you can now attribute the content that goes with your open source project on Google Code.

This is a piece of news that won’t make TechMeme, but I believe it is actually a big deal (even more so than Robert Scoble blogging about blogging).

We often think of opensource projects as code. We think about the licensing of that code, and how important it is. Tell a developer GPL vs. BSD and they know the general rules.

That is great, but few projects only contain code. What about the artifacts? What about documentation, and samples in articles, and screencast movies, and protocols and formats? A good project will clearly define that area too, but the open source licenses don’t fit.

On Google Code, you can now select a content license that fits your project. A small thing, but an important one, as you yet again tell all of the users and developers of the project exactly what the rules are…. explicitly.