Dissecting Microsoft’s proposed policy to ban commercial open source apps


Bradley M. Kuhn is a free and open source software (FOSS) activist who serves as “hacker-in-residence” at Software Freedom Conservancy, a not-for-profit organization that provides support and legal services for open source software projects. In the aftermath of Microsoft’s policy change, Kuhn and his colleague Denver Gingerich penned an in-depth blog post outlining their issues with the new policy (as well as more long-standing gripes with Microsoft’s attitude to open source), and the main thrust of their argument was that the very nature of open source software is that it’s free of restrictions, with no favoritism over who can and can’t monetize it.
“We believe that the rights ensured by FOSS, as is well-enshrined in the licenses themselves, allow everyone to monetize FOSS,” Kuhn told TechCrunch. “FOSS licenses have always treated all commercial and non-commercial actively equally. It’s free as in freedom, but also it’s free as in market.”
While there are many different kinds of open source licenses available (whether they are all truly “open source” is a debate for another day), Kuhn is referring specifically to so-called “copyleft” licenses. Such licenses have few restrictions, but they do mandate that any software derived from the original open source project must be released under a similar open source license. This runs in contrast to more “permissive” licenses that don’t impose such restrictions (meaning that private companies can easily adopt an open source project as part of a proprietary product).
Put simply, the spirit of open source is all about the freedoms it permits.
“Copyleft licenses require that you provide correct, complete, and corresponding source code to all customers, and have various rules about patents, but there are otherwise generally not intended to be serious restrictions on the ability monetize FOSS,” Kuhn said.
A recurring discussion point around Microsoft’s proposed policy change is how it may protect trademarks or avert “brand confusion.” But Kuhn argues that this is already well-provisioned for in existing laws, and it’s not specifically a FOSS problem — it’s a problem relating to software in general.
“Trademark rules control the rights to name and market a product under a particular name,” Kuhn said. “Trademark restrictions on using a name are completely compatible with FOSS and have long been encouraged. Now, this is not a FOSS-specific problem, but cloned software by fly-by-night entities and malware on app stores is a broader problem.”
While all of this is probably true, independent open source developers generally don’t have the resources to pursue what are often faceless entities over trademark violations (assuming that they actually own the trademark at all). And that is precisely why a policy that deters “fly-by-night” developers from capitalizing on the hard work of others will likely be well received whenever it’s finally introduced.
-
- Login or register to post comments
Printer-friendly version- 1022 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
today's howtos
| Open Hardware: XON/XOFF and Raspberry Pi Pico
|
Security Leftovers
| How to Apply Accent Colour in Ubuntu Desktop
A step-by-step tutorial on how to apply accent colour in Ubuntu desktop (GNOME) with tips for Kubuntu and others.
|



This section of TuxMachines will no longer have new stories in it (with some caveats, including this post). To see the latest stories go to

.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.


Recent comments
2 days 4 hours ago
2 days 8 hours ago
2 days 8 hours ago
3 days 15 hours ago
3 days 16 hours ago
3 days 17 hours ago
3 days 17 hours ago
3 days 17 hours ago
3 days 20 hours ago
3 days 21 hours ago