[ 
https://issues.apache.org/jira/browse/SENSSOFT-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474511#comment-15474511
 ] 

Lewis John McGibbney commented on SENSSOFT-66:
----------------------------------------------

bq. The license headers will be included in the next release for UserALE.pyqt5

Great

bq. If I pulled example code from other sources and it included their own 
licenses, should we still include the apache license?

Accounting for this scenario is done within a NOTICE file.
Details which cover background and a couple of examples can be found at 
http://www.apache.org/dev/licensing-howto.html

If you have specific situation(s) then let me know here and we can work through 
them. Thanks

> Add ALv2.0 License Headers to UserALE.pyqt5
> -------------------------------------------
>
>                 Key: SENSSOFT-66
>                 URL: https://issues.apache.org/jira/browse/SENSSOFT-66
>             Project: SensSoft
>          Issue Type: Sub-task
>          Components: UserALE.pyqt
>            Reporter: Lewis John McGibbney
>            Assignee: Michelle Beard
>            Priority: Blocker
>             Fix For: 0.1.5
>
>
> {code}
> Licensed to the Apache Software Foundation (ASF) under one or more
> contributor license agreements.  See the NOTICE file distributed with
> this work for additional information regarding copyright ownership.
> The ASF licenses this file to You under the Apache License, Version 2.0
> (the "License"); you may not use this file except in compliance with
> the License.  You may obtain a copy of the License at
>   http://www.apache.org/licenses/LICENSE-2.0
> Unless required by applicable law or agreed to in writing, software
> distributed under the License is distributed on an "AS IS" BASIS,
> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> See the License for the specific language governing permissions and
> limitations under the License.
> {code}



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

Reply via email to