We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

The Cuckoo in Bidding: When the Manufacturer Loses to Itself

Formal Metadata

Title
The Cuckoo in Bidding: When the Manufacturer Loses to Itself
Title of Series
Number of Parts
43
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date2024
LanguageEnglish

Content Metadata

Subject Area
Genre
Abstract
Open Source often means more than just "free and accessible source code"; it also encompasses license models for free, unrestricted use. Yet, there are companies that successfully develop high-quality, commercially viable software with significant financial investment and a dedicated team of developers. Revenue is generated through "service and support" contracts, quality-tested releases, troubleshooting with short SLAs, or assistance with rollout and operation. This is based on the general understanding and acceptance that manufacturers need to be financially compensated for the use of their software, even if it is available as FOSS. As Open Source becomes more popular in public administration, procurement projects are increasingly being tendered solely on price. This attracts bidders who neither internalize nor share the principles of free software: Parasitic freeloaders offering third-party software on pure operational terms without any manufacturer compensation, consistently outbidding the manufacturer or its partners. Like a cuckoo, they shirk the work of raising their young onto others, even killing their offspring and peers in the process. The consequences are devastating. If this happens systematically and regularly, it rapidly deprives any further development of Open Source software of its financial foundation. The Open Source ecosystem is ruthlessly destroyed by freeloaders who play against the rules. How can Open Source projects protect themselves against this abuse? Various associations and providers are currently launching initiatives to ensure fair and sustainable procurement of Open Source software. A "Code of Conduct" could foster a common understanding. Ultimately, the tendering entities and public procurement officers need to be convinced that pure tenders seeking only the cheapest bidder destroy their future choices. And there are legal tasks to be accomplished: What might legally robust "Fair Use" clauses look like that could become mandatory criteria for tenders?