By releas­ing the Open Source License Com­pendi­um and the Open Source Com­pli­ance Advi­sor, Deutsche Telekom has sup­port­ed Open Source Com­pli­ance. At BOSL‑3.0 I was one of the co-authors — on behalf of DT. But DT offers so many 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. This post dis­cuss­es a new method (TDOSCA) and a new tool (OSCake) for automat­ing FOSS com­pli­ance that DT devel­ops and con­tributes under the umbrel­la of the Open Chain Project. […]

In 2000, I released the Gnu Tem­plate Gen­er­a­tion Tools, also known as gtgt. It instan­ti­ates a set of sources that 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 — in the con­text of TDOSCA — we could revive gtgt: […]

I am a loy­al soul. But my patience is lim­it­ed. Ubun­tu 20.04 dis­plays the tips from Eclipse 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 Atom on Ubun­tu 04/20 enforces us to cir­cum­nav­i­gate some cliffs. […]

Today, the Ger­man Coro­na-Warn-App was released as Open Source Soft­ware. You may know it as CWA. The jour­nal­ists most­ly received it pos­i­tive­ly, even those of Spiegel and Welt. The Ger­man gov­ern­ment want­ed to release it as open-source soft­ware. That should increase 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: […]

This arti­cle talks about some side effects. It 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 loves to cre­ate, share, and/or use free and open-source soft­ware. And believe me, I do so. The side effect is sim­ple. Includ­ing GPL-licensed Lily­Pond snip­pets enforce you to dis­trib­ute your own work under the terms of the GPL: […]

IoT gad­gets often only offer inter­faces that do not allow inspect­ing or mod­i­fy­ing their soft­ware. YOCTO tries to build spe­cif­ic soft­ware for IOT gad­gets. And the GPLv3 requires that GPLv3-licensed soft­ware must be replace­able. Thus, YOCTO, IOT, and the GPLv3 are in a clinch, if YOCTO wants to be a dis­tri­b­u­tion for IOT devices that do not come with an update inter­face. And we might ask, how YOCTO deals with this con­tra­dic­tion? […]

Cur­rent­ly, I am review­ing music soft­ware, 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.” Although it is host­ed on Source­Forge, the JINZ Licens­ing fails: The license is ‘strange’. And by this, the author final­ly vio­lates the GPL. A para­mount exam­ple: […]