MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

Seo Master present to you: By Michael Kerrisk, Software Engineering Team

As you may know,Google allows its engineers to spend 20% of their time on projects independent of their regular day to day job. For my 20% time, I chose to continue and expand my work on maintaining the Linux man-pages.

Since April, we've managed to ship 21 new releases, with a dozen or so new pages, and around 400 major and minor improvements to existing pages.

My work on the Linux Man-pages project man-pages led me to talk about kernel-userland interface design, testing, and documentation at the recent LinuxConf Europe, where my Zurich colleague Roman Marxer also spoke about Google's recently open-sourced Ganeti virtual server management software.

I was lucky enough to be invited to the immediately following USENIX Linux Kernel Developers Summit, where I joined Google colleagues Andrew Morton, Paul Menage, and Martin Bligh to participate in the discussion of current topics related to kernel development, including the topic of kernel-userland API design, testing, and documentation.

You can read my talk, and in-depth coverage of the Kernel Developer Summit at LWN.net. It's available to LWN.net subscribers only until the 20th of September, but you can already see the obligatory group photo.



Googlers Andrew Morton and Paul Menage relaxing at the end of the Linux Kernel Summit, Cambridge, England

(photo credit: Michael Kerrisk)

Ed. note: Post updated to fix typo.2013, By: Seo Master

Seo Master present to you: By Ashleigh Rentz, Developer Programs team

Since 2006, we’ve believed in freely licensing our developer documentation. We believe this is best for all of us, both Google and the developer community. We most often rely on the Creative Commons Attribution 3.0 license for documentation and the Apache 2.0 license for code samples.

The freedom to reuse code samples encourages the wider adoption of our APIs and spares you from having to reinvent the wheel when you begin using our products. The freedom to create derivative works from our documentation is beneficial to book authors, bloggers, and even non-English speakers when members of the developer community translate our docs into additional languages. It’s a winning situation for all of us!

During the intervening years, however, some docs were not explicitly licensed in this manner. We wanted to bring them in line with this practice, so we embarked on a review of all our documentation on developers.google.com this week and made sure they all have a footer displaying the license they’re subject to. The vast majority of our docs are now available under liberal terms that we hope will spur new innovation in the community. In the rare cases where a doc isn’t being freely licensed for some reason, we now clearly display “All rights reserved” so you aren’t left wondering. We’ve also tweaked our internal process for publishing new documentation so that pages yet to be written will display a license footer when they’re released. Here’s to the sharing of knowledge!


Ashleigh Rentz supports the team of technical writers who tirelessly document Google’s developer products. She can often be seen skating down the hallways between meetings.

Posted by Scott Knaster, Editor

2013, By: Seo Master