Fresh on the heels of the entire Munich and Linux debacle, another story involving Microsoft and free software has popped up across the world, in Chile. A prolific magazine from the South American country says that the powerful Microsoft lobby managed to turn around a law that would allow the authorities to use free software.
On the topic of source code liability, Greer suggests that eventually software developers, including medical device development companies, will be responsible for the trouble their software causes (or fails to prevent). I think it’s fair to say that it is impossible to guarantee a totally secure system. You cannot prove a negative statement after all. Given enough time, most systems can be breached. So where does this potential liability end? What if my company has sloppy coding standards, no code reviews, or I use a third-party software library that has a vulnerability? Should hacking be considered foreseeable misuse?
Yes, the government -- one U.S. federal government employee told me that government IT tends to be "stove-piped," with people "even working within the same building" not having much of a clue what their peers are doing, which is not exactly the open source way.
That's changing. One way to see this shift is in government policies. For the U.S. federal government, there is now a "default to open," a dramatic reversal on long-standing practices of spending heavily with a core of proprietary technology vendors.
The Linux Foundation wants an open source platform in the pole position. The nonprofit consortium already has a fully functional Linux distribution, called "Automotive Grade Linux," or AGL. It is a customizable, open source automotive software stack with Linux at its core.
Google has its own plan for connecting cars to mobile devices and the Internet. Google's Android Auto is a dashboard navigation and entertainment system powered by an Android smartphone. It is very similar in concept to competing designs from Apple and Microsoft.
Companies increasingly understand that open source allows them to create faster, cheaper, and more secure products than they did by constantly reinventing the wheel in closed-source development environments. And the drivers of OSS adoption go beyond cost cutting and time savings. Participating in open source communities is a goal in itself—one that gives companies a competitive edge and helps them to attract top talent and influence project direction.
It's hard to tell which database management systems (DBMB)s are the most popular. DB-Engines gives it a try every month. And, by its count, Oracle is still the top DBMS, followed closed by Oracle's open-source DBMS MySQL, which is just noses ahead of Microsoft SQL Server.
As the General Services Administration’s 18F continues to promote open source federal IT development, the organization last week published a contributor’s guide to help those reusing and sharing its code.
Tracing the basics along with other key topics like how users can enhance code, 18F’s Dr. Robert Read explains in his post on 18F’s tumblr the best ways anyone — federal worker or not — can take part in the team’s development process and why they should. Read uses the FBOpen.com project as a real-time example of how contributors can leverage 18F code and even offer improvements, which he argues “improves the rapidity of our coding and the quality and security of the code.”
Jahia was incepted in 2002 in Switzerland – the name comes from the contraction of Java (our core language) and Bahia (which means “bay” in Brazil). To support the international growth of the project, Jahia Solutions Group was later formed (in 2005) with offices throughout Europe and Jahia Inc. (the US subsidiary) was created in 2008. Jahia has now offices in Geneva, Paris, Toronto, Chicago, Washington, DC, Dusseldorf and Klagenfurt – and outsourced support centers in Australia and Nicaragua.