Illustrating Open-Source Posts

I love ZEN-presentations, especially when they deal with open-source software. To create such files, we need pictures. Many pictures. That’s why I keep stumbling over the question of whether the FOSS licenses also allow us to use icons and logos in the same way as the code? Moreover: Under which conditions may we illustrate our articles with ‘internet-pictures‘ ? I’ve always wanted to make that clear to myself → …

INSPECTION of 2020-12-31 about Compliance, FOSS, Open Source etc. with 1 comment

TDOSCA & OSCake: Automating FOSS Compliance

By releasing the Open Source License Compendium and the Open Source Compliance Advisor, Deutsche Telekom has already supported the task to deal with Open Source Compliance. But DT offers so many and complex Open Source based products that it is too expensive to create the necessary Open Source compliance artifacts manually. Thus, DT needs a practically usable automated toolchain. → …

REPORT of 2020-11-28 about Compliance, FOSS, Tooling etc. with 0 comments

gtgt Or The Life After

In 2000, I had released the Gnu Template Generation Tools that instantiate a set of sources which were readily prepared for being developed, compiled, and installed with the GNU ‘Autoconf/Automake’ development environment. A few years later they were passed – by new languages, techniques, and tools. But now we have revitalized gtgt for special reasons of open source compliance: → …

REPORT of 2020-08-21 about Compliance, FOSS, Open Source, Tooling etc. with 0 comments

LilyPond, LilyPond Snippets and the GPL: About some bad side effects.

This article explains why it is a bit suboptimal to distribute LilyPond snippets under the terms of the GPL, even if one – as I do – loves to create, to share and/or to use free and open-source software. → …

INSPECTION of 2019-10-29 about Compliance, Musictools, Open Source etc. with 2 comments

YOCTO, IoT, and the GPLv3

IoT gadgets often only offer interfaces which do not allow to inspect or to modify their software. YOCTO tries to build specific software of IOT gadgets. And the GPLv3 requires that GPLv3 licensed software must be replaceable. So, we might ask, how YOCTO deals with this contradiction? → …

INSPECTION of 2019-06-30 about Compliance, FOSS, Open Source etc. with 0 comments

JNIZ – or how a licensing fails

. Currently I am reviewing music software, as for example JNIZ. It allows “[…] to build and to harmonize several voices according to the rules of classical harmony.” [1] Although it is hosted on SourceForge, its license is ‘strange’. And by this, the author finally violates the GPL. A paramount example: → …

INSPECTION of 2019-02-17 about Compliance, FOSS, Licensing, Open Source etc. with 0 comments

The Problem of Compliance for Javascript Libraries

For improving the performance, usually javascript libraries are compressed by erasing all blanks, linefeeds and comments. Hence, they do not contain any license texts and only very brief license information. This is a problem in case of open source licensed javascript libraries. → …

INSPECTION of 2018-05-19 about Compliance, Javascript, Open Source etc. with 0 comments