[incubator-pulsar] branch master updated: [documentation] Add section about licensing at contribution guide (#2511)

[si...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-pulsar.git


The following commit(s) were added to refs/heads/master by this push:
     new 3e9a445  [documentation] Add section about licensing at contribution guide (#2511)
3e9a445 is described below

commit 3e9a445e9ced577c1e494875e9a490c3dee9a5ab
Author: Sijie Guo <gu...@gmail.com>
AuthorDate: Sun Sep 9 16:51:03 2018 -0700

    [documentation] Add section about licensing at contribution guide (#2511)
---
 site2/website/contributing.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/site2/website/contributing.md b/site2/website/contributing.md
index 9552244..310045a 100644
--- a/site2/website/contributing.md
+++ b/site2/website/contributing.md
@@ -181,6 +181,15 @@ Then you can push your local, committed changes to your (forked) repository on G
 
 All code should have appropriate unit testing coverage. New code should have new tests in the same contribution. Bug fixes should include a regression test to prevent the issue from reoccurring.
 
+### Licensing
+
+All code contributed to Pulsar will be licensed under [Apache License V2](https://www.apache.org/licenses/LICENSE-2.0). You need to ensure every new files you are adding have the right
+license header. You can add license header to your files by running following command:
+
+```shell
+$ mvn license:format
+```
+
 ### Develop C++/Python Client
 
 Currently C++ and Python client are developed under `pulsar-client-cpp` directory. You can use following commands to build and test your c++ or python code changes.