singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Moaz Reyad (JIRA)" <>
Subject [jira] [Commented] (SINGA-273) Improve license and contributions
Date Thu, 24 Nov 2016 05:25:58 GMT


Moaz Reyad commented on SINGA-273:

The LICENSE in GitHub is for the github repository contents as far as I understand. 

If you distribute other formats of the project (Debian package, wheel, Maven package, tar
file, Mac OS installer, etc.) then each release must has its own license. 

I am not sure it is correct to include one license restriction from a platform/distribution
on other platforms or distribution formats. 

Github just distribute the SINGA source code and what is not bundled in the Github SINGA repository
MUST NOT be included in the license as Apache guidelines says.

We can keep it if you like, but I suggest to revise this issue with a license expert.

> Improve license and contributions
> ---------------------------------
>                 Key: SINGA-273
>                 URL:
>             Project: Singa
>          Issue Type: Improvement
>            Reporter: Moaz Reyad
>            Priority: Minor
> The project needs a file. (see
> Also the third party licenses are mixed with the project license and this makes the project
license unclear. We may separate the third party license in the /thirdparty folder and keep
the Apache 2.0 license in the project root folder. 
> Finally, a license badge can be added to the

This message was sent by Atlassian JIRA

View raw message