Closure Library welcomes patches/pulls for features and bugfixes.For contributors inside Google, follow the instructions given here:http://go/closure-contributorsFor contributors external to Google, follow the instructions given here:Notes on Contributions to Closure LibraryGoogle Individual Contributor LicenseIn all cases, contributors must sign a contributor license agreement,either for an individual or corporation, before a patch can beaccepted. Please fill out the agreement for an individual or acorporation, as appropriate.https://developers.google.com/open-source/cla/individualhttps://developers.google.com/open-source/cla/corporateIf you or your organization is not listed there already, you shouldadd an entry to the AUTHORS file as part of your patch.If you plan to add a significant component or large chunk of code, itis recommended to bring it up on the discussion list for a designdiscussion before writing code.If appropriate, write a unit test that demonstrates your patch. Tests are thebest way to ensure that future contributors do not break your codeaccidentally.To change the Closure Library source, you must submit a pull requestin GitHub. See the GitHub documentation here:https://help.github.com/categories/63/articlesClosure Library developers monitor outstanding pull requests. They mayrequest changes on the pull request before accepting. They will alsoverify that the CLA has been signed.Oftentimes, the pull request will not be directly merged, but patched tothe internal Google codebase to verify that unit and integration testswill Closure pass before submitting (and optionally make changes tothe patch to match style, fix text, or to make the code or commentsclearer). In this case, the issue associated with the pull requestwill be closed when the patch pushed to the repository via the MOE(Make Open Easy) system.https://code.google.com/p/moe-java/