[SOLVED] Lisence for open source Qt application?

mcosta

Hi,

Why you don't want publish your code?
The power of OpenSource is to allow other people to improove and extend your code.
Also you can publish your code on sourceforge/gitorious/github and so on and ask for help for translating/porting on Windows

koleygr

I am an ubuntu user...
and i chosed ubuntu for their open source philosophy...

I want to publish my code and i will do it anyway...

I am just a little bit confused with the licences just because i want
to finish my code before someone take the idea and make a better
program than mine... and sell it instead of offering it as an open source

mcosta

If someone modify your code, he can't "sell" it.
Once a Program was created with GPL/LGPL license, no one can change license, only you can.

Little tip. You'll never finish your code
This means that a program can be forever upgradable

koleygr

Thank you very much @mcosta...

I will finally use the GNU GPLv3...

I know no one can change the license of my program,
i just worry of making his own program on my idea
before my alpha is ready... and sure, this way he could sell it.

But it is not a big deal... my program will be finished soon,
and it will be an open source, so i am not afraid,
because open source always are better ;)

Thank you, its SOLVED
Kostis

goblincoding

[quote author="mcosta" date="1367575224"]Little tip. You'll never finish your code
This means that a program can be forever upgradable[/quote]

Isn't that the truth! :D

minds

[quote author="mcosta" date="1367575224"]
Little tip. You'll never finish your code
This means that a program can be forever upgradable

[/quote]

Not always the case. Only some programs.

Anyways, I think it would be better if you read the contents of the GNU GPLv3. You might be mistaken of some things.

ceora

hi i have a similar problem to your:
I'm using visual studio express edition and windows SDK compiler
I'm using an external library with it'own license
I'm using Qt creator as developing environment
'm using Also the Qt libraries 4.8.5 non commercial

So each "tool", i think impose it's own licenses so at the end what i've should do? I want to release my software opensource and free( i think GPLv3 is the right license), i have to include each license in the package?? how i know if some licenses are in contrast. and what about copyright, i have to register the software somewhere to get copyright notice???

Thanks

sierdzio

ceora it's all really rather simple. Visual Studio and Qt Creator are just code editors: they don't impose any licensing on you, ever. I'm not sure about SDK compiler, but it should not cause any problems here, either.

For Qt (since you don't have the commercial license) your options are: LGPL or GPL. If you choose GPL, your code is required to be GPL, too. If you choose LGPL, your code can have any license (including proprietary, commercial EULAs). In all cases, you need to include the license for Qt with your code - so that users can read about their rights.

[quote]I’m using an external library with it’own license[/quote]

Everything now relies on that single library. What is it's license?

ceora

Hi thanks for the fast answer!!!

this is the license shipped with the source:

bq. Open Asset Import Library (assimp)

Redistribution and use of this software in source and binary forms,
with or without modification, are permitted provided that the
following conditions are met:

Redistributions of source code must retain the above
copyright notice, this list of conditions and the
following disclaimer.
Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other
materials provided with the distribution.
Neither the name of the assimp team, nor the names of its
contributors may be used to endorse or promote products
derived from this software without specific prior
written permission of the assimp team.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

AN EXCEPTION applies to all files in the ./test/models-nonbsd folder.
These are 3d models for testing purposes, from various free sources
on the internet. They are - unless otherwise stated - copyright of
their respective creators, which may impose additional requirements
on the use of their work. For any of these models, see
<model-name>.source.txt for more legal information. Contact us if you
are a copyright holder and believe that we credited you inproperly or
if you don't want your files to appear in the repository.

Poly2Tri Copyright (c) 2009-2010, Poly2Tri Contributors
http://code.google.com/p/poly2tri/

Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
Neither the name of Poly2Tri nor the names of its contributors may be
used to endorse or promote products derived from this software without specific
prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

sierdzio

Looks BSD-ish, and definitely Open. As far as my limited knowledge says, you can use this safely in your app. Happy coding :)

ceora

Really thanks!!