Git Product home page Git Product logo

Comments (4)

DavidEGrayson avatar DavidEGrayson commented on June 12, 2024

It sounds like you are just asking about the source code in this repository, and not any kind of binary files.

So, to answer your question, none of the source code in this repository is licensed with the GPLv3.

If you want permissions for the code in this repository written by Pololu, can license it from us by following the terms in our license file, LICENSE.txt.

If you want permissions for the libyaml and tinyxml2 code in this repository (which we did not write), you can license it from the copyright holders for those libraries by finding the appropriate license for each library and following the terms of it. Each of those libraries comes with a license in the source code, and we have placed copies of those licenses at the top level of this repository to make the situation more clear.

You said "the permissive" in your question. Please note that there is no single license that grants permissions to all the code in this repository, since this repository holds copyrighted works from different parties.

from pololu-tic-software.

jomade avatar jomade commented on June 12, 2024

Thank you for the swift answer!

No source code is licensed with the GPLv3 - excellent.

Why is the GPLv3 included in the repository? (at least for me this is confusing...)

from pololu-tic-software.

DavidEGrayson avatar DavidEGrayson commented on June 12, 2024

You saw the sentence at the top of LICENSE_GPLv3.txt, right?

This is the license for the binary software distribution.

When we build a binary version of the Tic software, we have to use some GPL libraries, so we include that file in the LICENSE.html file that we generate for each binary version.

from pololu-tic-software.

jomade avatar jomade commented on June 12, 2024

Hi!

You saw the sentence at the top of LICENSE_GPLv3.txt, right?

No, actually, I didn't. Then I understand. Thanks!

Maybe you want to consider to rename the LICENSE_GPLv3.txt to LICENSE_binarydist_GPLv3.txt then it would be more in line with the naming convention of the other license files (i.e. LICENSE_libyaml.txt) - and/or add a section in the readme for this ...

Thanks for your help!

from pololu-tic-software.

Related Issues (9)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.