1 Closure Library welcomes patches/pulls for features and bugfixes.
3 For contributors inside Google, follow the instructions given here:
4 http://go/closure-contributors
6 For contributors external to Google, follow the instructions given here:
8 Notes on Contributions to Closure Library
10 Google Individual Contributor License
12 In all cases, contributors must sign a contributor license agreement,
13 either for an individual or corporation, before a patch can be
14 accepted. Please fill out the agreement for an individual or a
15 corporation, as appropriate.
17 https://developers.google.com/open-source/cla/individual
18 https://developers.google.com/open-source/cla/corporate
20 If you or your organization is not listed there already, you should
21 add an entry to the AUTHORS file as part of your patch.
23 If you plan to add a significant component or large chunk of code, it
24 is recommended to bring it up on the discussion list for a design
25 discussion before writing code.
27 If appropriate, write a unit test that demonstrates your patch. Tests are the
28 best way to ensure that future contributors do not break your code
31 To change the Closure Library source, you must submit a pull request
32 in GitHub. See the GitHub documentation here:
34 https://help.github.com/categories/63/articles
36 Closure Library developers monitor outstanding pull requests. They may
37 request changes on the pull request before accepting. They will also
38 verify that the CLA has been signed.
40 Oftentimes, the pull request will not be directly merged, but patched to
41 the internal Google codebase to verify that unit and integration tests
42 will Closure pass before submitting (and optionally make changes to
43 the patch to match style, fix text, or to make the code or comments
44 clearer). In this case, the issue associated with the pull request
45 will be closed when the patch pushed to the repository via the MOE
46 (Make Open Easy) system.
48 https://code.google.com/p/moe-java/