It is with regret that I urge all FOSS developers to treat anything Novell has contributed to the community as suspect, scrutinize any Novell contributions and purge them as deemed appropriate.
This threat is real, and it is not necessarily contingent upon whether or not Microsoft would actually sue customers for patent infringements. This is a classic case of posturing. Novell is leveraging its agreement with Microsoft in a way that harms all other Linux distributions and other FOSS projects. It is actively exploiting its unique position in ways that seem beneficial, but will pose risks to anyone but its own customers (and even their own customers are only protected for the next five years).
The agreement between Novell and Microsoft started with talks that began supposedly over six months ago. I do not find it coincidental that Novell recently contributed code to introduce Microsoft Excel VBA script compatibility in OpenOffice.org.
This is what I consider to be "loading the gun". With this, and possibly other contributions (especially with respect to but not limited to Mono), Novell is seeding projects with code that may cause anyone but its own customers to fear Microsoft legal action. I urge project leaders and FOSS developers to reject this code.
No doubt some customers will view Microsoft compatibility enhancements as a positive move for Linux. They are not considering the long term consequences of providing compatibility Novell's way. There are other ways to solve the same problems without inserting Microsoft IP into FOSS. A well designed automatic VBA translator would provide the same benefits to OpenOffice.org, for instance, as Novell's VBA patches. The difference is that a translator would not insert Microsoft IP into OpenOffice.org.
Bruce Perens wrote an open letter to Novell. Here is the open letter. I signed the Perens open letter with this comment:
Nicholas Petreley, Editor in Chief, Linux Journal, Freelance writer, analyst and consultant
Note from Nicholas Petreley: I urge everyone to purge their systems of anything related to Novell/SUSE. I also urge all FOSS developers to refuse to adopt anything contributed by Novell (such as the VBA compatibility code in OpenOffice.org). Now that Novell has a virtual license to adopt Microsoft intellectual property without risk to its customers, it is a reasonable fear to assume that everything Novell produces or contributes is potentially tainted with Microsoft intellectual property. This perpetuates a substantial risk to all but Novell customers for the next five years, and may pose a substantial risk to all current FOSS adoption once this current agreement expires. Novell must either reverse its agreement or provide some other acceptable remedy before its products and/or contributions will be anything less than suspect.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Speed Up Your Web Site with Varnish
- Containers—Not Virtual Machines—Are the Future Cloud
- Linux Systems Administrator
- Non-Linux FOSS: libnotify, OS X Style
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- RSS Feeds
- Reply to comment | Linux Journal
3 hours 49 min ago
- Yeah, user namespaces are
5 hours 5 min ago
- Cari Uang
8 hours 36 min ago
- user namespaces
11 hours 30 min ago
11 hours 56 min ago
- One advantage with VMs
14 hours 24 min ago
- about info
14 hours 57 min ago
14 hours 58 min ago
14 hours 59 min ago
15 hours 1 min ago
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?