Add license type: variety of NOTICE licenses am: 024572bc81 am: c8c1424155 am: d985e31d24 am: 789bfd6dce am: 7b0f1044ea

Change-Id: I25046ab6a815f46da678debc8744917c08fe7e15
tree: 7302b3aba66f80328131cca667660087c56825c8
  1. cpplint/
  2. docguide/
  3. include/
  4. angularjs-google-style.html
  5. cppguide.html
  6. cppguide.xml
  7. eclipse-cpp-google-style.xml
  8. eclipse-java-google-style.xml
  9. google-c-style.el
  10. google-r-style.html
  11. google_python_style.vim
  12. htmlcssguide.html
  13. htmlcssguide.xml
  14. intellij-java-google-style.xml
  15. javaguide.css
  16. javaguide.html
  17. javaguidelink.png
  18. javascriptguide.xml
  19. jsguide.html
  20. jsoncstyleguide.html
  21. jsoncstyleguide.xml
  22. jsoncstyleguide_example_01.png
  23. jsoncstyleguide_example_02.png
  25. lispguide.xml
  30. objcguide.xml
  31. OWNERS
  35. Rguide.xml
  36. shell.xml
  37. styleguide.css
  38. styleguide.xsl
  39. vimscriptfull.xml
  40. vimscriptguide.xml
  41. xmlstyle.html

Google Style Guides

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.

This project holds the C++ Style Guide, Objective-C Style Guide, Java Style Guide, Python Style Guide, R Style Guide, Shell Style Guide, HTML/CSS Style Guide, JavaScript Style Guide, AngularJS Style Guide, Common Lisp Style Guide, and Vimscript Style Guide. This project also contains cpplint, a tool to assist with style guide compliance, and google-c-style.el, an Emacs settings file for Google style.

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 for more details.

The following Google style guides live outside of this project: Go Code Review Comments and Effective Dart.