[Savannah-register-public] [task #14426] Submission of TUServer

Update of task #14426 (project administration): Status: In Progress => Cancelled Open/Closed:Open => Closed ___ Follow-up Comment #15: Thank you;

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #14, task #14426 (project administration): Well, I think that it's a really unsolvable problem, and I have not to use Savannah to host this project. All the best, may meet you again if TUServer will become not a NodeJS package and I'll not use another hosting for it You can clos

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #13, task #14426 (project administration): We concluded that relicensing your code permissively doesn't effectively make it GPL-compatible, because it indirectly uses OpenSSL, and OpenSSL license isn't compatible with the GPL.

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #12, task #14426 (project administration): Please wait. ___ Reply to this item at: ___ Message sent via/by Savannah http://savannah.

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #11, task #14426 (project administration): Should I do anything more or just wait? ___ Reply to this item at: ___ Message sent via/by

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #10, task #14426 (project administration): FWIW, I think we should accept WTFPL and this approach to avoiding the OpenSSL compatibility. I know of nothing in our policies against it ... -k ___ Reply to this item at:

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #9, task #14426 (project administration): > GPL applies to the whole program and it doesn't matter how its parts are linked. Okay, I remembered > GNU project doesn't recommend using WTFPL I know, but I like this license, and, after some hours of thinking, I decided to relicen

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #8, task #14426 (project administration): > but, it does that by calling a MIT licensed JavaScript code that uses bindings to C++ functions (also MIT) that communicate with OpenSSL I don't think this is essential. Just imagine: I take a GPL'ed library, write a complicated wrappe

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #7, task #14426 (project administration): Well, I've found the fastest and easiest way to solve this issue. Here's a tarball - https://savannah.gnu.org/submissions_uploads/tuserver_fixed.tar.gz Just change the license field to "Other"

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #6, task #14426 (project administration): Following https://github.com/nodejs/node/wiki/OpenSSL-upgrade-process, NodeJS uses SSL for SSL features (https://nodejs.org/api/tls.html), HTTPS (https://nodejs.org/api/https.html), but also it uses SSL for crypto (https://nodejs.org/api/

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #5, task #14426 (project administration): First, I may be wrong, but I think NodeJS is not an interpreter of JavaScript, it's a library. Then, when you distribute NodeJS as a whole, OpenSSL already applies to it (with other licenses for other parts of its code), you needn't even

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #4, task #14426 (project administration): I think you are right in principle: if, when your program is being interpreted by node, no openssl code gets executed, then your license need not be compatible with openssl. however, is that really the case? i know nothing about node, bu

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #3, task #14426 (project administration): I read https://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL and now I'm a little bit confused. The second one says that the code of my program (that is interpreted by NodeJS) should be compatible with the lilbraries that the inter

[Savannah-register-public] [task #14426] Submission of TUServer

Update of task #14426 (project administration): Status:None => In Progress Assigned to:None => ineiev ___ Follow-up Comment #2: As far as I

[Savannah-register-public] [task #14426] Submission of TUServer

Follow-up Comment #1, task #14426 (project administration): Oops, I forgot to include ToberUberStobe itself to the dependencies. So ToberUberStobe - GPL3 - https://savannah.nongnu.org/projects/toberuberstobe/ ___ Reply to this item at: <

[Savannah-register-public] [task #14426] Submission of TUServer

URL: Summary: Submission of TUServer Project: Savannah Administration Submitted by: lupshenko Submitted on: Mon 27 Mar 2017 12:47:07 PM +07 Should Start On: Mon 27 Mar 2017 12:00:00 AM +07