Power

Google will give up direct control of the Knative open-source project

Under an agreement recently approved by the Knative leadership team, the project will transition to a governance structure in which no single vendor will be able to occupy a controlling number of seats, Protocol has learned.

Google's Thomas Kurian

Knative was designed to let developers run so-called "serverless" applications on top of Kubernetes, the container-management platform service originally developed at Google and open-sourced in 2015.

Photo: Bloomberg via Getty Images

Google and its partners on Knative, a key cloud open-source project controlled by Google until very recently, plan to announce sweeping changes to the project's governance structure on Thursday, Protocol has learned.

The new changes are part of many twists and turns in Google's enterprise open-source strategy over the past year, which have angered and confused some of its partners. This time, Google is relinquishing direct control of a popular open-source project: Later this year Knative will implement a steering committee structure in which no single vendor can hold more than two seats on a five-seat committee, according to a blog post released late Thursday, after this report was published.

Individuals will now hold seats on the Knative steering committee rather than vendors, and elections will be held later this year to select two new members. The committee, which sets the overall direction for the project, could expand to as many as seven members in the future to include representatives from the end-user community.

Knative was designed to let developers run so-called "serverless" applications on top of Kubernetes, the container-management platform service originally developed at Google and open-sourced in 2015. The idea is to give companies a way to take advantage of the speed and cost-efficiency of serverless applications — which can automatically scale in response to events without having to manually spin up additional computing resources — while using the deployment flexibility that applications built around containers enjoy.

It's a central link between Kubernetes and Istio, another open-source project developed by Google. For years, partners and contributors to both projects, which include companies like IBM, VMware and Lyft, had expected Google to transfer operational control of Istio and Knative to a foundation like the Cloud Native Computing Foundation, which was created to manage the development of Kubernetes.

But last year Google told Knative contributors directly that it had no plans to transfer it to a foundation, and trickled out news of similar plans for Istio in smaller groups over the end of 2019. At the time, Google controlled a voting majority of the seats on both projects, a troubling development for open-source community members who believed that the neutrality of Kubernetes was one of the greatest reasons for its success.

Google tried to address some of those concerns earlier this year with the Open Usage Commons, which the company said would manage trademark policies around key projects including Istio. The Knative project is setting up a similar committee within the project to manage trademark use, which is an important consideration for companies that are building services around open-source projects.

Google's open-source strategy has waxed and waned since the release of Kubernetes, but for a very long time the company was considered one of the friendliest megacorporations in the open-source community. That perception started to change under Google Cloud CEO Thomas Kurian, as a contingent within the company that believed it was a strategic mistake to give up control of Kubernetes started to gain traction.

The changes to Knative's governance structure should mollify some of those critics, and follow similar moves undertaken by Istio in August. It could also spread adoption of the project, now that other cloud vendors understand that a rival won't exert overall control over the direction of the project.

Protocol | Workplace

Introducing Protocol’s Diversity Tracker

Tech companies talk a good game on diversity. Our new tracker shows where there's progress – and where there isn't.

Our tracker contains historical and current diversity data for the most powerful tech companies.
Illustration: Christopher T. Fong/Protocol
Protocol team

A new media company from the publisher of POLITICO reporting on the people, power and politics of tech.

If you've ever tried to pick up a new fitness routine like running, chances are you may have fallen into the "motivation vs. habit" trap once or twice. You go for a run when the sun is shining, only to quickly fall off the wagon when the weather turns sour.

Similarly, for many businesses, 2020 acted as the storm cloud that disrupted their plans for innovation. With leaders busy grappling with the pandemic, innovation frequently got pushed to the backburner. In fact, according to McKinsey, the majority of organizations shifted their focus mainly to maintaining business continuity throughout the pandemic.

Keep Reading Show less
Gaurav Kataria
Group Product Manager, Trello at Atlassian
Protocol | Workplace

Productivity apps can’t stop making money

ClickUp had one of the biggest Series C funding rounds ever. Here's how it matches up to the other productivity unicorns.

ClickUp made $400 million in its series C funding round.

Photo: ClickUp

Productivity platform ClickUp announced a milestone today. The company raised $400 million, which is one of the biggest series C funding rounds in the workplace productivity market ever. The round, led by Andreessen Horowitz and Tiger Global, put the private company at a $4 billion valuation post-money.

In case it's not clear: This is a massive amount of money. It shows how hot the productivity space is right now, with some predicting the market size could reach almost $120 billion by 2028. In a world of hybrid workers, all-in-one tool platforms are all the rage among both startups and productivity stalwarts. Companies everywhere want to escape tool overwhelm, where work is spread across dozens of apps.

Keep Reading Show less
Lizzy Lawrence

Lizzy Lawrence ( @LizzyLaw_) is a reporter at Protocol, covering tools and productivity in the workplace. She's a recent graduate of the University of Michigan, where she studied sociology and international studies. She served as editor in chief of The Michigan Daily, her school's independent newspaper. She's based in D.C., and can be reached at llawrence@protocol.com.

The Supreme Court of the United States
Photo: Angel Xavier Viera-Vargas

If a company resolved a data breach in the past, does it need to disclose the potential negative fallout of that breach as a risk to investors later on? In a new petition asking the Supreme Court to take up the question, Alphabet is arguing emphatically: no. And it's using the ol' "the past is history, tomorrow's a mystery" defense.

Keep Reading Show less
Issie Lapowsky

Issie Lapowsky ( @issielapowsky) is Protocol's chief correspondent, covering the intersection of technology, politics, and national affairs. She also oversees Protocol's fellowship program. Previously, she was a senior writer at Wired, where she covered the 2016 election and the Facebook beat in its aftermath. Prior to that, Issie worked as a staff writer for Inc. magazine, writing about small business and entrepreneurship. She has also worked as an on-air contributor for CBS News and taught a graduate-level course at New York University's Center for Publishing on how tech giants have affected publishing.

Protocol | Workplace

Facebook’s hiring crisis: Engineers are turning down offers

"All of you are now starting to experience that major imbalance between supply and demand — and it doesn't feel good," a recruiting leader wrote in an internal memo.

Here are all the Facebook Papers stories
Image: Getty Images, Protocol

Facebook cannot find enough candidates to meet engineering demand, especially in the Bay Area, and has struggled and failed to meet early 2021 recruiting goals, according to a detailed internal memo outlining recruitment strategy and hiring pains.

The company also failed to meet hiring goals in 2019, which frustrated CEO Mark Zuckerberg, and it built an ad-hoc team of leaders to create an emergency plan to address the painful shortage, according to disclosures made to the Securities and Exchange Commission and provided to Congress in redacted form by Frances Haugen's legal counsel. A consortium of news organizations, including Protocol, has reviewed the redacted versions received by Congress.

Keep Reading Show less
Anna Kramer

Anna Kramer is a reporter at Protocol (Twitter: @ anna_c_kramer, email: akramer@protocol.com), where she writes about labor and workplace issues. Prior to joining the team, she covered tech and small business for the San Francisco Chronicle and privacy for Bloomberg Law. She is a recent graduate of Brown University, where she studied International Relations and Arabic and wrote her senior thesis about surveillance tools and technological development in the Middle East.

Latest Stories