Tools
6. July 2022 / 11. August 2023 by Karsten Reincke | Leave a Comment
After having updated to Ubuntu 22.04, I recently wanted to reactivate my music work environment. But when I installed Musescore‑3 and let it play my music score, I got an ugly mess of background noises. And I could not add any soundfont. Obviously, I faced two obstacles that I had to overcome
Read more »
Tagged
Musicology
24. April 2022 / 11. May 2024 by Karsten Reincke | Leave a Comment
Musicologists have a hard time — namely if they want to enrich their LaTeX texts by score examples and harmony analyses. Up to now, there did not exist any study of whether and how that could be realized with free software. This article summarizes a German-written self-referential tutorial teaching what’s possible and what is not […]
Compliance
26. February 2022 / 8. August 2023 by Karsten Reincke | Leave a Comment
A presentation without images sucks. Therefore, we are sometimes tempted to take some from the Internet for beautifying our work. There are so many excellent pictures on the World Wide Web. But to legally inserting a foreign picture in one’s own presentation is not that easy. Unfortunately, a new type of troll has emerged recently, […]
28. November 2020 / 8. August 2023 by Karsten Reincke | Leave a Comment
By releasing the Open Source License Compendium and the Open Source Compliance Advisor, Deutsche Telekom has supported Open Source Compliance. At BOSL‑3.0 I was one of the co-authors — on behalf of DT. But DT offers so many complex Open Source based products that it is too expensive to create the necessary Open Source compliance […]
21. August 2020 / 11. August 2023 by Karsten Reincke | Leave a Comment
In 2000, I released the Gnu Template Generation Tools, also known as gtgt. It instantiates a set of sources that 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 — in the context […]
9. August 2020 / 11. August 2023 by Karsten Reincke | 2 Comments on Atom on Ubuntu 20.04
I am a loyal soul. But my patience is limited. Ubuntu 20.04 displays the tips from Eclipse in black on black. Hmm. Markdown editors are cumbersome. Oops. And the ‘spell-check’ for German-English texts still doesn’t work. Grrr. So, it is time to conquer new frontiers: everyone is already talking about ‘Atom’. Let us give it […]
16. June 2020 / 11. August 2023 by Karsten Reincke | Leave a Comment
Today, the German Corona-Warn-App was released as Open Source Software. You may know it as CWA. The journalists mostly received it positively, even those of Spiegel and Welt. The German government wanted to release it as open-source software. That should increase the acceptance of the app by the German people. Unfortunately, there is still some […]
Compliance Musicology
29. October 2019 / 8. August 2023 by Karsten Reincke | 2 Comments on GPL-Licensed LilyPond Snippets — And Some Sideaffects
This article talks about some side effects. It explains why it is a bit suboptimal to distribute LilyPond snippets under the terms of the GPL. Even, if one loves to create, share, and/or use free and open-source software. And believe me, I do so. The side effect is simple. Including GPL-licensed LilyPond snippets enforce you […]
30. June 2019 / 8. August 2023 by Karsten Reincke | 1 Comment on YOCTO, IoT, and the GPLv3
IoT gadgets often only offer interfaces that do not allow inspecting or modifying their software. YOCTO tries to build specific software for IOT gadgets. And the GPLv3 requires that GPLv3-licensed software must be replaceable. Thus, YOCTO, IOT, and the GPLv3 are in a clinch, if YOCTO wants to be a distribution for IOT devices that […]
17. February 2019 / 8. August 2023 by Karsten Reincke | Leave a Comment
Currently, I am reviewing music software, for example, JNIZ. It allows “[…] to build and to harmonize several voices according to the rules of classical harmony.” Although it is hosted on SourceForge, the JINZ Licensing fails: The license is ‘strange’. And by this, the author finally violates the GPL. A paramount example:
