Data Center is our focus

We help to build, access and manage your datacenter and server rooms

Structure Cabling

We help structure your cabling, Fiber Optic, UTP, STP and Electrical.

Get ready to the #Cloud

Start your Hyper Converged Infrastructure.

Monitor your infrastructures

Monitor your hardware, software, network (ITOM), maintain your ITSM service .

Our Great People

Great team to support happy customers.

Thursday, February 13, 2014

Globodox versi 9 sudah keluar !! silahkan download

Here is the big news you were waiting for!!
Globodox version 9 is out !!
We are pleased to announce that we have released a new version for Globodox. The new version 9 is our biggest and most ambitious release in a long time with a whole bunch of exciting new features!
The full setup Globodox 9 – is now available to download!! An update setup to upgrade your existing installations will be available in a couple of days.
Here is a list of the big new features in version 9…
Globodox Drive
Globodox Drive appears like any other drive in Windows Explorer and the Windows File Open box. It allows you to access folders, tags, document types and stack types with ease without having start Globodox Desktop Client. This means that you can now easily open and view documents stored in Globodox from within any Windows application. It also simplifies the process of attaching documents to email messages you are sending MS Outlook or Web based email services such as GMail or Yahoo mail.
Globodox Mobile App for Android and iOS based devices
The Globodox App allows users to view, access and delete files on the go using any Android and iOS device. With a simple user interface navigate through your files with ease. Folders, Tags, Document Types and Stack Types are all now available even when you are not at your desk. See…
A FAQ is available at…
Globodox Virtual Printer
The Globodox Printer allows you to print a document from any Windows application and automatically add the printed document as a searchable PDF file in Globodox. Need to store the receipt of an online purchase you just made? Simply print the receipt to the Globodox Printer and it is stored in Globodox and categorized for you right away!
Send To
The new Send To feature in Globodox integrates with the Send To right-click menu option in Windows Explorer by adding Globodox option to it. Simply select one or more files in Windows Explorer or your Windows Desktop and choose this option to add the files to Globodox.
Import Pre Scanned Pages
In the Scan Window, you can choose a folder instead of a scanner as the source of scanned images. GLOBODOX will treat these images as if they were received via a scanner and will let you perform additional powerful features such as bar coded separator page detection, combining pages into PDF files and assigning Document Types, Stack Types and Tags.
Capture Folders
Capture Folders provide a quick and easy way to add documents to Globodox while also categorizing/indexing them.
Capture Folders are folders which Globodox monitors for new files. Each capture folder is linked to a Destination Profile in Globodox. Whenever Globodox finds a new file in a capture folder it is monitoring, it adds that file to the Globodox DB specified in the Destination Profile along with any indexing information specified in the Destination Profile.
For existing users of Globodox
If you’re already a Globodox user, you will need to wait for just a couple more days till we release the update setup for version 9. That setup will enable you to upgrade your existing installation of Globodox.
Not part of the Globodox family?
Click here to download a full featured 30 day free trial of Globodox version 9!

10 Proyek opensource terbaik 2013

diverse open source projects
Image by
(9 votes)
We cover a wide range of open source projects on From beehives to Linux, from the Netherlands to India, featuring a diversity of open source projects is part of our mission. It's a goal we achieved in 2013 and one we'll continue to strive for in 2014.
Our readers tell us on a regular basis that they appreciate how we branch out and capture stories from open source projects of all kinds. In this Best of, we gathered our top 10 articles on open source projects. If you don't see your favorite, please share it with us in the comments and remind us why it's awesome.

Top 10 open source projects in 2013


"I agree and always tell people in training to go ahead and try to break Koha because that's how they learn and how they come up with ways to improve the final product." —Nicole Engard, Vice President of Education at ByWater Solutions


(cloud computing)
"There is an open design and development process, and it works. It can and does support integrating new projects, the process for vetting new ideas, and growing a stronger portfolio of new services. The sunlight of transparency only makes the design and vetting process stronger. Continued innovation is critical." —Diane Mueller, OpenShift Origin Community Manager


"We're creating the pull request for courses, and the process of getting there means creating the tools necessary to support the community of a new open future for education." —cofounder and CTO Eric Martindale


(open data)
"By equipping reporters with the ability to automatically digitize these scanned paper records, DocHive could take hours of drudgery out of the early stages of document-driven investigative reporting and dramatically upgrade the watchdog capabilities of newsrooms large and small." —Tyler Dukes, managing editor at Reporter’s Lab


(server environments)
"Docker makes it very easy to create and deploy container images. Developers can very quickly, on their own machines, create and configure a container based on one of the widely available base images. They can then then test the container locally, and when it works, create a standardized image that they can deploy anywhere in the cloud, running the exact same set of bits that they tested locally." —Alexander Larsson, principle software engineer at Red Hat

Project Libre

(project management)
"We all know things don't go exactly as planned, so when those mild or major impacts happen, a project management software plan will automatically adjust to show you the new reality." —cofounder Marc O'Brien


"We have a great mix of talented people who are passionate about networking and have a desire to create an open controller SDN codebase that anyone can use. This is what is most important to OpenDaylight’s longevity." —David Meyer, Chair of the Technical Steering Committee


"Zanata grew out of Red Hat's long-standing involvement in open source software translation communities, and it is used inside Red Hat to handle the translation of Red Hat software products into 22 different languages. The best part about Zanata is that the features are mostly determined by its users." —product manager Runa Bhattacharjee


(project management)
"Customers are more willing to talk with us and to share information when they see that we are living an open source business model. I believe that we have access to more valuable insight this way, compared to our closed source competitors." —founder Frank Bergmann

Open source beehives

"Their partnership has generated the creation of two beehive designs that can be freely downloaded (and 3D printed) and filled with innovative sensors to log and track bee colony health using the Smart Citizen kit." —Tristan Smith, Video & Communications at Open Tech Forever

Drupal, terus berjaya

The story of Drupal's beginning sounds like a story ripped from the pages of a cyberpunk novel. It was in a small apartment during college that Dries Buytaert created what would become one of the most widely-used open source content management frameworks. As a forum for his friends, early-Drupal was used as a communication tool for monitoring the group's fragile Internet connection, which was expensive and being spliced between them.
The evolution of Drupal since its introduction to the open source community in 2001 is a significant touchstone for the development of how the open source community and commercial private enterprises interact in the digital arena.
In the mid-90s, careful observers were noticing a new kind of economy emerging as a result of open source. This economy was based on creators freely sharing and further refining high-quality content with users who would provide helpful feedback, and often, make contributions of their own. More than a thriving ecosystem generating user-sensitive content and ideas, however, open source communities stood, and currently stand, for an ideology of communal work and collaboration. Open source communities are driven by a commitment to the success of the collective and to user contribution.
It is understandable then that politically-savvy open source community members saw a natural dovetail between the group and the public sphere. And, if users and creators could work together to create a sustainable, thriving online network around useful content, surely open source principles could be successfully incorporated in many other industries and social communities as well. For one, the open source community has become one of the foremost proponents of democracy on the Internet.
Future designers, developers, and creators can learn from Drupal’s legacy of sustaining such a powerful force in promoting open source projects as starting points for spurring on more democratic communities. The philosophy of open source development transmuted into a movement for open source governance, with an increased emphasis on the value of deliberation and educated compromise among  participants. The strides made by the open source community provide a continuing example of how a group can operate efficiently and build outstanding projects and ideas, exemplifying the potential for participatory democratic systems. 
As we all know, one of the greatest strengths of all open source communities is their flexibility—open source projects can adapt to users' needs with extreme efficiency, allowing development to remain relatively unshackled from commercial pressure.
Drupal is a prime example of this. Drupal's first real distribution was the result of the independent project: DeanSpace, created in 2003 by Zack Rosen and Clay Johnson as the central platform for Howard Dean’s online presence for the 2004 presidential election. Dean supporters continued to encourage groups around the country to create their own websites and network with DeanSpace. The flexibility and independence of each web enclave of Dean supporters mimicked Drupal’s program structure—a core + module format.
DeanSpace served as the community’s command center, coordinating wider activities, while local groups crowd sourced outreach strategies and events. This provided uniformity in core functions and added versatility where needed. Dean’s campaign stood out from the rest of the superPAC-funded candidates with its grassroots organization and crowd sourced funding. The campaign embodied a commitment to voter representation and made a huge stride towards a more active political dialogue between citizens and representatives.
After Dean’s withdrawal from the race, DeanSpace was dissolved and recreated into CivicSpace—a platform that enables efficient and versatile civic engagement and coordination. Users for smaller affiliated groups can create a customized node and use the tools at hand to create events, post pictures, and distribute local news on the subject; all the while maintaining connection to the larger organization, allowing for wider coordinated activities.  The managers of CivicSpace set out to make the project more than just an offshoot of the Drupal community; they wanted it to be a major contributor. Today, CivicSpace is widely considered to be the first Drupal distribution.
Additionally, the creation of CivicSpace elevated Drupal as the CMS/CMF of the people. Consequently, those citizens who chose an online platform (Drupal) to organize their efforts became known as thenetizens. The notoriety Drupal achieved through enabling such a dominant voice for civic engagement became a scintillating feature of both the product and the community, a feature that would cause increased success. With the dawn of the age of the conscientious consumer, the public had become increasingly disenchanted with products of the commercial industry, and the opportunity to turn to the open source community for software development became not just financially appealing, but ever-more ethically compelling. As stories of pervasive corporate exploitation increased, citizens became skeptical of corporations with which they had felt familiar and trusting.
Thus, the rise of Drupal coincides with a movement that values thoughtful collaboration over aggressive competition. Contrary to tmany proprietary software companies and products, open source projects tend to become increasingly user-friendly and the communities around them actively work to welcome newcomers to the fold. The driven and radical altruism of many open source communities offered this new movement the authenticity they hungered for and one-upped the commercial competition’s biggest selling point—affordability. 
It wasn't long before the usability, affordability, and ideology driving the popularity of open source began to pose a major threat to the commercial software industry. At first, the industry reacted with indifference, but one infamous case wherein Microsoft released a series of attack ads against the open source giant OpenOffice revealed that open source was becoming more popular than anticipated. When members of the industry realized, however, that open source wasn’t going away, the market began to adapt. Software giants began their own open source projects, some as an attempt to court open source users and others as a way to promote further interoperability between systems. Open source communities began to influence new projects and the foundation of a new economic model.
In 2007, Dries Buytaert founded Acquia, a Drupal consulting firm that contracts with businesses, non-profit organizations, and government departments to provide specialized insight and Drupal support. Other companies began to organize, reflecting the continued emergence of an industry built around access to specialized knowledge and intellectual property. Open source consulting agencies provided an additional bridge between the community and the wider public, creating a new market for open source development. Many projects from the open source community had to assimilate to the new demands of the wider market, forcing further innovation in the areas of wider usability for non-experts and data management.
This only broadened their original base and drew in new developers and voices to the community. This new direction did not co-opt open source communities and drag them toward commercialized software models, and only open source platforms like Drupal, Joomla, and Wordpress straddled the lines between private use and commercial enterprise.
Larger, more notable companies began to transition their software and webdev needs to open source solutions, and, as a result, created demand for increased technical support and expert advice. There arose new niches for open source to fill. What started as a strictly private and user-driven experience grew increasingly sensitive to market demands, but still continued to be first and formost a community dedicated to authentic user-driven innovation and collaboration. The developments remained relatively untethered from the dictates of the sometimes-panic of the company boardroom.
 In 2009, Drupal experienced a Cambrian explosion of notoriety when they nabbed what is possibly their most high-profile user to date—, with Acquia consulting the transition. News outlets buzzed about the purpose behind the move due to the fact that the White House itself characterized the shift to Drupal as signifying a new, more open and transparent government. The collaborative nature of open source software and code was expanded beyond the practical reality to encompass a message of civic engagement and cooperation. Impressed by the security and capabilities of Drupal, other prestigious clients like the U.S. department of Commerce, the Louvre, and the International Monetary Fund became clients and users as well. At this time, in order to ensure universal access to quality code and promote further stability, Dries Buytaert instituted a code freeze to the core Drupal code. This freeze locked down Drupal's source code in order to prevent additional bugs from swarming out of a programming misstep in the source code, safeguarding the creations built by the diverse community of users.
With new themes and plug-ins added daily, Drupal continues to be one of the most versatile platforms available. For tasks Drupal cannot accomplish, the community continues to innovate and integrate with other platforms, enhancing the functionality for all users. So, what’s next for Drupal? Gauging by their history, we can expect Drupal's appeal and use to continue to broaden throughout the civic, social, and business spheres. Additionally, it seems unlikely for it to stray from its roots as a collaboration-driven, operator-sensitive system with supporters, users, and developers firmly entrenched in the open source community.

5 tool opensource untuk Project management

open source project management
Image credits: photo
(9 votes)
Last year, covered some popular open source project management tools (ProjectLibre, ]project-open[, and OpenProject.) We found these articles to be valuable to our readers, so here we take a look forward at what we think 2014 holds for these open source project management tools.
This is by no means an exhaustive list, but each tool listed here has been deliberately selected based on a rich feature set.


In our interview with Marc O’Brien, co-founder of ProjectLibre, we featured a tool with support for task management, resource allocation, tracking, Gantt charts, and much more. ProjectLibre is a good alternative to a commercial software product like Microsoft Project.
In December 2013, ProjectLibre released version 1.5.8, and a full rewrite of the codebase towards an Open Services Gateway Initiative (OSGI) modular architecture is ongoing. This will allow connector modules for better integration with enterprise solutions such as Enterprise Resource Planning (ERP).
ProjectLibre is a Java based client tool. During their 2014 Q1 this year, they will release version 2.0. It is not clear yet when the SaaS version will become available.
ProjectLibre was awarded InfoWorld's "Best of Open Source" in 2013 and ranks in my personal top 3 favorite open source project management tools.


LibrePlan is a web based application, making project management available to not just the project manager, but the entire project team, and if necessary across organisations. LibrePlan is licensed under the AGPL. This is another full featured tool supporting resource allocation, Gantt charts, financials, and more. These features coupled with a web based application make LibrePlan a great collaboration platform.
LibrePlan ranks in my personal top 3 favorite open source project management tools because of its modern design and balanced user interface, as well as, good and complete documentation, built in reporting, and professional support.
View all of the features on this page.
I did not note any newly released features or version release dates for 2014.


"Team collaboration redesigned" is how we introduced our interview with Birthe Lindenthal, Chairperson of the OpenProject Foundation's Board of Directors.
OpenProject is released under the GNU General Public License Version 3 and runs on Ruby on Rails. I happen to agree with their tagline that this tool has "everything you need for collaboration" to support the entire project life cycle. There are two big features that deserve to be highlighted: OpenProject supports Accessibility and a Scrum plugin supporting Agile methods and Scrum teams.
OpenProject is currently working on a major upgrade ready for release during 2014 Q1. Version 3.0 will support Ruby 2.0 and Rails 3.2. See their full roadmap here.
OpenProject ranks in my personal top 3 favorite open source project management tools because of their user interface, documentation, and rich feature set.


In our interview with Frank Bergmann, founder of ]project-open[, he gave readers insight into what this tool, ]po[ for short, is meant to do:
"We're not dealing with individual project managers, but focus on organizations with 10 - 1,000 users that earn their money by executing projects."
]po[ is said to be used by over 6,000 companies worldwide. A full installation is based on over 100 open source packages including a Linux distro, Postgre SQL, TCL as it’s main language, Perl for system integration, and many more. It supports integration with 30+ packages such as OpenLDAP, OpenOffice, ProjectLibre, and others.
]po[ is an enterprise project management tool with many features, including support for Agile. The software is released under a mixed source model, or a "dual license", meaning that at it’s core it is open source, with additional modules released under a commercial license. ]po[ runs as client software on both Windows and Linux, depending on a stack of open source packages.
In 2014, ]po[ hopes to release version 4.2 which will bring a full AJAX GUI, integration between collaboration features and project management, and more.


Redmine is a web-based project management tool that I actively use. It's powerful, runs on Ruby and Rails, and is licensed under GNU General Public License v2 (GPL).
Where it lacks enterprise features, compared with the other project management tools I've mentioned above, it has strong web applications. Along with basic project management features, this Redmine includes a wiki, repository, and issue tracker. View the full feature list here.
Redmine also has an advantage in access: it is available to project managers, other team members, as well as, the clients.
In 2014, the Redmine roadmap shows a steady flow of releases that continue to improve the quality of the tool.

BONUS TOOL: Agilefant

Agilefant, as its name implies, is based on Agile methods. However, this open source project management tool also supports product portfolios, projects, sprints, and multi-team development. See the full feature set in the Agilefant user guide.
Agilefant offers a free and open source product that can be downloaded and deployed into your own private cloud. They also offer a SaaS solution. In 2014, they will add a paid service.
Agilefant runs on Java, Tomcat, and MySQL. The source code and license can be found onGitHub.

10 hal menarik terkait legal di dunia opensource

free software legal issues
Image by
(8 votes)
The year 2013 continued the trend of the increasing importance of legal issues for the Free and Open Source Software (FOSS) community. FOSS projects have  increased from 900,000 in 2012 to 1,000,000 in 2013, according to Black Duck Software.
Last year, I provided a look at the top legal issues from the year before. Continuing with this tradition, here is my take on the top ten legal developments in FOSS during 2013.

1. Android patent litigation

The litigation surrounding the Android operating system has continued around the world, but a new front has opened in a suit recently filed by the Rockstar Consortium against Google, Samsung, ZTE, Pantec, Asus, LG Electronics, HTC, and Huawei. The Rockstar Consortium consists of Apple, Microsoft, Blackberry, Ericsson, and Sony. Unlike the litigation between Apple Computer and Samsung, this lawsuit goes after basic features of Android and could have a much broader impact on the Android market. The litigation between Apple Computer, Inc. and Samsung continues with cases pending throughout the world.
As I mentioned in last year’s post, a decision in Silicon Valley awarded Apple $1.05 billion in damages for Samsung’s violation of its patents. The judge reduced the damages, but the parties were granted a new trial and in the fall of 2013, the jury resolved the dispute over damages by awarding Apple $290 million. According to eWeek, Apple has been awarded $930 million across all of its suits (Red Hat represents some of the parties in other matters, I offer no opinion on the correctness of the decision). The litigation will clearly continue.

2. License compliance and standard of care

On June 14, 2013, the district court of Hamburg found that Fantec violated the obligation in the GPLv2 to provide to its customers the "complete corresponding source code" of the software. Fantec objected that it had been assured by its Chinese supplier that the source code received from the supplier was complete. And Fantec claimed that they had investigated options with third parties for source code analysis and had been informed that such reviews were quite expensive and not completely reliable. The court rejected these excuses.
The court required Fantec to pay a contractual penalty based on the prior settlement agreement. In addition, the court awarded the plaintiff’s expenses in enforcing the GPLv2. The distributor of GPLv2 software is responsible for compliance with the terms of the license and cannot delegate such responsibility. Even the most sophisticated companies can have problems with the compliance as demonstrated by Samsung’s problems with the inadvertent release of the native Linux driver for Microsoft’s exFAT file-system.

3. Rise of forks in major programs

One of the major advantages of open source software is the flexibility for companies to modify the software and even develop a completely different version of the product, so called "forking." Although forks have occurred in the past, they are frequently temporary departures which are reintegrated into the original product. However in 2013, we witnessed a well-financed fork in a major product of MySQL software: Intel Capital led a consortium of investors in a $20 million round of financing for SkySQL (which is now managing the MariaDB version of MySQL).
Google announced that it would migrate all of its MySQL software to the MariaDB version of the software. MySQL software is widely used and the effect of this fork is difficult to predict. Although not strictly a "fork," the Android operating system continues to have challenges due to its fragmentation. These problems may be exacerbated by proprietary extensions such as the CyanogenMod, which is a customized, aftermarket firmware distribution for several Android devices. The CyanogenMod is designed to increase performance and reliability over Android-based ROMs released by other vendors and carriers. Cyanogen has recently received a $23 million financing led by Andreessen Horowitz.  

4. Enforcement of the FOSS licenses

Although FOSS is widely used and GPLv2 is the most widely used license, the GPLv2 has rarely been the subject of litigation, particularly in the United States. Until 2013, this litigation has been brought primarily by non-profit entities on behalf of small companies and individuals. However, this year two lawsuits were brought by commercial companies to enforce the GPLv2 against other commercial companies: Continuent v. Tekelec and Ximpleware v. Trilogy. As FOSS is more widely used, it is natural that it could become part of disputes between companies. The question is whether these suits indicate a trend or whether they are simply unusual situations. In addition, if the suits go to trial, they could provide guidance on the interpretation of the GPLv2. 

5. GitHub adopts a license selection policy

As I noted last year, one disturbing trend was the posting of "FOSS" modules without licenses. This problem was particularly acute on GitHub. However, Simon Phipps of the Open Source Institute (OSI) worked with GitHub, and GitHub stated that "sharing your code isn't everything... it's also important to tell people how they can use that code" and that "choosing an open source license can be confusing." GitHub then created, a website to assist developers to select a license. Although I disagree with some of the statements in the site, it is an important change to GitHub’s policy. (I am particularly concerned about the inclusion of "No license" as an option similar to a traditional license).  

6. Good news in the patent wars

Patent settlement on VP8. Although much ink has been spilled over patent suits filed against open source projects, we rarely get to announce good news.  This year, we have such an opportunity: Google settled patent threats from MPEG LA, LLC about Google’s use of the open source VP8 codec. The dispute arose in 2011 when Google announced that support in Google Chrome for the widely used H.264 codec would be dropped. Google would promote the VP8 codec as open source. Google had acquired this codec as part of the purchase of On24 Technologies in 2010. MPEG LA had been threatening On24 Technologies for a long time and, thus the settlement is a surprise; the announcement of a Department of Justice antitrust investigation into MPEG LA over its call for a patent pool for VP8 may have encouraged the settlement.

7. FOSS enters government use

The use of FOSS by governments and government participation in FOSS projects would seem to be a natural fit but has frequently run into problems in implementation. One example of a great success is the OpenStack cloud software project which began as a joint venture between NASA and Rackspace. The OpenStack project is now managed by an independent foundation and is one of the fastest growing open source projects, with over 290 supporting companies and 13,000 individual members.
However, open source adoption by governments is very uneven.
Germany has been particularly active in 2013: in January, Jimmy Schulz, a member of Parliament and chairman of the Interoperability, Standards and Free Software Project Group, stated that current law prohibits governments from being part of the development process in FOSS projects because they cannot give away services; he recommended that the law be changed to permit such participation. More recently in December, the new governing coalition agreed that public administrations should give priority to open source in their public procurement and commit the coalition to support open source at a European level. Munich also implemented its transition to open source IT in October and November. However, the UK, despite early commitments to open source, has not effectively implemented those strategies.
In France, Jacques Marzin, the French state Chief Information Officer (CIO), confirmed that government is working to implement the Open Source Guidelines approved last year by Prime Minister Jean-Marc Ayrault (these guidelines promote the use of free software and open source in French ministries).
The situation in the US remains complex with FOSS being widely used but actions by some departments making such its use more difficult. The Department of Defense’s (DoD) release of the DoD Open Systems Architecture Contract Guidebook for Program Managers, v.1.1 in June demonstrates the complexity of the landscape for FOSS. On the one hand, this DoD publication acknowledges the "strong relationship between Open Source Software and Open Architecture" and, consistent with the DoD’s Better Buying Power 2.0 Initiative, encourages the managers of the DoD’s major systems to explore the use of FOSS; on the other hand the Guidebook cautions that certain FOSS licenses “may be problematic for the Government." Recently, Lockheed donated the source code of the Distributed Data Framework (part of the Distributed Common Ground System) to the Codice Foundation, a nonprofit supporting government open-source projects; this donation makes the code available to all government agencies and their commercial partners.
In addition, Representative Issa introduced the Federal Information Technology Acquisition Reform Act to encourage the use of FOSS and required that regulations be revised to ensure: "The standards and guidelines shall include those necessary to enable effective adoption of open source software." Finally, the National Defense Authorization Act for Fiscal Year 2014 (FY 2014 NDAA) includes two sections that should ultimately work to encourage the use of FOSS. Specifically, Section 935 of the FY 2014 NDAA, titled "Additional Requirements Relating to the Software Licenses of the Department of Defense" provides that the Chief Information Officer of the DoD shall update the plan for the inventory of selected software licenses of the DoD required under section 937 of NDAA for FY 2013, to include a plan for the inventory of all software licenses of the DoD for which a military department spends more than $5 million annually on any individual title.
With respect to cloud computing, Section 938 of the FY 2014 NDAA, titled "Supervision of the Acquisition of Cloud Computing Capabilities" provides requirements for reviewing, developing, modifying, and approving the requirements for cloud computing solutions for data analysis and storage by the Armed Forces and Defense Agencies. Section 938 also includes requirements for reviewing, developing, and implementing plans for the competitive acquisition of cloud computing systems, including developing plans to ensure that the cloud systems are interoperable and universally accessible and usable through attribute-based access controls, and plans to ensure the integration of cloud systems with enterprise-wide plans of the Armed Forces and the DoD for the Joint Information Environment and the Defense Intelligence Information Environment.

8. Contribution agreements and projects

The management of contributions to FOSS projects continues to be important. The Eclipse Foundation revised their contribution process by implementing new, simpler Contributor License Agreements (CLAs) for all contributors at Eclipse. This CLA is much shorter than CLAs for other projects, limiting the agreement to stating that the contributions will be provided under the license(s) for the project to which they’re making a contribution. They automated their process to accept contributions via git and Gerrit as well as automating their workflow.
The importance of the terms of contribution agreements was also important in 2012 in the context of the departure of Nikos Mavrogiannopoulos from the GnuTLS project. As the primary drafter of the Harmony Project contribution agreements, I have had an opportunity to consider these issues in detail. I am in favor of making the contribution process more simple, but the process should be clear. I have some concern that the Eclipse CLA goes too far in simplifying the CLA, for example by not including standard provisions from Article 2 of the Uniform Commercial Code (all of the old favorites, such as waiver of consequential damages and disclaimer of implied warranties).

9. Rise of open source collaborations

Open source collaborations continued to grow last year. Two of the major new collaborations were the AllSeen Alliance (the Alliance is based on the AllJoyn open source project which develops software which "can communicate over various transport layers, such as Wi-Fi, power line or Ethernet, regardless of manufacturer or operating system and without the need for Internet access") and Open DayLight (software "to accelerate adoption of Software-Defined Networking and Network Functions Virtualization").
Both of these projects chose to become members of the Linux Foundation Collaborative Projects rather than developing their own independent organization. This option can be very attractive because it reduces the cost of starting the project. The OpenStack Foundation continues to grow at a rapid rate, increasing the number of companies involved from 150 to 290 and individual members from 6,000 to over 13,000 in early 2014 (as a matter of transparency, I represent the OpenStack Foundation).

10. Commercial companies support FOSS

Commercial companies have realized that the support of FOSS projects is an important strategy. IBM announced that it will invest an additional $1 billion in Linux and other open source technologies to support its Power System servers.
As noted above, Intel invested $20M in SkySQL to develop MariaDB software, a fork of MySQL. Netflix is providing its cloud tools as FOSS, named Netflix OSS, to other cloud service providers. Netflix had developed many tools to fill in the gaps in Amazon Web Services (for example, the Chaos Monkey software for testing web application resiliency) and is now making them available as FOSS to other cloud providers. The adoption of the Netflix FOSS tools by other cloud providers could lead to such cloud providers being able to provide more scalable public clouds; such public clouds might even become an alternative to Amazon Web Services. Netflix also established the Netflix OSS Cloud Prize: $200,000 across ten prizes to reward developers for assisting in developing Netflix’s cloud platform.
EMC and VMware took another approach: they spun out its Cloud Foundry software (a FOSS project) to form Pivotal, a new company with 500 employees. General Electric then invested $105 million in Pivotal. IBM also announced that they would collaborate with Pivotal in developing its technology.