-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License potential issue #17
Comments
Well that would only apply to the README.md file, since that's the file
that has the notice, now wouldn't it?
I have filters generate the open source version from the proprietary
version.
Obviously not all the bug are worked out of them.
…On Saturday, March 23, 2019, Alessandro DE LAURENZIS < ***@***.***> wrote:
Hello,
there is an on-going effort to import OpenSTA in the OpenBSD port tree.
Currently the main concern is related to the software license; even if it
seems clear from all file headers that you are using the GPLv3, the
"License" paragraph in README.md is confusing:
Copyright (c) 2019, Parallax Software, Inc. All rights reserved.
No part of this document may be copied, transmitted or disclosed in any
form or fashion without the express written consent of Parallax Software,
Inc.
Could you please clarify? Does your software integrally adhere to the GPL?
Thanks and regards
--
Alessandro
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#17>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AhI8lWVryqCA_3yAXilFZFIPQp-Wo2WAks5vZd3vgaJpZM4cEx1X>
.
|
Hello James,
Well, README.md makes part of the distribution tarball and that notice would prevent to put the distfile on public FTP mirrors. Anyway, I see that with commit 20ab0a1 you amended the copyright for both README.md and seach/Genclks.hh (the only other file that had a similar problem), thanks for that. I think you can close this ticket. Regards -- |
Hello,
there is an on-going effort to import OpenSTA in the OpenBSD port tree. Currently the main concern is related to the software license; even if it seems clear from all file headers that you are using the GPLv3, the "License" paragraph in README.md is confusing:
Could you please clarify? Does your software integrally adhere to the GPL?
Thanks and regards
--
Alessandro
The text was updated successfully, but these errors were encountered: