Language Selection

English French German Italian Portuguese Spanish

Openwashing: Altair, Microsoft and SmartBear

Filed under
OSS

Mac Asay at it again

Microsoft FUD Against FOSS Again

Black Duck again

More new FUD

  • Evaluating Open Source Software to Build a Connected Autonomous Vehicle [Ed: Muckraking as usual, lawyers from Mayer Brown LLP (Marjorie H. Loeb, Richard M. Assmus, Linda L. Rhodes and Paul A. Chandler) make FOSS sound scary, dangerous legally. It wasn't so long ago that Black Duck, Microsoft's anti-copyleft front, told the media that if automobiles adopted FOSS, vehicles would start crashing. CBS/ZDNet posted that crap for them.]

    The varying OSS licenses may conflict with each other, which can frustrate an automaker’s license compliance. To comprehensively assess the risk that any combination of OSS blocks may infringe or violate the license terms, one must first identify and trace the use of OSS throughout, which may involve analyzing thousands of files or lines of code contributed from numerous sources. To maintain compliance, significant due diligence is required both at the outset and each time code is changed or altered. To complicate matters further, the use of automated software development tools, which pull pieces of OSS from the Internet, may make it difficult to identify applicable license requirements before those pieces become an integral part of the code base. While scanning software and solutions may help identify embedded OSS, significant analysis is still required to evaluate the provenance of the OSS and whether its intended use raises license compliance or related concerns.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.