[ 
https://issues.apache.org/jira/browse/HAWQ-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lei Chang closed HAWQ-57.
-------------------------

> Apache License v2.0 File, Notice File Added to Top Level Directory and 
> License Header added to each source file
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HAWQ-57
>                 URL: https://issues.apache.org/jira/browse/HAWQ-57
>             Project: Apache HAWQ
>          Issue Type: Task
>          Components: Core
>            Reporter: Goden Yao
>            Assignee: Lin Wen
>            Priority: Blocker
>              Labels: OSS
>             Fix For: 2.0.0-beta-incubating
>
>         Attachments: NOTICE
>
>
> *Reference*
> http://www.apache.org/dev/apply-license
> APPLYING THE LICENSE TO NEW SOFTWARE
> To apply the ALv2 to a new software distribution, include one copy of the 
> license text by copying the file:
> http://www.apache.org/licenses/LICENSE-2.0.txt
> into a file called LICENSE in the top directory of your distribution. If the 
> distribution is a jar or tar file, try to add the LICENSE file first in order 
> to place it at the top of the archive. This covers the collective licensing 
> for the distribution.
> In addition, a correct [NOTICE 
> file|http://apache.org/legal/src-headers.html#notice] MUST be included in the 
> same directory as the LICENSE file.
> Each original source document (code and documentation, but excluding the 
> LICENSE and NOTICE files) SHOULD include a [short license 
> header|http://www.apache.org/legal/src-headers.html] at the top. If the 
> distribution contains documents not covered by CLA, CCLA or Software Grant 
> (such as third-party libraries) then see the [policy 
> guide|http://www.apache.org/legal/resolved.html].
> 3rd party source file should not add the license header.
> We can use [Apache 
> Rat|http://creadur.apache.org/rat/index.html#How_Do_I_Use_Rat] for 
> verification.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to