NGINX Community Blog

NGINX and F5: Our Continued Commitment to Open Source

—

by

Gus Robertson

Last week, we announced that F5 will be acquiring NGINX. The response has been overwhelmingly positive from customers, the community, partners, employees, and throughout the industry. It’s humbling and we thank everyone for their ongoing support of NGINX.

But we also heard loud and clear: F5 and NGINX need to continue demonstrating our joint commitment to open source.

Let me explain what we’re doing. I’d like to hear from you if we’re not meeting expectations.

NGINX and F5 Are Committed to NGINX Open Source

Let me take a moment to be very explicit: F5 is committed not only to supporting the development of NGINX Open Source and other NGINX open source projects, but to increasing investment over time.

Just to repeat that. F5 is committed to the NGINX open source technology, developers, and community.

I mentioned this in my blog post about the acquisition. F5 CEO François Locoh-Donou mentioned it in his open letter to F5 employees. And numerous articles have covered the F5 promise to be a good steward of NGINX Open Source, including Computer Business Review, Business Insider, CRN, ZDNet, and The New Stack.

We’re also seeing increased acceptance of mainstream companies as stewards of open source technologies. Recently Microsoft bought GitHub. VMware bought Heptio. And IBM bought Red Hat. The assumption that Big-Fish-Eats-Little-Fish means Big-Fish-Kills-Open-Source-Project is outdated thinking. The companies acquiring open source technologies are spending large amounts of cash to create value, not destroy it.

If software is eating the world, then open source is eating software. Open source is a huge driver of software innovation and powers the most compelling applications and digital services on the planet. It’s a key resource and a large part of what attracted F5 to NGINX. Trust me when I say that neither NGINX nor F5 wants to destroy the value the NGINX team spent 15 years creating.

On second thought, I’ve changed my mind. . .don’t trust me. Watch us instead! When we announced NGINX Plus in 2013, members of the open source community expressed the same concerns as they are now. Since then we have delivered new features and capabilities in NGINX Open Source every month. We added TCP, UDP, gRPC, and HTTP/2 capabilities, to name just a few.

We’re Committed to a Full NGINX Open Source Roadmap

To date, we’ve delivered a massive amount of new capabilities into NGINX Open Source. Our goal is that NGINX Open source continues to be the most powerful and flexible web server, reverse proxy, and content cache available. We proudly develop these use cases as first‑class capabilities in the open source project. We’ve also launched NGINX Unit as a new open source application server, and continued work on other open source projects.

In 2018 alone, we delivered key new features in 32 open source releases:

And we’re not stopping there. Our plan for 2019 is to accelerate open source development with even more capabilities. Notable roadmap items include:

  • NGINX – QUIC and HTTP/3 implementations, as well as support for asynchronous file open
  • NGINX Unit – Java servlet containers, proxying capabilities, static file support
  • njs – Support for JavaScript modules (import/export) and deeper NGINX integrations

All said and done, we expect to make 30+ releases of open source software during 2019, with updates to the NGINX Open Source mainline continuing at the established cadence of a release every six weeks.

In addition to features and project development, we’re also keeping NGINX Conf, our annual user event. We expect more than half of this year’s speakers to come from the community and discuss open source use cases. Keep an eye out for the call for papers and save the date: September 10–11 in Seattle.

Can’t wait until September? Join one of our monthly meetups! In February we hosted Gremlin to talk chaos engineering, and our own Faisal Memon updated attendees on NGINX Open Source. Next up, we’re doing a deep dive on NGINX Unit.

We’re Committed to Maintaining, and Even Increasing, Resources

We anticipate that the additional resources F5 brings to bear will enable us to develop more open source features, host more open source events, and produce more open source content than we can now. In fact, already F5 has committed to:

  1. Migrate the NGINX development team. NGINX co‑founders Igor Sysoev and Maxim Konovalov are joining F5, along with the core open source development team.
  2. Continue supporting users. We’ll continue staffing the open source mailing list and providing detailed release notes.
  3. Maintain nginx.org. We will keep the name of the project, along with the nginx.org website and all the valuable documentation on docs.nginx.com.
  4. Keep the NGINX repositories. We’ll continue to check our great software into Mercurial and mirror it to GitHub. Even your favorite Linux distros will still have NGINX.
  5. Develop other NGINX open source projects. We will continue newer open source projects, like NGINX Unit and the Kubernetes Ingress Controller.

What excites me the most, though, is the potential to increase investment in our open source capabilities. By that I mean that after the deal closes, F5 will help us:

  • Hire more developers to write great code
  • Build a team of community managers to strengthen our presence
  • Develop more evangelists to share the value of NGINX around the world
  • Create even more content on NGINX software, tips, tricks, and best practices
  • Do more of the things that made NGINX so great, and do them faster

Stay Tuned for More Exciting Open Source Evolution

I believe words are cheap and actions matter more. I think you’ll find both NGINX and F5 are committed to making sure that NGINX Open Source not only survives, but thrives.

As we find new and powerful ways to combine F5 and NGINX technology, people, and resources, we’re confident that you’ll see an accelerated pace in NGINX open source projects.

Watch this space. We’ve got great things planned and look forward to even more community engagement than before.