You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
We have this project as a package in Debian currently
Whilst I agree that every file containing "code" has a BSD license on top of it, but due to the absence of a LICENSE file, the data and documentation becomes non-free according to the free software guideline followed here.
Could you please add in the same in a LICENSE file and commit?
That'd be great.
PS: Considering that PAML has also adopted a free software license, this can also go about doing the same w/o conflicts, I suppose.
The text was updated successfully, but these errors were encountered:
Hi,
We have this project as a package in Debian currently
Whilst I agree that every file containing "code" has a BSD license on top of it, but due to the absence of a LICENSE file, the data and documentation becomes non-free according to the free software guideline followed here.
Could you please add in the same in a LICENSE file and commit?
That'd be great.
PS: Considering that PAML has also adopted a free software license, this can also go about doing the same w/o conflicts, I suppose.
Hi,
We have this project as a package in Debian currently
Whilst I agree that every file containing "code" has a BSD license on top of it, but due to the absence of a LICENSE file, the data and documentation becomes non-free according to the free software guideline followed here.
Could you please add in the same in a LICENSE file and commit?
That'd be great.
PS: Considering that PAML has also adopted a free software license, this can also go about doing the same w/o conflicts, I suppose.
The text was updated successfully, but these errors were encountered: