|author||Igor Murashkin <email@example.com>||Thu Nov 16 00:06:06 2017 +0000|
|committer||android-build-merger <firstname.lastname@example.org>||Thu Nov 16 00:06:06 2017 +0000|
Android: Add repository import files am: b397128e82 am: 333e3bc131 am: 17eb825388 Change-Id: I2fd899fcb7d54faa11924065f466ed1f0e5550a0
Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a consistent style.
“Style” covers a lot of ground, from “use camelCase for variable names” to “never use global variables” to “never use exceptions.” This project (google/styleguide) links to the style guidelines we use for Google code. If you are modifying a project that originated at Google, you may be pointed to this page to see the style guides that apply to that project.
If your project requires that you create a new XML document format, the XML Document Format Style Guide may be helpful. In addition to actual style rules, it also contains advice on designing your own vs. adapting an existing format, on XML instance document formatting, and on elements vs. attributes.
The style guides in this project are licensed under the CC-By 3.0 License, which encourages you to share these documents. See https://creativecommons.org/licenses/by/3.0/ for more details.