By releas­ing the Open Source License Com­pendi­um and the Open Source Com­pli­ance Advi­sor, Deutsche Telekom has already sup­port­ed the task to deal with Open Source Com­pli­ance. But DT offers so many and com­plex Open Source based prod­ucts that it is too expen­sive to cre­ate the nec­es­sary Open Source com­pli­ance arti­facts man­u­al­ly. Thus, DT needs a prac­ti­cal­ly usable auto­mat­ed tool­chain. […]

In 2000, I had released the Gnu Tem­plate Gen­er­a­tion Tools that instan­ti­ate a set of sources which were read­i­ly pre­pared for being devel­oped, com­piled, and installed with the GNU ‘Autoconf/Automake’ devel­op­ment envi­ron­ment. A few years lat­er they were passed — by new lan­guages, tech­niques, and tools. But now we have revi­tal­ized gtgt for spe­cial rea­sons of open source com­pli­ance: […]

I am a loy­al soul. But my patience is lim­it­ed: On Ubun­tu 20.04, the tips from Eclipse are dis­played in black on black. Hmm. Mark­down edi­tors are cum­ber­some. Oops. And the ‘spell-check’ for Ger­man-Eng­lish texts still does­n’t work. Grrr. So, it is time to con­quer new fron­tiers: every­one is already talk­ing about ‘Atom’. Let us give it a try even if — on Ubun­tu 04/20 — we have to cir­cum­nav­i­gate some cliffs. […]

Today, the Ger­man Coro­na-Warn-App was released. It was received pos­i­tive­ly, even at Spiegel and Welt. The Ger­man gov­ern­ment want­ed it to be devel­oped as open-source soft­ware for increas­ing the accep­tance of the app by the Ger­man peo­ple. Unfor­tu­nate­ly, there is still some skep­ti­cism. Let me com­ment on some of these con­cerns: […]

There was a gap: The extra­or­di­nary and mar­velous music nota­tion soft­ware Lily­Pond could not ade­quate­ly deal with har­mo­ny analy­sis sym­bols. As a last con­se­quence, musi­col­o­gists could not real­ly use it. But the gap was closed — by harmonyli.ly. Here comes a very first intro­duc­tion […]

This arti­cle explains why it is a bit sub­op­ti­mal to dis­trib­ute Lily­Pond snip­pets under the terms of the GPL, even if one — as I do — loves to cre­ate, to share and/or to use free and open-source soft­ware. […]

IoT gad­gets often only offer inter­faces which do not allow to inspect or to mod­i­fy their soft­ware. YOCTO tries to build spe­cif­ic soft­ware of IOT gad­gets. And the GPLv3 requires that GPLv3 licensed soft­ware must be replace­able. So, we might ask, how YOCTO deals with this con­tra­dic­tion? […]

. Cur­rent­ly I am review­ing music soft­ware, as for exam­ple JNIZ. It allows “[…] to build and to har­mo­nize sev­er­al voic­es accord­ing to the rules of clas­si­cal har­mo­ny.” [1] Although it is host­ed on Source­Forge, its license is ‘strange’. And by this, the author final­ly vio­lates the GPL. A para­mount exam­ple:

For improv­ing the per­for­mance, usu­al­ly javascript libraries are com­pressed by eras­ing all blanks, line­feeds and com­ments. Hence, they do not con­tain any license texts and only very brief license infor­ma­tion. This is a prob­lem in case of open source licensed javascript libraries.