|author||Bob Badour <firstname.lastname@example.org>||Mon Apr 27 23:00:19 2020 +0000|
|committer||Automerger Merge Worker <email@example.com>||Mon Apr 27 23:00:19 2020 +0000|
Add license type: variety of NOTICE licenses am: 024572bc81 am: c8c1424155 am: d985e31d24 am: 789bfd6dce am: 7b0f1044ea Change-Id: I25046ab6a815f46da678debc8744917c08fe7e15
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.