Language Selection

English French German Italian Portuguese Spanish

Richard Stallman on "World Domination 201"

Filed under
OSS

The "World Domination 201" made an impact on some parts of the Free Software community, including myself as I found myself in agreement. However, as I believe in Free Software and hence tend to prioritize the issue of freedom I was interesting in hearing what Richard Stallman, the head of the FSF, has to say about it. So I fired up the following email.

What if FSF, or maybe some other entity representing the Free Software community would sign a contract with a certain GNU/Linux distro provider which would let that distro provider temporarily include non-free software, but only if they work on replacing this non-free software with Free Software and do it within a time of two years (for example). And if they fail to do this in two years the contract would require them to remove non-free software anyway and replace it with whatever they can come up with in the meantime.

If some distro maker wants to do this, he can make a public commitment
such that failure to follow through would be embarrassing. Making it
a contract with the FSF would not really help. We would be in a
contradictory position if we endorsed the initial inclusion of the
non-free software.

Full Story.


Also:

Richard Stallman, the guru of free software, has taken a deliberate stance to favour and support in all ways possible the use of free software also when it comes to publishing his video interviews.

In other words, Stallman wants YouTube or other video sharing sites not to publish video clips of his interviews or lectures as these video distribution services do not utilize video software and file formats that adhere to the Free Software Foundation principles.

No More Stallman On YouTube? Open-Source Evangelist Says No To The Use Of Proprietary Video Formats

More in Tux Machines

today's howtos

Security Leftovers

  • Java and Python FTP attacks can punch holes through firewalls
    The Java and Python runtimes fail to properly validate FTP URLs, which can potentially allow attackers to punch holes through firewalls to access local networks. On Saturday, security researcher Alexander Klink disclosed an interesting attack where exploiting an XXE (XML External Entity) vulnerability in a Java application can be used to send emails.
  • Microsoft: no plans to patch known bugs before March [Ed: Microsoft is keeping open 'back doors' that are publicly known about, not just secret ones]
    Microsoft has no plans to issue updates for two vulnerabilities, one a zero-day and the other being one publicised by Google, before the scheduled date for its next round of updates rolls around in March. The company did not issue any updates in February, even though it had been scheduled to switch to a new system from this month onwards. It gave no reason for this, apart from saying: "This month, we discovered a last minute issue that could impact some customers and was not resolved in time for our planned updates today. "After considering all options, we made the decision to delay this month’s updates. We apologise for any inconvenience caused by this change to the existing plan." The Google-disclosed bug was made public last week, and is said to be a flaw in the Windows graphic device interface library that can be exploited both locally and remotely to read the contents of a user's memory.
  • Microsoft issues critical security patches, but leaves zero-day flaws at risk
    Microsoft has patched "critical" security vulnerabilities in its browsers, but has left at least two zero-day flaws with public exploit code. The software giant released numerous patches late on Tuesday to fix flaws in Adobe Flash for customers using Internet Explorer on Windows 8.1 and later, as well as Edge for Windows 10.

Red Hat News

  • Why upstream contributions matter when developing open source NFV solutions.
    When software is developed using open source methods, an upstream repository of the code is accessible to all members of the project. Members contribute to the code, test it, write documentation and can create a solution from that code to use or distribute under license. If an organization follows the main stream or branch of the upstream code their solution will receive all the changes and updates created in the upstream repository. Those changes simply “flow down” to the member’s solution. However, if a member organization forks the code — if they create a solution that strays from the main stream — their solution no longer receives updates, fixes and changes from the upstream repository. This organization is now solely responsible for maintaining their solution without the benefit of the upstream community, much like the baby salmon that took a tributary and then have to fend for themselves rather than remain in the main stream and receive the benefit and guidance of the other salmon making their way to the ocean.
  • HPE and Red Hat Join Forces to Give Customers Greater Choice for NFV Deployments
    Hewlett Packard Enterprise ( NYSE : HPE ) and Red Hat, Inc. ( NYSE : RHT ) announced today they are working together to accelerate the deployment of network functions virtualization (NFV) solutions based on fully open, production-ready, standards-based infrastructures. HPE plans to offer ready-to-use, pre-integrated HPE NFV System solutions and HPE Validated Configurations incorporating Red Hat OpenStack Platform and Red Hat Ceph Storage for communications service providers (CSPs).
  • Red Hat Joins the OpenPower Foundation
    As part of our commitment to delivering open technologies across many computing architectures, Red Hat has joined the OpenPOWER Foundation, an open development community based on the POWER microprocessor architecture, at the Platinum level. While we already do build and support open technologies for the POWER architecture, the OpenPOWER Foundation is committed to an open, community-driven technology-creation process – something that we feel is critical to the continued growth of open collaboration around POWER.
  • Buy, Sell or Hold? Analysts Approach: HCA Holdings, Inc. (HCA), Red Hat, Inc. (RHT)?

Linux and FOSS Events