In the golden age of Open Source compliance offerings, one of the key marketing argument still appears to be: “The General Public License (GPL) is sooo risky. In case of GPL infringement, you will have to release all of your code – speak your intellectual property (IP) – under the same terms. Take our license scanner as we are the best to protect you against such nightmares.”
That statement simply is not correct. But very effective if you want to sell your services. Which company wants to be forced to release its valuable IP into the public only by not following specific license terms?
His general understanding of one of the basic principles of Free Software and the GPL – reciprocity – speaks of great intellectual power. However this muddle-headed theory in total is utterly wrong but still persistent today serving as one of the main arguments to sell license compliance offerings.
Even infringing the terms of the GPL will never force you to put your own source code under the same license. Simple as that.
Sure, in the worst case you have violated a software license. In this aspect there is no difference between the GPL or any other even proprietary license. Copyright infringement claims are caused by
the actual violation of the license and
the unlicensed use of software.
You have to cope with its consequences. Legal remedies are
punitive damages and
injunction to not distribute your product any further.
Wenn man von einem Chaos Communication Congress zurückkehrt, wird man oft interessiert gefragt: Und, wie war es? Erzähl mal, um was geht es da eigentlich?
Übervoll mit Eindrücken und übermüdet trotz regelmäßigen Mate-Konsums fällt es schwer, auf Anhieb passende Worte für einen allgemein verständlichen Abriss zu finden.
Wenn auf diese Art keine Zusammenfassung möglich ist, würde man als nächstes eigentlich zum mobilen Endgeräte greifen, um zumindest die bildlichen Impressionen für sich sprechen zu lassen. Doch halt, dort wird der Grundsatz noch ernst genommen, nur Photos anzufertigen, wenn alle auf dem Bild abgebildeten Personen damit einverstanden sind. Dementsprechend leer ist die eigene Bildergalerie.
Do you plan to switch from Adobe Lightroom to a different image management and raw editor, like its free alternatives darktable or RawTherapee? One of the main challenges is to preserve your carefully created collections’ structure whilst migrating. Ideally via the file system represented by a hierarchical folder structure to be independent from whatever software you choose.
As I am currently abandoning Lightroom, I have written a Bash-script to accomplish this task:
Over time Mozilla’s Thunderbird may happen to require some maintenance in order to continue running smoothly. Symptoms could be that either you cannot find mails that are supposed to be there, mails are doubling without any reason, or deleted mails show up again in its original folder.
Note that Thunderbird must be closed (and really not running) for the next steps to be successful. You then need to navigate to your profile folder and execute the given commands at the root of this directory.
I really do not know why I did not check out Drush earlier. It is a command-line interface to comfortably maintain your Drupal-based website. Labeled by its creators as “veritable Swiss Army knife” it can virtually do any administrative tasks that you can think of. And this within a fraction of the time that you would usually spend to execute each single step via the original user interface of Drupal.
As prerequisite you should have a well setup Drupal installation. If not for example updating Drupal’s core might not work out well and even screw up your site. After installing Drush you can easily verify this by running the command drush core-requirements.
The current stable release of Drush is 8.1.12 and requires PHP 5.4.5 or later. It supports Drupal 6.X, 7.X, and 8.X.
Right in time for the WWDC 2017 and the release of Debian 9 Stretch, a quick guide on how you can enrich your Macintosh with a free operating system.
Meanwhile older hardware from Cupertino like my Macbook Pro (Late 2013) is well supported by most GNU/Linux distributions. It is not anymore a thrilling adventure to get its components working like it used to be a few years ago. They just work out of the box.
What I still find quite challenging is to choose for and set up a working boot process. My goal is to be able to easily boot GNU/Linux as well as macOS. So this is mainly what this HowTo is all about.