Language Selection

English French German Italian Portuguese Spanish

Four Considerations When Using Open Source in Production

Filed under
OSS

Most IT staff and developers have no problem technically evaluating open source software. However, they often overlook other considerations that could mean success or failure of a production system.

Here are some of the top non-technical issues you should consider for any open source that will be running in your production environment.

1. Understand ALL the licenses

Most people realize that they need to understand "the license" associated with a piece of open source software, but most people don't realize there's often more than one license associated with individual open source packages.

Open source packages often bundle other open source components, which may have different licenses. There are also many cases where a package includes specific files or pieces of code under different licenses. You need to find, review, and follow ALL of those bundled licenses. For example, if a project is licensed under the Apache License but includes other open source code provided under a GPL license, you must comply with each of those licenses for the relevant portion of the software.

2. Vet the project and community




More in Tux Machines

Android Leftovers

Raspberry Pi 101 – An Introduction to the Raspberry Pi GPIO

An important feature of the Raspberry Pi is the row of GPIO pins, where GPIO stands for general purpose input/output. It will allow us to communicate between Pi and the outside world. We have 40pins on Pi, we count these pins from left to right out of which seventeen pins are GPIO pins. Different pins are used for the different functions and can be connected to a number of external peripherals such as buttons, lights, relays, sensors, etc. Read more

Intel Pentium vs. AMD Ryzen 3 Performance For Linux Gaming

For those that may be looking to assemble a new low-end Linux gaming system in early 2018, here is a look at the Linux gaming performance of an Intel Pentium (Kabylake) processor to an AMD Ryzen 3 while testing with the GeForce GTX 1050 and Radeon RX 560 graphics cards. Read more

Containers, the GPL, and copyleft: No reason for concern

Though open source is thoroughly mainstream, new software technologies and old technologies that get newly popularized sometimes inspire hand-wringing about open source licenses. Most often the concern is about the GNU General Public License (GPL), and specifically the scope of its copyleft requirement, which is often described (somewhat misleadingly) as the GPL’s derivative work issue. One imperfect way of framing the question is whether GPL-licensed code, when combined in some sense with proprietary code, forms a single modified work such that the proprietary code could be interpreted as being subject to the terms of the GPL. While we haven’t yet seen much of that concern directed to Linux containers, we expect more questions to be raised as adoption of containers continues to grow. But it’s fairly straightforward to show that containers do not raise new or concerning GPL scope issues. Read more