"blender-osm" licensed under GNU GPL (according Blender rules)

[ghost]

I previously got "blender-geo" (while it was in opensource state), where was only one limitation:

# This is the release version of the plugin file io_import_scene_osm_dev.py
# If you would like to make edits, make them in the file io_import_scene_osm_dev.py and other related modules
# To create the release version of io_import_scene_osm_dev.py execute:
# python plugin_builder.py io_import_scene_osm_dev.py

It had not any copyright restrictions or limitations for forking. So, how I could fork it? Under MIT or so?

[vvoovv]

It's pure technical issue, it has nothing to do with license.

All Blender addons must have GNU GPL license according to https://www.blender.org/support/faq/:
If you share or publish Python scripts – if they use the Blender API calls – have to be made available compliant to the GNU GPL as well.

[ghost]

@vvoovv, So, this mean, that ALL addons if they atleast include string import bpy must be licensed under GPL, right?

[vvoovv]

Yes, I think so.

[ghost]

Yes, I think so

@vvoovv, Why you not describe this in current "blender-osm" addon code and README files?

P.S.: on #blenderpython IRC-channel got same answer.

[vvoovv]

I forgot to include the license file. The next public release will have it.
Thanks for the reminder.

[ghost]

I forgot to include the license file. The next public release will have it. Thanks for the reminder.

Also add this licensing info into main README file.

... next public release...

According Blender FAQ, there no any private or public addons: if you use Blender API then every addon must be immediatly licensed as GNU GPL.

[vvoovv]

The addon is released under GNU GPL. The attribution will be added in the next release.

Your last statement isn't correct. If you modify software privately (without distributing it), there is no need care about licensing and to provide modifications back.

[ghost]

Your last statement isn't correct. If you modify software privately (without distributing it), there is no need care about licensing and to provide modifications back

Not true. If You use GNU GPL code (Blender API) in you own code, then you CAN'T drop GNU GPL never! (ask FSF for it)

You may use other license only if "private" work is fully scratch code, that not use any 3rd party API.

(without distributing it)

There no "distributing" term on Blender FAQ. There is "publish", in Github terminology every commits (in private or public) repositary is "publishing". So, not manipulate there.

[ghost]

@vvoovv, removing "dev" and "old" branches isn't solution: I already forked them and archived according GNU GPL.

Also this topic archived

• http://web.archive.org/web/20170104150956/https://github.com/vvoovv/blender-osm/issues/42

P.S.: maybe it would be usefull for you understand GNU GPL

• https://www.gnu.org/licenses/gpl-faq.html
• GPL License Compliance Request espressif/ESP8266_RTOS_SDK#1

[vvoovv]

Why did you archive this topic?

[ghost]

Why did you archive this topic?

For history.

• http://web.archive.org/web/20170104154736/https://github.com/vvoovv/blender-osm/issues/42
• http://archive.is/TK1wo

[vvoovv]

It will be kept in this repo anyway.

[ghost]

@vvoovv, And why you remove "dev" & "old" branches? Can't see any logic why did it...

[vvoovv]

The development is done in the repo with limited access. All customers will get full source code under GPL license.

[ghost]

All customers will get full source code under GPL license.

"... and they can modify, fork redistribute and sell it under the GNU GPL terms" must be added too!

And where this "updated" licensing info described?

• http://wiki.openstreetmap.org/wiki/Blender
• https://forum.openstreetmap.org/viewtopic.php?id=25188
• https://blenderartists.org/forum/showthread.php?334508-Addon-Import-OpenStreetMap-(-osm)
• https://github.com/vvoovv/blender-osm/blob/master/README.md

[vvoovv]

The distribution contains all necessary information about licensing according to https://www.gnu.org/licenses/gpl-howto.en.html

[ghost]

As I understand, README.md from "master" branch is part of distribution and it must include this info.

[vvoovv]

README.md is neither source file nor a part of the distribution.

[vvoovv]

Added copyright notice and copying permission statement to each source file.
Added GNU GPL text to the the distribution.
Added GNU GPL license in README.md and documentation.

[ghost]

Archived

• https://web.archive.org/web/20170111141006/https://github.com/vvoovv/blender-osm/issues/42

[ghost]

Added GNU GPL license in README.md and documentation.

@vvoovv, why are you lying? I can't see this info in README.md

• https://github.com/vvoovv/blender-osm/blob/info/README.md

[vvoovv]

Use search function of your browser for the word GPL

[ghost]

All customers will get the addon source code under GPL license!

License is GNU GPL, and you don't show what version of GNU GPL used. Also, whole project on Github must be marked as GNU GPL.

[FractalizeR]

There is no project on GitHub now as I can see. The project page now serves advertising purposes only. And this seems to violate GitHub Terms of Service: https://help.github.com/articles/github-terms-of-service/#j-advertising-on-github

GitHub Repositories

GitHub repositories are intended to host Content. You may include static images, links, and promotional text in the README documents associated with your repositories, but they must be related to the project you are hosting on GitHub.

You may not advertise in other Users' repositories, such as by posting monetized or excessive bulk content in issues.

[vvoovv]

The project hosts documentation related to the blender-osm addon.
See the documentation pages at https://github.com/vvoovv/blender-osm/wiki

No link is pointing to this github repo.
So I don't see any violation of the GitHub Terms of Service.

[andreygursky]

Also, whole project on Github must be marked as GNU GPL.

@Symbian9, marking is a nice feature to find out quickly what license is in use. But why do you insist on "must"?

There are projects with files under different licenses (and even differently licensed code pieces in a file). It is also possible to compile the same project resulting in different licenses.

[vvoovv]

Good news!
All source code is back: https://github.com/vvoovv/blender-osm/tree/release