Note: This blog post and interview is an excerpt of an article on Linux.com

Starting an open source program office is a growing trend among companies that leverage open source software in their business strategies.

Led by an open source program officer, open source offices can range in size from one or two advocates on an engineering team to an entirely separate R&D division. But the goal is the same: to strategically address common challenges companies face when adopting open source software.

"An open source office whether centralized or by division can bring multiple best practices on how a company can manage consumption, compliance and contribution to open source” says Nithya Ruff, the head of SanDisk’s Open Source Strategy office, in the Q&A below. "It can create a proactive plan for driving more strategic involvement in projects important to the company’s roadmap and drive clear and common messages.""

We caught up with Nithya Ruff for a preview of their panel discussion, “Open source lessons from the TODO Group.”

What are some of the common challenges companies face when they start adopting open source?

Nithya Ruff: Companies that have not grown up with open source in their DNA face a number of challenges when they first adopt open source or look at adopting an open source strategy.

a. They don’t completely understand the licenses and legal obligations and often see it as a single license which would force them to open their intellectual property or trade secrets. Once they start understanding it more deeply they realize that one can consume without creating obligations and that there are a number of different licenses each with their own obligations. So legal education is the first challenge.

b. The second is to create awareness of the need to engage with open source and the need to have a strategy around how the company needs to work with open source communities. This is a strategy and a business discussion with executives and business leaders so that they support the need to have a plan and investment in this effort. These are the top 2 areas of challenge.

How does creating an in-house open source office help companies maximize their open source involvement?

Ruff: One can continue to engage with open source in an ad hoc and distributed manner but this often creates issues and challenges with messaging, unintended consequences, multiple processes and confusion in the market on company intent. It could also inadvertently expose a company to compliance risks. An open source office whether centralized or by division can bring multiple best practices on how a company can manage consumption, compliance and contribution to open source. It can create a proactive plan for driving more strategic involvement in projects important to the company’s roadmap and drive clear and common messages.

What is one of the key lessons SanDisk has learned about corporate open source participation since starting its open source office two years ago?

Ruff: The biggest lesson has been learning about how much open source activity there already was in the company and how we would not have any knowledge of this and support it without starting this initiative. Knowing consumption and dependencies has allowed us to shape our compliance and community engagement plan.

How have you benefited from your involvement in the TODO Group?

Ruff: Just this week, I needed to know a simple and best practice way to manage contribution license agreements or CLAs. I contacted my fellow open source officers in other companies via the TODO group and within hours I had two very usable solutions. This is huge, to be able to consult each other on the best way to do things. I am a big believer in reuse and to not recreate. And this was a great example of how we can share practices. TODO members have been generous in sharing their time and coming to SanDisk to share their practices like Guy Martin (Autodesk) and Cedric Williams (PayPal) did recently. It is impactful to hear from other companies and to learn from their initiatives in open source. This is one area, where we don’t compete and are happy to share.


Attribution and License

This blogpost was published by the TODO Group under the terms of the CC-BY-SA v4.0 license. The original page can be found here.