Somehow it seemed like a perfect post for today, don't you agree?
Happy Halloween!
But the experience of browsing entries on that list feels more blog-aware to me, precisely because I won't necessary have the all-the-news-that-fits experience that the 100 might give. I don't need to know -- not for work, not as a person -- what the amorphous "everyone" is talking about. I want to hear what people I respect are thinking, and I want to find more people who challenge or amuse or infuriate me. I think my personal blog intake is richer with less Michelle Malkin and more Andrew Kantor and Matthew Caverhill, or more Joe Bageant and fewer Gothamist clones if you prefer -- and as for my own blog, I'd rather be original than encyclopedic.
By Bram Moolenaar, Software Engineer
We've heard from a number of site owners who want to make sure their public source code is searchable via Google Code Search. To help with that, we extended the Sitemap Protocol to support code files. This makes it possible to specify all the code files on your site, as well as the programming language and software license for each file.
To get started, check out the new Code Search tags for Sitemaps. For complete software packages that are archives (.tar, .tar.gz, .tar.bz2, or .zip), you can create a packagemap file to describe all the individual code files in each package. For example:
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:codesearch="http://www.google.com/codesearch/schemas/sitemap/1.0">
<url>
<loc>http://example.com/download/myfile.c</loc>
<codesearch:codesearch>
<codesearch:filetype>C</codesearch:filetype>
<codesearch:license>LGPL</codesearch:license>
</codesearch:codesearch>
</url>
<url>
<loc>http://example.com/download/myproject.tgz</loc>
<codesearch:codesearch>
<codesearch:filetype>archive</codesearch:filetype>
<codesearch:license>Apache</codesearch:license>
<codesearch:packagemap>packagemap.xml</codesearch:packagemap>
</codesearch:codesearch>
</url>
</urlset>
Once you've created your Sitemap, post it to a public URL on your site and then be sure to submit it through Google Webmaster Tools.
We hope this effort will help make even more code accessible and useful for developers. Let us know what you think. There's still a lot more code out there, so we'll keep working on improving Google Code Search as a tool for finding it.
First, the kids will vote on their favorite and least favorite playgrounds in the park. Then they will collect data on a variety of metrics: number of swings, amount of open space, shady vs. sunny areas, etc. Then they will try to figure out the factors that make a good playground good and a bad playground bad. They will also consider the safety of each playground, and other measures.That reminds me of our next planned school holiday activity: "does the law of large numbers really work? Let's toss a coin a thousand times and see."