open source program

Gil Yehuda, Senior Director of Open Source at Oath (which owns the Yahoo and AOL brands), describes the company’s open source goals.

For seven years and counting, Gil Yehuda, Senior Director of Open Source at Oath Inc. (which owns the Yahoo and AOL brands), has led the open source program at Yahoo. Now with an expanded scope, he is gearing up to grow his team and improve the program. The company’s formal open source program office serves as a hub to connect all open source activities across the company, he says, but it didn’t start out that way.

As with many other companies, the open source program started informally with a group of diligent engineers and a few legal people. But the ad hoc group soon realized it needed a more formal program if it was going to be able to scale to address more issues and achieve specific business goals. With a formal program in place, they are poised to achieve its goals.

The top five of Oath’s numerous open source goals, according to Yehuda, are:

  1. Keep aligned with the industry on open source technology standards by avoiding creating unique tech stacks that Oath alone would have to manage at its own expense.
  2. Make it easy for engineers to interact with open source as users and as contributors.
  3. Be viewed as an open source friendly company for partnerships and collaborations.
  4. Be known as a great place for engineers to work on open source projects.
  5. Give back to the Open Source community by sharing code and practices.

Measuring and monitoring success requires the right tools and attitudes. Yehuda says at Oath they actively solicit and listen to the needs of their many engineering teams, track all their work transparently in Jira, and spread the work across many teams who help with the process.

“We have custom tools we use to check code and manage projects, but we’re hoping to work more with our peers in the TODO Group on tooling we can share across many of our peer open source program offices,” he said.

Success comes from being open, at scale

Yahoo helped make Apache Hadoop the cornerstone of the big data revolution when it took the early code and created a team around it to help it scale to Internet-scale. They agreed to publish it all as open source. When the need for real-time processing came to the forefront, Yahoo created S4 and open sourced it too, but then discovered Storm was just published, too, and it looked more promising. The team ditched their own code and put their efforts into helping make Storm even better.  

“We applied to Apache Storm what we learned from Hadoop and S4,” Yehuda said. “Our goal was to make it great, even though it kind of competed with our own first stab.”

Storm is a success today, and the company runs it alongside Hadoop to power many of its products. They added machine learning and high-scale data serving capabilities by adding Vespa Engine, to their platforms, and then published that too. And they helped other machine learning projects scale better too, all by publishing open source.

“We’ve leveraged our expertise with Storm to help both Caffe and TensorFlow achieve better scalability. We don’t own these solutions exclusively. Rather we share our code and help others — all the while we get to leverage our expertise to build one of the industry’s most scalable platforms for our use,” he said. “This saves us money while making us a fantastic place to work on projects that impact hundreds of millions of people.”

The program office worked on strategy, legalities, and execution of these and similar projects. Leveraging open source licensing and processes effectively was a key element throughout. Now as Oath, this work continues and expands.

Yehuda cited three key lessons he learned managing an open source program:

  1. Be a service to the engineers, not a barrier.
  2. Accept that challenges will be never-ending.
  3. Run the program office like you run an open source project: Be transparent in the way decisions are made and be open to input and collaboration from everyone.

“There are so many edge cases that come up — partnerships, acquisitions, unclear contract terms — and we simply need to be open to learn, explore, and come up with an answer to every open source related question. But the most rewarding part of my job is when people tell me they joined our company because they knew about our open source friendly culture. You know, we’re always looking for open source talent, and I’m hiring into the program office.” added Yehuda.

open source reading list

Check out the list of 21 must-read books for open source program managers, recommended by members of the TODO Group.

Is your organization looking to build out an open source program or are you already managing one? If so, you’re probably already considering the kinds of tools and guidance that can make your program a holistic success. That is why, in this article series, we have been covering tools for managing open source programs and providing advice from leading experts.

Now, to take your program to the next level, we offer a free guide containing an essential open source reading list. This list can help any organization launch and maintain a thriving open source program.

Specifically, the guide provides 21 must-read books for open source program managers, recommended by members of the TODO Group. These books can help your organization build a strong foundation and avoid missteps in developing your open source program.

Advice from experts is key to running a successful open source program. “It took us years of constant discussion and negotiation to break from the traditional IT setup into a more flexible environment that supports our open source development,” said Ibrahim Haddad, Vice President of R&D and Head of the Open Source Group at Samsung Research. “We made it work for us and with enough persistence you also can make it work for your open source team.”

The book in this list provide expert advice on how to get your open source tool collection started, how to approach issues such as licensing and governance, and much more. “A well-designed open source compliance process should simultaneously ensure compliance with the terms of open source licenses and also help companies protect their own intellectual property and that of third-party suppliers from unintended disclosure and/or other consequences,” notes Haddad.

Here are just some of the titles on the essential open source reading list:

Codev2 by Lawrence Lessig: A classic treatise on Internet regulation and the role of code as a form of law

New Frontiers in Open Innovation by Henry William Chesbrough: A thorough examination of research conducted to date on open innovation

Managing 3rd-Party Software Licenses by Giles Middleton: Covers not only license types, but methods of handling and tracking components and their licenses

Open Source for Business: A Practical Guide to Open Source Software Licensing by Heather Meeker: A downloadable ebook on licensing and legal terms

Producing Open Source Software: How to Run a Successful Free Software Project by Karl Fogel: From your mission statement to project fruition, don’t miss these guidelines

The Art of Community: Building the New Age of Participation by Jono Bacon: Sound advice from one of the most respected of all community managers

The free reading list can help you navigate all kinds of common open source-related challenges. It covers everything from evaluating ROI to optimizing practices, and it explores how to seamlessly and safely leverage existing tools to complement your open source creations. It is one of a new collection of free guides from The Linux Foundation and The TODO Group that are targeted at organizations running open source programs or considering them.

The guides are available now and they can help you run an open source program office where open source is supported, shared, and leveraged. They can also, in many instances, keep your program out of trouble, where trouble can range from licensing skirmishes to lawsuits.

These free resources were produced based on expertise from open source leaders, including advice from many members of The TODO Group, which includes Autodesk, Comcast, Dropbox, Facebook, Google, Intel, Microsoft, Netflix, Red Hat, Salesforce, and Samsung.

Also, don’t miss the previous articles in the series:

How to Create an Open Source Program

Tools for Managing Open Source Programs

Measuring Your Open Source Program’s Success

Effective Strategies for Recruiting Open Source Developers

Participating in Open Source Communities

Using Open Source Code

Launching an Open Source Project: A Free Guide

Practical Ways to Improve Your Open Source Development Impact


One of the most important things when building an open source community is making sure that your own processes are open, according to Dropbox’s Luke Faraone.

The open source program at Dropbox was initially just a mailing list, where some interested engineers wanted to open source projects and develop with open source. Over time, things became more formalized, with a focus on ensuring that the company was consistent about what code it would release versus what code was best kept internal.

They also wanted to ensure that the things they were releasing were things that would actually provide value.

“We set minimum standards for what we would release as open source projects, including a review process, and our program just started to drive a lot of value,” said Luke Faraone, Security Engineer at Dropbox.

What drives Dropbox’s open source program

It’s important to ensure that the metrics and goals you track are not just related to volume, such as measuring the number of open source projects that you’re releasing or the number of lines of code you’re releasing. Those sort of metrics don’t necessarily provide business value or community value.

“We make sure to be thoughtful with our program’s goals, focusing on things that either provide back some business through external contributions or otherwise indicate that others are getting value out of our projects,” said Faraone. “We want to make sure that the community is connected back to us. Also, it is good to make sure to have fun and not have a process that is too onerous. We want people to feel comfortable working with us, and we want to be partners with folks as they work on projects. Ensuring that we have good relationships is really important.”

How Dropbox measures community success with open source

One of the most important things when building an open source community is making sure that your own processes are open.

“The more transparent you can make your decision-making processes, the more of a sense of ownership your community will have. You also want to make sure that your process doesn’t become a blocker. If your open source process for either inbound or outbound contributions is onerous, people will look to bypass the process or simply decide that contributing is too difficult,” said Faraone.

How Dropbox tracks contribution and release metrics with open source

It is important to track metrics related to contributions to projects, including such questions as:

  • What rate of contribution are you getting on a per-contributor basis?
  • Do people tend to come back to contribute to particular projects or would they also be interested in contributing to other projects that we are involved with?
  • How likely is a contributor who provides one patch to come back?

At Dropbox, according to Faraone, they also monitor the time between releases and the amount of churn that occurs between releases, where the goal is to encourage releases early and often. They also check in with teams if they have gone several months without committing to a new version.

Zulip stands out

Among Dropbox’s open source successes — if you look at the number of contributions — a project called Zulip stands out. Zulip was an open source chat system that the company acquired in 2014, but eventually they decided that they wanted to release it to the community.

“As an open source project, members of the community had set up hosting services for the chat system, and we eventually sunsetted our hosted service. We offered all of our users an opportunity to elect to have their data migrated to one of the community-operated hosting providers. What’s really impressive is that the Zulip open source project has a higher commitment velocity than it did when it had 10 or 15 employees working on it full time,” said Faraone.

Key lessons for open source program managers

Faraone offers the following tips to help ensure success when developing an open source program.

  • Community involvement can often give a project higher commitment velocity than dedicating a lot of full time employees to the project.
  • In driving community around projects, it is critical to make sure that your own processes and decisions are open and not too onerous.
  • Track metrics related to community contributions closely, including whether contributors participate in more than one project, and whether releases are arriving early and often.
  • When compared to tracking community ecosystem health and evaluating whether your program is creating business value, tracking metrics such as lines of code created has less value.
  • Evaluate whether you are choosing highly restrictive licenses, and if you are, what impact that will have as you start receiving external contributions.

You can read more TODO group case studies on GitHub.

Open Networking Summit

Speak at the largest open networking and orchestration event of 2018.

The Linux Foundation has just opened the Open Networking Summit North America (ONS NA) 2018 Call for Proposals, and we invite you to share your expertise with over 2,000 technical and business leaders in the networking ecosystem. Proposals are due by 11:59pm PT on Jan. 14, 2018.

Over 2,000 attendees are expected to attend ONS North America 2018, taking place March 26-29 in Los Angeles, including technical and business leaders across enterprise, service providers, and cloud providers. ONS North America is the only event of its kind, bringing networking and orchestration innovations together with a focus on the convergence of business (CIO/CTO/Architects) and technical (DevOps) communities.

Sign up to get the latest updates on ONS NA 2018!

Open Networking Summit NA conference tracks will include the following topical areas:

Track 1: (General Interest) Networking Futures in IoT, AI, and Network Learning. Including discussions on the progress in standards and open source interworking to drive the industry forward. We’re also seeking topics on networking as it relates to Kubernetes, cloud native, network automation, containers, microservices, and the network’s role in connected cars and connected things.

Track 2: (General Interest) Networking Business and Architecture. We’re looking for proposals on how to effectively evaluate the total cost of ownership of hybrid (public/private, SDN/NFV + traditional, proprietary/open source) environments, including acquisition strategies and good cost models for open source solutions. We’re also interested in case studies of open source business models for solution providers.

Track 3: (Technical) Service Provider & Cloud Networking. We want to hear what you have to say about the containerization of service provider workloads, multi-cloud, 5G, fog, and edge access cloud networking.

Track 4: (Business & Architecture) Service Provider & Cloud Networking. We’re seeking proposals on software-defined packet-optical, mobile edge computing, 4G video/CDN, 5G networking, and incorporating legacy systems (legacy enterprise workload migration, role of networking in cloud migration, and interworking of carrier OSS/BSS/FCAPS systems).

Track 5: (Technical) Enterprise IT & DevOps. Share your experience on scale and performance in SDN deployments, expanding container networking, maintaining stability in migration, networking needs of a hybrid cloud/virtualized environment, and figuring out the roadmap from a cost perspective.

Track 6: (Business and Architecture) Enterprise IT (CXO/IT Architects). Do you have use cases to share on IoT and networking from the retail, transportation, utility, healthcare or government sectors? We’re looking for proposals on cost modeling for hybrid environments, automation (network and beyond), analytics, security and risk management/modeling with ML, and NFV for the enterprise.

View here for more details on suggested topics, and submit your proposal before the January 14 deadline.

Get inspired! Watch presentations from ONS 2017.

See all keynotes from ONS 2017.

Not submitting but planning to attend? Register by Feb. 11 and save $800!

open source marketing

In Deirdré Straughan’s talk at Open Source Summit, she explained common marketing approaches and why they’re important for open source projects.

The widely experienced and indefatigable Deirdré Straughan presented a talk at Open Source Summit NA on how to market an open source project. Deirdré currently works with open source at Amazon Web Services (AWS), although she was not representing the company at the time of her talk. Her experience also includes stints at Ericsson, Joyent, and Oracle, where she worked with cloud and open source over several years.

Through it all, Deirdré said, the main mission in her career has been to “help technologies grow and thrive through a variety of marketing and community activities.” This article provides highlights of Deirdré’s talk, in which she explained common marketing approaches and why they’re important for open source projects.

Why you have to market free stuff

So, what is marketing? At its most basic, she said, marketing is about getting people to exchange their money for goods and services. So you might think: “Marketing is about selling. Open source is free. I don’t have to try to sell anything, so why would I need marketing?”

open source marketing

Deirdré Straughan

But, you are selling something. You are selling ideas, and the currency you are requesting in return is something extremely valuable, which is people’s time and attention. That may feel counterintuitive, because open source generally means giving something away, but it does have substance and it does have worth. In fact, it is so worthwhile  that people contribute time, money, talent, and effort to the cause. However, they can only do that if they are aware of your project and convinced of the value of supporting it.

Additionally, competition is fierce, said Deirdré. To succeed, your project must compete for attention and support with some 25 and a half million other open source projects. Thus, open source marketing is about capturing very scarce attention and resources in a very crowded environment. It’s about attracting people and resources to your project, which can be difficult to do.

According to Deirdré, the main resource projects need is people — their time and effort. They may be people who use your project, or they may be contributors. Of those who are contributors, some will work independently, often in their spare time. Others may be assigned a project by their employer, or, as is increasingly common, be specifically hired to work on a particular open source project.

“And, yes, in some cases, you are also asking for money. We would all like to believe that pure technical goodness will be rewarded, and that we should never have to think about money. However, most of us need some money to survive,” she said.

Open source is increasingly supported by companies, but many companies are unsure about which projects to invest in. To succeed, your project needs to rise above the crowd and to attract not just independent contributors, but also companies that could offer material support.

Common points of failure in marketing

“Even so, marketing often fails to happen in open source. A common reason is that many people in tech despise marketing. But you shouldn’t automatically recoil from the mere mention of marketing, because you need to be doing it if you want to survive. It will be difficult to do marketing well, if you go into it thinking it’s sleazy,” Deirdré said.

Sometimes resistance to marketing comes from a literal machismo, according to Deirdré. Marketing is considered a soft skill, a job for women, as opposed to the (ahem) “manly” work of coding. It is perceived as a lower-status role (until you get to the VP or CMO level). Other reasons for lack of marketing involve lack of funding, or simply the fact that nobody working on a project happens to know how to do it.

At its best, Deirdré said, marketing helps people understand what the technology is about, and how they can use it. It is a form of  communication that is informative, truthful, convincing, and even inspiring.

Marketing tools

There are many marketing tools readily available. First in importance, Deirdré said, is your code. GitHub is your resumé. Your basic code should be architectured purposefully and offer the capability to write libraries or modules so that the barriers to entry for a newcomer are fairly low. It should be well coded and offer tools that help people learn to use and contribute to your project.  

A common pitfall relates to documentation. Many companies don’t bother with it, but documentation will help attract people to your project. Documentation usually explains all the commands and parameters and what the output means. This information is necessary, but insufficient. Additional types of documentation are needed, according to Deirdré, such as, white papers, blogs, video, podcasts, and conference talks.

Once you’ve created all this content, you need a place to put it. Obviously, a GitHub repo is necessary, but you’ll also need a website and/or wiki.

Discoverability is crucial, Deirdré said. You have created all this content, but people still have to find it. Toward that end, you should be cautious about project names. For example, if your project name is also a common word, searching for it is going to be difficult. To maximize results in a search engine, you can use keyword tags and categories that will help people find your project.

Search engine optimization is an arcane art. Being on the first page of search results for a keyword is extremely valuable. For that reason, “SEO best practice changes frequently, as search engines are in an arms race with the black hats who want to game search results,” she said. “You can easily find recent tips and tricks on how to improve your rankings. However, it usually takes about a year to make any real progress in search engine rankings. You’ll need patience.”


Everything that touches the customer is marketing, Deirdré said. For example, consider airlines. Everything about the airline experience affects what consumers  think about the airline. From buying a ticket, the check-in process, boarding, the plane ride and experience, the atmosphere of the airport, timeliness in departures and arrivals, and whether luggage arrived on time and unscathed — all of these processes and experiences help shape the consumer’s opinion of the brand.

“This is also true for technology, and especially for communities and projects. Everything that somebody experiences around your project — good or bad — affects their perception of that project and whether they are going to want to participate in it,” she said.

So, community is important. Community culture is important, as is diversity.  Nurture your community. If your open source community is not diverse, ask yourself why, and think about how you can attract a wider range of participation.

Diversity also means diversity of contribution. Does your project recognize and value contribution beyond just the code? Again, you’re asking people to help you do this work, so make sure that they’re recognized for it.

Kindness also matters

Look closely at the newbie experience. What is it like onboarding someone to your technology? Think, too, about growing pains. Projects, like startups, can reach a critical inflection point, when there is rapid success but things start to fall apart, because there just aren’t enough people to respond quickly.

“In conclusion, I’d like you to take away that marketing is not evil. You may already be doing it. You just may not think of some of what you’re doing as marketing,” Deirdré said.

“And marketing, particularly that which is appropriate for open source, is mostly stuff you’re probably already doing, or at least know how to do. There are even people out there who would love to help. They’re just waiting to be asked.”

Deirdré Straughan is the Content Lead for the AWS Open Source Community Engagement team. Her work for AWS includes the new AWS Open Source blog and @AWSOpen on Twitter. You can find her at @deirdres on Twitter.



“Bell has been engaged in the ONAP journey from day one and committed to get it to production to demonstrate its value,” said Tamer Shenouda, Director of Network Transformation for Bell.

Bell, Canada’s largest communications company, is the first in the world to deploy the open source version of the Open Network Automation Platform (ONAP) in production. Bell has built the capability to automate its data center tenant network provisioning on top of the ONAP Platform, providing its operations teams with a new tool to improve efficiency and time to market. This is the first step in using ONAP as a common platform across Bell’s networks on its journey towards a multi-partner DevOps model.

As part of the company’s Network 3.0 transformation initiative, Bell and its partners used Agile delivery to launch a minimum viable product with the platform and will continue to adapt it to ensure that it best supports the needs of Bell customers. This significant development sends a clear message to the industry that ONAP is ready and usable, and that carriers don’t need to implement all ONAP components from day one to start production. Bell has also leveraged the capabilities of ONAP Operations Manager to simplify deployments, drastically reduce footprint and enable continuous delivery.

“Bell has been engaged in the ONAP journey from day one and committed to get it to production to demonstrate its value,” said Tamer Shenouda, Director of Network Transformation for Bell. “This demonstration will encourage other partners to take a similar incremental approach in delivery and operations of the platform, and we look forward to other telecoms launching ONAP to production.”

ONAP is a Linux Foundation project that unites two major open networking and orchestration projects – Open Source ECOMP and the Open Orchestrator Project (OPEN-O). ONAP brings together top global carriers and vendors, using shared knowledge to build a unified architecture that allows any network operator to automate, design, orchestrate and manage services and virtual functions.

“We’re very proud to be the first member of the ONAP Project to demonstrate the viability of the platform live on our network,” said Petri Lyytikainen, Bell’s Vice President, Network Strategy, Services and Management. “The evolution of our advanced software-defined networks will enable us to respond even faster to the unique needs of our customers.” 

Bell is a founding Platinum Member of ONAP. Platinum members include: Amdocs, AT&T, China Mobile, China Telecom, Cisco, Cloudify, Ericsson, Huawei, IBM, Intel, Jio, Nokia, Orange, Tech Mahindra, Türk Telekom, Vmware, Vodafone, and ZTE.

This free guide can help you increase your development team’s efficacy through and with open source contributions.

Open source programs are sparking innovation at organizations of all types, and if your program is up and running, you may have arrived at the point where maximizing the impact of your development is essential to continued success. Many open source program managers are now required to demonstrate the ROI of their technology development, and example open source report cards from Facebook and Google track development milestones.

This is where the new, free Improving Your Open Source Development Impact guide can help. The aim of the guide is to help you increase your development team’s efficacy through and with open source contributions. By implementing some of the best practices laid out in the guide, you can:

  • Reduce the amount of work needed from product teams
  • Minimize the cost to maintain source code and internal software branches
  • Improve code quality
  • Produce faster development cycles
  • Produce more stable code to serve as the base for products
  • Improve company reputation in key open source communities.

Open source development requires a different approach than many organizations are accustomed to. But the work becomes easier if you have a clear plan to follow. Fortunately, a whole lot of companies and individuals have already forged a path to success in contributing to significant open source projects. They have tried and true methods for establishing a leadership role in open source communities.

This open source guide offers lessons for increasing open source development impact through specific examples. Contributing to the Linux kernel is one of the hardest challenges for open source developers. With that in mind, the guide uses this case as an example, but the lessons learned will apply to nearly any open source project you’ll work with.

“It took us years of constant discussion and negotiation to break from the traditional IT setup into a more flexible environment that supports our open source development,” said Ibrahim Haddad, Vice President of R&D and Head of the Open Source Group at Samsung Research. “We made it work for us and with enough persistence you also can make it work for your open source team.”

Common Challenges

Notably, organizations run into common problems as they try to improve the impact of their open source inventions. The figure below shows some of the challenges that dedicated open source teams face in an enterprise source guidesThe Improving Your Open Source Development Impact guide can help you navigate these and other common open source-related challenges. It covers everything from evaluating ROI to optimizing practices, and it explores how to seamlessly and safely leverage existing tools to complement your open source creations.

It is one of a new collection of free guides from The Linux Foundation and The TODO Group providing valuable insight and expertise for any organization running an open source program. The guides are available now to help you run an open source program office where open source is supported, shared, and leveraged.

Check out the all the guides, and don’t miss the previous articles in the series:

How to Create an Open Source Program

Tools for Managing Open Source Programs

Measuring Your Open Source Program’s Success

Effective Strategies for Recruiting Open Source Developers

Participating in Open Source Communities

Using Open Source Code

Launching an Open Source Project: A Free Guide


OpenChain makes open source compliance more predictable, understandable, and efficient for all participants in the software supply chain.

Communities form in open source all the time to address challenges. The majority of these communities are based around code, but others cover topics as diverse as design or governance. The OpenChain Project is a great example of the latter. What began three years ago as a conversation about reducing overlap, confusion, and wasted resources with respect to open source compliance is now poised to become an industry standard.

The idea to develop an overarching standard to describe what organizations could and should do to address open source compliance efficiently gained momentum until the formal project was born. The basic idea was simple: identify key recommended processes for effective open source management. The goal was equally clear: reduce bottlenecks and risk when using third-party code to make open source license compliance simple and consistent across the supply chain. The key was to pull things together in a manner that balanced comprehensiveness, broad applicability, and real-world usability.

Main Pillars of the Project

The OpenChain Project has three pillars supported by dedicated work teams. The OpenChain Specification defines a core set of requirements every quality compliance program must satisfy. OpenChain Conformance allows organizations to display their adherence to these requirements. The OpenChain Curriculum provides the educational foundation for open source processes and solutions, while meeting a key requirement of the OpenChain Specification. The result is that open source license compliance becomes more predictable, understandable, and efficient for all participants in the software supply chain.

Reasons to Engage

The OpenChain Project is designed to be useful and adoptable for all types of entities in the supply chain. As such, it is important to distill its value proposition for various potential partners. Our volunteer community created a list of five practical reasons to engage:

  1. OpenChain makes free and open source software (FOSS) more accessible to your developers. OpenChain provides a framework for shared, compliant use of FOSS. Conforming companies create an environment that supports use of FOSS internally and sharing of FOSS with partners.
  2. OpenChain reduces overall compliance effort, saving time and legal and engineering resources. OpenChain allows companies in a supply chain to work together toward FOSS compliance and provides a consistent standard to which all must perform. By contrast, in a typical supply chain, each member of the chain has to perform FOSS compliance for software of others in the chain, wasting time and resources in a duplication of effort.
  3. OpenChain may be adapted to your existing systems. OpenChain allows you to choose your own processes to meet its requirements. OpenChain provides resources that help you design new processes from the ground up, or you may choose to use the systems you have in place.
  4. OpenChain helps your business teams work together toward a common goal. OpenChain provides a blueprint for your legal, engineering, and business teams to work together toward FOSS compliance.
  5. OpenChain allows you to conform to a stable, community-backed specification. When you adopt OpenChain, you conform to a stable specification that is widely backed by industry and community participants. OpenChain was developed in an open, collaborative process, with contributors from a wide range of industries across Asia, Europe and North America. OpenChain is being formally adopted by a growing number of both small and larger companies.

Today, the OpenChain Project is addressing its goals and moving towards wider market adoption with the support of 14 Platinum members: Adobe, Arm, Cisco, Comcast, GitHub, Harman, Hitachi, HPE, Qualcomm, Siemens, Sony, Toyota, Western Digital, and Wind River. The project also has a broad community of volunteers helping to make open source compliance easier for a multitude of market segments. As we move into 2018, the OpenChain Project is well positioned for adoption by Tier 1, Tier 2, and Tier 3 suppliers in multiple sectors, ranging from embedded to mobile to automotive to enterprise to infrastructure.

Entities of all sizes are welcome to participate in the OpenChain Project. Everyone is welcome and encouraged to join our mailing list at:

You can also send private email to the Project Director, Shane Coughlan, at

Mauro Carvalho Chehab answers a few questions about his work on the Linux kernel.

According to the recent Linux Kernel Development Report, the Linux operating system runs 90 percent of the public cloud workload, has 62 percent of the embedded market share, and 100 percent of the TOP500 supercomputers. It also runs 82 percent of the world’s smartphones and nine of the top ten public clouds. However, the sustained growth of this open source ecosystem would not be possible without the steady development of the Linux kernel.

In this series, we are highlighting the ongoing work of some Linux kernel contributors. Here, Mauro Carvalho Chehab, Open Source Director at Samsung Research Brazil, answers a few questions about his work on the kernel.

Linux Foundation: What role do you play in the community and what subsystem(s) do you work on?

I’m responsible for the Open Source efforts at Samsung Research Brazil, as part of Samsung’s Open Source Group. I maintain the media and EDAC (Error Detection and Correction) kernel subsystems.

Linux Foundation: What have you been working on this year?

This year, I did a lot of patches that improves Linux documentation. A lot of them were related to the conversion from the XML-based DocBook docs to a markup language (Restructured Text). Thanks to that, no documents use the legacy document system anymore. I also finally closed the documentation gap at the DVB API, with was out of sync for more than 10 years! I also did several bug fixes at the media subsystem, including the 4.9 breakage of many drivers that were doing DMA via stack.

Linux Foundation: What do you think the kernel community needs to work on in the upcoming year?

We should continue our work to support new device drivers and get rid of out of tree stuff. At the media subsystem, we should work to add support for newer TV standards, like ATSC version 3 and to improve support for embedded systems, on both DVB and V4L2 APIs.

Linux Foundation: Why do you contribute to the Linux kernel?

Because it is fun! Seriously, I strongly believe that the innovation process on computer engineering is currently driven by Linux. Working on its kernel has provided me the opportunity of working with great developers and helping to improve the top operating system.

You can learn more about the Linux kernel development process and read more developer profiles in the full report. Download the 2017 Linux Kernel Development Report now.

open source culture

Open source involves a culture of understanding change. It’s about evolution as a group, says Mesosphere’s CMO Peter Guagenti.

In the early days of open source, one of the primary goals of the open source community was educating people about the benefits of open source and why they should use it. Today, open source is ubiquitous. Almost everyone is using it. That has created a unique challenge around educating new users about the open source development model and ensuring that open source projects are sustainable.

Peter Guagenti, CMO at Mesosphere, Inc.

Peter Guagenti, the Chief Marketing Officer at Mesosphere, Inc., has comprehensive experience with how open source works, having been involved with several leading open source projects. He has been a coder, but says that he considers himself a hustler. We talked with him about his role at Mesosphere, how to help companies become good open source citizens, and about the role of culture in open source. Here is an edited version of that interview.

The Linux Foundation: What’s the role of a CMO in an open source software company?

Peter Guagenti: The role of a CMO in a software company is fundamentally different from that in any other category.  We have a really interesting role in marketing and technology, and it’s one of education and guidance. There used to be a place 20 years ago where, as a marketer, you would come up with a simple pithy message and buy a bunch of advertising and people would believe it.

That’s not true anymore. Now we have to position ourselves alongside the architectures and the thought leadership that our customers are interested in to prove our value.

The Linux Foundation: Can you explain more about this approach?

Guagenti: I love that instead of focusing on marketing taglines, you really have to know the technology so customers have the confidence that they will get the support we promise. Since this space is changing so quickly, we spend probably half our time simply on educating and informing about the market and the challenges that customers face.

I don’t think about talking about DCOS, for example; I think about how connected cars are really important but nobody really knows how to build them. We serve six of the largest car makers in the world. So getting them to talk about how they’re approaching this problem — what they think about Edge computing, what they think about computing in the car, or what they think about data and moving that data around. These are the real exciting things.

The Linux Foundation: Can you talk about other work you have done in open source?

Guagenti:  I’m a long-time open source advocate. I’ve been in open source for over 10 years. I built an open source services practice in a large digital agency called Razorfish when I was at a client services there. I’ve spent time at three open source companies: Acquia, which is in the Drupal open source project; Nginx, which is the world’s most popular web server and application delivery controller; and now I am at Mesosphere, the container company.

The Linux Foundation: Open source has become the de facto software development model — almost everyone is consuming open source these days. That creates a new challenge as many new consumers don’t fully understand how open source works, which can lead to problems like not being part of the ecosystem and creating technical debt. Have you come across this problem?

Guagenti: Open source has evolved dramatically over the past 20 years. I would argue 10 years ago you were crazy if you were a Fortune 500 company and you were the CIO and said I’m going to integrate open source everywhere. But now open source is the default. I’ve worked in large state and national governments around the world. I’ve worked in the Fortune 500, and they all have adopted open source. But how they adopt open source successfully is different. If you look company by company, if you look at projects, there is a difference.

There are community-driven models, there are corporate-driven models, and there are things in between where you see things like Kubernetes, where you’ve multiple companies contributing at scale. There is a great mix, but companies don’t always know how to make the best use of that. It becomes critical for them to find the right enterprise that helps them understand how to use and deploy it. More important than that is to help them ensure they are making good decisions with that software and driving the roadmap forward by contributing or at least by being a voice in that.

We take for granted that open source exists, but open source requires involvement—either contribution of code or cash—to keep those projects healthy. We are at a point where open source has been around long enough that we have seen early open source projects just die because they didn’t have core maintainers able to earn a salary.

I was told that every great technology company needs a hacker and a hustler. I was a good coder early on, but I wasn’t great. I’m more of a hustler. I loved being able to see businesses build around open source and then have have that really be the heart of a healthy ecosystem where everyone is able to benefit from that code.

The Linux Foundation: What role does culture play in open source adoption?

Guagenti: It matters. Look at the digital transformation that we have been going through for the last 20 years. Look at the companies that have done it best. You will notice that the old stalwarts have now reinvented themselves in a meaningful way. They are continuing to evolve with the time and are competing effectively. They had a culture where they could embrace and accept a lot of these things.  

If you look at hiring the great technology talent, what’s the number one thing great technology talent expects? They want to work with the tools they want to use. They want to do it in a way that fits their pattern of behavior, their pattern of building these things. It’s not the money, it’s not the stock options, it’s not the fancy work. It’s about the kind of work I want to do everyday and and the way I want to do it.  

I work with some of the largest banks, I work with some of the largest government entities. What I have noticed, with some of the most successful ones, is that they have a culture internally where they understand this stuff. They understand what it means to not just use open source but to be a part of an open source community. Sometimes you do run into hurdles. I work with a lot of large companies that are either not comfortable contributing code back or just simply don’t feel they have the time to do it. But they do their bit in a different way; they may do things like contribute  financially to projects, send people to to events, or actually go and tell their story.

That’s what we do a lot at Mesosphere. Since this space is changing, we love having our largest customers talking about what they’re doing with open source. Their culture matters because it’s not just the culture of open source and using open source. It’s a culture of innovation. It’s a culture of understanding change.  And that’s what open source is all about. It’s about evolution as a group.

Learn more about best practices for sustainable open source in the free Open Source Guides for the Enterprise from The Linux Foundation.