opentf.org Open in urlscan Pro
2606:50c0:8002::153  Public Scan

Form analysis
0 forms found in the DOM

Text Content

THE OPENTF MANIFESTO

Terraform was open-sourced in 2014 under the Mozilla Public License (v 2.0) (the
“MPL”). Over the next ~9 years, it built up a community that included thousands
of users, contributors, customers, certified practitioners, vendors, and an
ecosystem of open-source modules, plugins, libraries, and extensions. Then, on
August 10th, 2023, with little or no advance notice or chance for much, if not
all, of the community to have any input, HashiCorp switched the license for
Terraform from the MPL to the Business Source License (v1.1) (the “BUSL”), a
non-open source license. In our opinion, this change threatens the entire
community and ecosystem that's built up around Terraform over the last 9 years.

Our concern: the BUSL license is a poison pill for Terraform.

Overnight, tens of thousands of businesses, ranging from one-person shops to the
Fortune 500, woke up to a new reality where the underpinnings of their
infrastructure suddenly became a potential legal risk. The BUSL and the
additional use grant written by the HashiCorp team are vague, and now every
company, vendor, and developer using Terraform has to wonder whether what they
are doing could be construed as competitive with HashiCorp's offerings. The FAQ
provides some solace for end-customers and systems integrators today, but even
if you might be in the clear now, how can you build confidence that your usage
won't violate the license terms in the future? What if your products or
HashiCorp's products change? What if HashiCorp changes how they interpret
competitive? What if they change the license again? As a result, everything that
uses Terraform is on shaky ground.

It is clear to us that under the new license, the thriving ecosystem built up
around the open source Terraform will dwindle and wither. As developers consider
what tools to learn and what ecosystems to contribute to, and as companies
consider what tools to use to manage their infrastructure, more and more,
they'll pick alternatives that are genuinely open-source. Existing Terraform
codebases will turn into outdated liabilities, independent tooling will all but
disappear, and the community will fracture and disappear.

This sort of change also harms all similar open-source projects. Every company
and every developer now needs to think twice before adopting and investing in an
open-source project in case the creator suddenly decides to change the license.
Imagine if the creators of Linux or Kubernetes suddenly switched to a
non-open-source license that only permitted non-competitive usage.

We believe that the essential building blocks of the modern Internet, such as
Linux, Kubernetes, and Terraform need to be truly open source: that is the only
way to ensure that we are building our industry on top of solid and predictable
underpinnings.

Our goal: ensure Terraform remains truly open source—always.

Our aim with this manifesto is to return Terraform to a fully open source
license. BSL is not open source, so this would mean moving Terraform back to the
MPL license, or some other well-known, widely accepted open source license
(e.g., Apache License 2.0). Moreover, we want to be confident that Terraform
will always remain open source, so you don't have to worry about another sudden
license change putting everything at risk.

Our request to HashiCorp: switch Terraform back to an open source license.

We ask HashiCorp to do the right thing by the community: instead of going
forward with the BUSL license change, switch Terraform back to a truly open
source license, and commit to keeping it that way forever going forward. That
way, instead of fracturing the community, we end up with a single, impartial,
reliable home for Terraform where the whole community can unite to keep building
this amazing ecosystem.

Our fallback plan: fork Terraform into a foundation.

If HashiCorp is unwilling to switch Terraform back to an open source license, we
propose to fork the legacy MPL-licensed Terraform and maintain the fork in the
foundation. This is similar to how Linux and Kubernetes are managed by
foundations (the Linux Foundation and the Cloud Native Computing Foundation,
respectively), which are run by multiple companies, ensuring the tool stays
truly open source and neutral, and not at the whim of any one company.

In particular, we want to create a foundation for Terraform that is:

 * Truly open source - under a well-known and widely-accepted license that
   companies can trust, that won't suddenly change in the future, and isn't
   subject to the whims of a single vendor
 * Community-driven - so that the community governs the project for the
   community, where pull requests are regularly reviewed and accepted on their
   merit
 * Impartial - so that valuable features and fixes are accepted based on their
   value to the community, regardless of their impact on any particular vendor
 * Layered and modular - with a programmer-friendly project structure to
   encourage building on top, enabling a new vibrant ecosystem of tools and
   integrations
 * Backwards-compatible - so that the existing code can drive value for years to
   come


CONTACT US

If you are a member of the community, a member of the press, an employee of
HashiCorp, or anyone else with questions or feedback to share, you can reach the
team behind this manifesto by emailing us at pledge@opentf.org.

Join our Reddit community!


SHARE




FREQUENTLY ASKED QUESTIONS

Is OpenTF going to be a foundation?

We strongly prefer joining an existing reputable foundation over creating a new
one. Stay tuned for additional details in the coming week.

Can anyone pledge?

Yes, the pledge is open to both all individuals and all companies who care about
the future of Terraform. You can also support this initiative by staring this
manifesto repository on GitHub and spreading the word via share buttons.

I'm a regular Terraform user and I'm not competing with HashiCorp. Why should I
care?

How do you know you're not competing with HashiCorp?

That's not meant to be a redundant or snarky question. The key issue with the
BSL is that the wording is intentionally vague. What does "competing" mean? What
does "hosting or embedding" mean? Who decides?

The answer to all these questions is that, in order to really know if you're a
competitor, you have to reach out to HashiCorp. So whether your usage is valid
is not controlled by the terms of the license, but is instead entirely at the
whim of HashiCorp. They get to decide on a case by case basis who is and who
isn't a competitor—and they can change their mind at any time.

That is very shaky footing on which to build anything.

At every company you ever work at in the future, before starting to use
Terraform, the CTO will have to think about whether HashiCorp could possibly
consider you a competitor, now, or at any time in the future. The legal team at
that company will have to wonder if they want to take the risk of allowing a BSL
license, or if they should ban it due to all the uncertainty. Every developer at
that company will have to wonder if they want to contribute back to Terraform,
given there's no certainty they'll be able to use their own work at a future
job.

In short, the BSL is a poison pill for the entire Terraform community.

Doesn't forking hurt the whole community? Why take such a brash action?

Terraform was under the MPL license for ~9 years. This created an
understanding—an implicit contract—that Terraform is open source and you can use
it for just about anything you want. Based on that understanding, tens of
thousands of developers adopted the tool, and contributed back to it. HashiCorp
even had all contributors sign a CLA which explicitly said (link to the CLA in
the Internet Archive as HashiCorp has of course removed this wording):

> HashiCorp is committed to having a true Free and Open Source Software (“FOSS”)
> license for our non-commercial software. A CLA enables HashiCorp to safely
> commercialize our products while keeping a standard FOSS license with all the
> rights that license grants to users: the ability to use the project in their
> own projects or businesses, to republish modified source, or to completely
> fork the project.

The move to BSL—which is not a free and open source license—broke the implicit
contract. That was the brash action!

Terraform would've never gotten the adoption it did, or all the contributions
from the community, had it not been open source. Most of us would've never
agreed to the CLA to contribute to the project if it was BSL licensed. Taking
all those contributions and all that community trust, and then changing to the
BSL license is a bait and switch.

The OpenTF manifesto is about undoing those changes! It's about going back to
the way Terraform was for the first ~9 years: as a truly open source tool that
we can all trust, contribute to, and use as we wish.

Didn't HashiCorp adopt BSL to deter vendors who were using Terraform but not
contributing back?

In the blog post where HashiCorp announces the switch to BSL, they justify the
license switch as a response to the following:

> However, there are other vendors who take advantage of pure OSS models, and
> the community work on OSS projects, for their own commercial goals, without
> providing material contributions back. We don’t believe this is in the spirit
> of open source.

This is inaccurate and misleading. First of all, many of the vendors affected by
the change to BSL have made considerable contributions to the Terraform
community. Here are just a handful of examples:

 * Terraform binaries: Terraform core has 1,700+ contributors. The Terraform AWS
   provider has 2,800+. The Azure provider has 1,300+. The vast majority of
   these contributors do not work at HashiCorp. And that's not even counting the
   thousands of other providers in the Terraform Registry that built with no
   HashiCorp involvement at all.
 * Terraform modules: There are 14K+ in the Terraform Registry alone. The vast
   majority of these were not built by HashiCorp employees.
 * Terraform tools: There are hundreds of tools such as Terragrunt, Terratest,
   tfsec, tflint, Infracost, terraform-docs, and countless others that were not
   built by HashiCorp employees.
 * Learning resources: There are thousands of books, blog posts, courses and
   courses, such as Terraform: Up & Running, Terraform Best Practices, Udemy
   courses, Pluralsight courses, and many others that were not created by
   HashiCorp employees.

And so much more. Tools like Terraform don't live in isolation: they are part of
a large ecosystem. The same is true of Kubernetes or Linux or Go or other major
infrastructure tools. The ecosystem is a big part of why you pick those tools in
the first place: that way, you know you'll be able to hire people who know the
tools, find answers to your questions online, find libraries/extensions/etc to
save you time, and so on.

Of course, no one is questioning HashiCorp's contribution here. They created
Terraform and led the project to where it is today. They deserve full credit for
that. But to not acknowledge the tens of thousands of developers, many of whom
worked at a variety of "vendors," who contributed to the ecosystem and played a
pivotal role in Terraform's success is misleading, at best.

Terraform didn't get to where it is today solely due to HashiCorp's involvement.
The entire community, vendors included, played a huge part in that. To not
acknowledge that is bad. To then take all those contributions from the
community—which would've never happened had Terraform not been open source—and
put them under a commercial license so those contributors might not be able to
use their own work in the future is even worse.

HashiCorp deserves to earn a return on their investment. What's wrong with that?

When any company releases their tool as open source, the contract with the
community is always the same: Anyone can use this code, but we the creators hold
a privileged position of being at the epicenter of the ecosystem. Vendors then
compete to offer the best solution, and the creators enjoy a unique competitive
advantage.

We believe that HashiCorp should earn a return by leveraging its unique position
in the Terraform ecosystem to build a better product, not by outright preventing
others from competing in the first place.


SUPPORTERS

We acknowledge that maintaining an open source project such as Terraform takes a
considerable investment in terms of time, skill, effort, and coordination. We
are grateful to HashiCorp for creating Terraform and their leadership in getting
it to this point, and to the thousands of community members for their
contributions so far. The next step for Terraform must be to remain open source,
either by HashiCorp switching it back to a truly open source license or by us
forking it into a foundation. Whichever way it turns out, to ensure that there
is sufficient investment to grow and evolve Terraform, the signatories below
pledge to pool our resources to build a more open, inclusive future for an open
source Terraform.


INSTRUCTIONS

If you’re willing to join our cause, please sign the manifesto as follows:

 1. Check out the manifesto repo (instructions).
 2. Add a new row to the end of the table below with your details.
 3. Open a pull request with your changes (instructions).


CO-SIGNED

Name Type How you'd like to help Gruntwork Company Development; open-source
community efforts Spacelift Company Cover the cost of 5 FTEs for at least 5
years env0 Company Cover the cost of 5 FTEs for at least 5 years Scalr Company
Cover the cost of 3 FTEs for at least 5 years Digger Company Development;
open-source community efforts Doppler Company Development; open-source community
efforts Gem Agile Company Development; open-source community efforts Massdriver
Company Development; open-source community efforts Qovery Company Development;
open-source community efforts Rivet Company Development; open-source community
efforts Terramate Company Development; open-source community efforts Terrateam
Company Development; open-source community efforts Verifa Company Development;
open-source community efforts Argonaut Company Development; open-source
community efforts Finisterra Company Development; open-source community efforts
AutoCloud Company Development; open-source community efforts 35up Company
Testing; code reviews; open-source community efforts Cirrus Assessment Company
Testing; minor development; open-source community efforts Amach Company
Development; open-source community efforts SMS Data Products Company
Development; open-source community efforts Cloud Posse Company Development;
open-source community efforts RoseSecurity Research Company Development;
open-source community efforts CloudDrove Company Development; open-source
community efforts Red Queen Dynamics Company Development; open-source community
efforts Octo Ventures Company Development; open-source community efforts Oxide
Computer Company Company Development; open-source community efforts Vates
Company Development; open-source community efforts Coherence Company
Development; open-source community efforts Nullstone Company Development;
open-source community efforts Hestio Company Testing; documentation; open-source
community efforts appCD Company Development; open-source community efforts
CloudKnit Company Development; open-source community efforts Code Factory
Company Development; open-source community efforts Indeo Solutions Company
Development; open-source community efforts 0pass Company Development;
open-source community efforts AppsCode Company Development; open-source
community efforts Firefly Company Development; open-source community efforts
ControlMonkey Company Development; open-source community efforts Labyrinth Labs
Company Development; open-source community efforts Wakam Company Development;
open-source community efforts Zerodha Tech Company Development; open-source
community efforts Ahead Guru Company Development; open-source community efforts;
Consultant and Solutions Provider HanaByte Company Development; open-source
community efforts OpenTeams Company (Collective) Community Work Orders; Open
Source Business Development; OSA Community Support Quansight Company
Development; Usage Testing esp. from SciPyData ecosystem; open-source community
efforts Veo Technologies Company Development; open-source community efforts
ReferrsMe Company Development; open-source community efforts FivexL Company
Development; open-source community efforts; sponsorship Funky Penguin Company
Documentation; open-source community efforts OpsVox Company Documentation;
open-source community efforts Sailorcloud Company Cover the cost of 1 FTE for at
least 2 years Stakater Company Development; open-source community efforts
Recursive Labs LTD Company Development; open-source community efforts and Open
Source foundation experience American Cloud Company Development; open-source
community efforts Inceptive Custom Software Solutions Company Development;
open-source community efforts Cloud Cauldron Ltd Company Development;
open-source community efforts CMPSOARES Lda. - Consultancy Services Company
Development; open-source community efforts Cloudresty Company Development;
open-source community efforts ColoradoColo Company Development; open-source
community efforts; Hosting and server environments Nuvibit Company Development;
open-source community efforts Sentinella Company Development; open-source
community efforts mkdev Company Development; open-source community efforts
Facets.cloud Company Development; open-source community efforts; ADV-IT Company
Development; open-source community efforts QDO Company Development; open-source
community efforts; Consultant and Solutions Provider StackGuardian Company
Development; open-source community efforts Raftech™ Company Development;
Open-source community efforts; Cloudacious Company Open-source community
efforts; DevOps; Documentation; Teaching Checkout.com Company Development;
open-source community efforts OTF Project Development; open-source community
efforts Terrakube Project Development; open-source community efforts Kubestack
Project Development; open-source community efforts Elastic2ls Project
Development; open-source community efforts Layerform Project Development;
open-source community efforts terraform-docs Project Development; open-source
community efforts Cristian Vlad Individual Development; open-source community
efforts Mariano Rodríguez Individual Development; open-source community efforts
Ted Parvu Individual Development; open-source community efforts Mike Hodgkins
Individual Development; open-source community efforts Thomas Schuetz Individual
Development; open-source community efforts Kelvin Soares Individual Development;
open-source community efforts Chris Doyle Individual Development; open-source
community efforts Alex Panayi Individual Development; open-source community
efforts Sandro Manke Individual Development; open-source community efforts Dave
Overall Individual Development; open-source community efforts Jeff Frasca
Individual Development; open-source community efforts Jeff Wenzbauer Individual
Development; open-source community efforts Alex Levinson Individual Development;
open-source community efforts Michael Pursifull Individual Development;
open-source community efforts Teodor Kostadinov Individual Development;
open-source community efforts Patrick Jain-Taylor Individual Development;
open-source community efforts Daniel Ristic Individual Development; open-source
community efforts Debasish Mishra Individual Development; open-source community
efforts Eddie Herbert Individual Development; open-source community efforts
Curtis Vanzandt Individual Development; open-source community efforts Talal
Tahir Individual Development; open-source community efforts Kevin Rathbun
Individual Development; open-source community efforts David Douglas Individual
Development; open-source community efforts Coin Graham Individual Development;
open-source community efforts Jim Jagielski Individual Development; open-source
community efforts and Open Source foundation experience Maciej Strzelecki
Individual Development; open-source community efforts Ioannis Polyzos Individual
Development; open-source community efforts Elvis McNeely Individual Development;
open-source community efforts Yoaquim Cintron Individual Development;
open-source community efforts Viktor Nagornyy Individual Open-source community
efforts; Non-profit experience; Fundraising/Open Collective Ronny López
Individual Development; open-source community efforts Khrist Hansen Individual
Development; open-source community efforts Fatih Tokus Individual Development;
open-source community efforts Bill Oberacker Individual Development; open-source
community efforts Tiago Rodrigues Individual Development; open-source community
efforts Nik Kotov Individual Development; open-source community efforts Nikolay
Individual Development; open-source community efforts Simón Ramos Individual
Development; open-source community efforts John Walsh Individual Development;
open-source community efforts Zoltan Vigh Individual Development; open-source
community efforts Ilyas Hamdi Individual Development; open-source community
efforts Samuel Phan Individual Development; open-source community efforts Denis
Vaumoron Individual Development; open-source community efforts Lawal AbdulLateef
Individual Development; open-source community efforts Nils Knieling Individual
Development; open-source community efforts Bruno Schaatsbergen Individual
Development; open-source community efforts Aymen Segni Individual Development;
open-source community efforts Luis M. Gallardo D. Individual Development;
open-source community efforts Willi Carlsen Individual Development; open-source
community efforts Lucas Tesson Individual Development; open-source community
efforts Simon Effenberg Individual Development; open-source community efforts
Ofer Chen Individual Development; open-source community efforts Arthur Busser
Individual Development; open-source community efforts Ahmed Qazi Individual
Development; open-source community efforts Oliver Shaw Individual Development;
open-source community efforts Nikul Jain Individual Development; open-source
community efforts Alex Torres Individual Development; open-source community
efforts Rasmus Rask Individual Development; open-source community efforts Henare
Degan Individual Development; open-source community efforts Vineet Pal Singh
Rauniwal Individual Development; open-source community efforts Bruno Mattarollo
Individual Development; open-source community efforts Mahesh Rijal Individual
Testing; Documentation; open-source community efforts Thomas van Latum
Individual Development; open-source community efforts Piotr Plenik Individual
Development; open-source community efforts Nguyen Duy Phuong Individual
Development; open-source community efforts Diego Cristóbal Individual
Development; open-source community efforts and Open Source foundation experience
Yasha Prikhodko Individual Development; open-source community efforts Allie
Coleman Individual Development; open-source community efforts Scott A. Williams
Individual Development; open-source community efforts Kevin Zheng Individual
Development; open-source community efforts Gayan Hewa Individual Development;
open-source community efforts Yadav Lamichhane Individual Development;
open-source community efforts Wan Azlan Wan Mansor Individual Development;
open-source community efforts Ben McNicholl Individual Development; open-source
community efforts Minchul Joh Individual Development; open-source community
efforts Karan Sharma Individual Development; open-source community efforts Colin
Wilson Individual Development; open-source community efforts Dylan Hitt
Individual Development; open-source community efforts Thomas Senay Individual
Testing; Documentation Alik Khilazhev Individual Development; open-source
community efforts Gary Mclean Individual Development; open-source community
efforts David Jones Individual Development; Consultancy; Leveraging OS tools on
behalf of clients Bob Rohan Individual Development; open-source community
efforts Javier Ruiz Jimenez Individual Development; open-source community
efforts Igor Rodionov Individual Development; open-source community efforts
Sumeet Ninawe Individual Development; open-source community efforts Ravish
Tiwari Individual Development; open-source community efforts; Helping teams
adopt scalable Open Source IaC tools Alexander Sharov Individual Development;
open-source community efforts Nikolai Mishin Individual Development; open-source
community efforts Ovidiu BOGDAN Individual Development; open-source community
efforts; Testing; Documentation; Webert Lima Individual Development; open-source
community efforts Mahsoud Badalbaev Individual Development; Research; Testing;
Helping teams adopt scalable Open Source IaC tools Farshad Nematdoust Individual
open-source community efforts; Testing; Helping teams adopt scalable Open Source
IaC tools Roozbeh Shafiee Individual Development; Research; Testing; Helping
teams adopt scalable Open Source IaC tools Eran Elbaz Individual Development;
open-source community efforts Razvan Cranganu Individual Development;
open-source community efforts; Documentation; Yuriy Medvedev Individual
Development; open-source community efforts Piotr Mossakowski Individual
Development; Testing; Documentation; open-source community efforts Włodzimierz
Gajda Individual Development; Research; Testing; Helping teams adopt scalable
Open Source IaC tools Bennie Mosher Individual Development; Research; Testing;
Helping teams adopt scalable Open Source IaC tools Alessio Dionisi Individual
Development; open-source community efforts Thom (Spyro) Smith Individual
Development; Testing; open-source community efforts Alan Ip Individual
Development; open-source community efforts Ayodele Spencer Ademeso Individual
Development; open-source community efforts Ken Spur Individual Development;
open-source community efforts Pedro Freitas Individual Development; open-source
community efforts; Helping teams adopt scalable Open Source IaC tools Shubham
Gopale Individual Development; open-source community efforts and Open Source
foundation experience Audun V. Nes Individual Testing; open-source community
efforts Aniket Singh Individual Development; open-source community efforts Adam
Comerford Individual Testing; Documentation Alex M. Schapelle Individual
Development;Operations;Reasearch;Consult open-source community efforts Phillipe
Smith Individual Development; open-source community efforts; Helping teams adopt
scalable Open Source IaC tools Nicolas Faugeroux Individual Development;
open-source community efforts and Open Source foundation experience Alan
Jumeaucourt Individual Development; open-source community efforts Andy Tan
Individual Development; Testing; open-source community efforts Adam Miller
Individual Development; open-source community efforts Maximiliano Alberto Di
Pietro Individual Development; open-source community efforts RUI Individual
Development; open-source community efforts David Cohan Individual Development;
open-source community efforts Rick Christy Individual Development; open-source
community efforts Ken Spur Individual Development; open-source community efforts
Ross Mason Individual Development; open-source community efforts Dheeraj Kumar
Individual Development; open-source community efforts Maeghan Porter Individual
Development; open-source community efforts Wesley Kirkland Individual
Open-source community efforts Aron Wagner Individual Open-source community
efforts Oldrich Vykydal Individual Development; Research; Testing; Helping teams
adopt scalable Open Source IaC tools John Dyer Individual Development;
open-source community efforts and Open Source foundation experience Frédéric
Harper Individual Development, open-source community efforts, Open Source
foundation experience, and helping teams adopt scalable Open Source IaC tools.
Steven Kreitzer Individual Development; Research; Testing; Helping teams adopt
scalable Open Source IaC tools Robert Lilly Individual Development; open-source
community efforts and Open Source foundation experience Robert Hafner
Individual, Author Development; open-source community efforts; Documentation;
author of Terraform in Depth Alexander As Individual Open-source community
efforts; Testing; Helping adopt scalable Open Source IaC tools Richard Rives
Individual Development; open-source community efforts Jeff Alyanak Individual
Development; open-source community efforts; Testing; Documentation Saeed
Hosseini Individual Development; Testing; Documentation; open-source community
efforts Ben Jackson Individual Development; open-source community efforts Jason
Hollis Individual Development; open-source community efforts Eli Shalnev
Individual Platform architecture; Development; Testing; Documentation;
open-source community efforts Matthew Weingarten Individual Development;
open-source community efforts Dougie Peart Individual Development; open-source
community efforts Joe Ciskey Individual Development; open-source community
efforts Ernest Mallett Individual Development; Testing; open-source community
efforts Michael Foster Individual Development; open-source community efforts;
Help teams adopt scalable Open Source IaC tools Raphael Cardoso Individual
Development; open-source community efforts Randy Wallace Individual Development;
open-source community efforts Roman Ryzhyi Individual Development; open-source
community efforts Juan Pablo Calvo Individual Development; open-source community
efforts Wesley Charles Blake Individual Development; open-source community
efforts Ervin Szilagyi Individual Platform architecture; Development; Testing;
Documentation; open-source community efforts Chris Funderburg Individual
Platform architecture; Development; Testing; Documentation; open-source
community efforts Rafael da Cruz Individual SRE; open-source community efforts,
Help teams adopt scalable Open Source tools Davi Miranda Individual Development;
open-source community efforts Rogelio Di Pasquale Individual Development;
open-source community efforts Sebastian Fyda Individual Development; open-source
community efforts David Cantos C. Individual Development; open-source community
efforts Jonathan Arana Individual Development; open-source community efforts Sam
Wuraola Individual Development; open-source community efforts Thiago Leoncio
Scherrer Individual Development; open-source community efforts Ulises Magana
Individual Development; open-source community efforts Ramon Silveira Borges
Individual Development; open-source community efforts Charles Ferguson
Individual Development; open-source community efforts Wanis Fahmy Individual
Development; open-source community efforts Arturo Delgado Individual
Development; devops/infra help where needed; promote the word of FOSS Glenn
Rolland Individual Development; Research; Testing; Open-source community efforts
Sergey Lanzman Individual Development; open-source community efforts Keegan
McIver Individual Development; open-source community efforts Felipe Freitas de
Oliveira Individual Open-source community efforts Jeff Geerling Individual
Documentation; open-source community efforts Sander van Zoest Individual
Development; open-source community efforts Pratik Lawate Individual DevOps;
CLoud; Help teams adopt scalable Open Source IaC tools Tyler Fougere Individual
Development; open-source community efforts Minecraftchest1 Individual
Enthusiasts Kellen Anker Individual Development; open-source community efforts
James Caldow Individual Development; open-source community efforts Luis Gonzalez
Individual Development; open-source community efforts Kai Korla Individual
Research; Testing; Helping teams adopt scalable Open Source IaC tools Carlos
Manuel Soares Individual Development; open-source community efforts Fabio
Segredo Individual open-source community efforts; Testing; Documentation;
Helping adopt scalable Open Source IaC tools Nikhil Sodemba Individual
Development; open-source community efforts Sanjay Sachdev Individual
Development; Documentation; open-source community efforts Evans Tucker
Individual Social Media - spreading awareness of FOSS and its importance. And
DevOps/infra help, if needed. Devin Young Individual Development; open-source
community efforts Manal Lamine Individual Development; open-source community
efforts; Helping teams adopt scalable Open Source IaC tools Keri Melich
Individual Development; Testing; open-source community efforts Dan Piet
Individual Development; Testing; open-source community efforts Guillermo
Alvarado Individual Development; Documentation; open-source community efforts
and DevOps/infra help, if needed. Enmanuel Moreira Individual Documentation;
open-source community efforts Julio C. Ortega Individual Development; Testing;
open-source community efforts;VaSLibre F/LOSS Group Zachary Ness Individual
Development; open-source community efforts Sanjay Hona Individual Development;
open-source community efforts Burak Cansizoglu Individual Development;
open-source community efforts Andre Bacao Individual Development; Terraform
Advocate; open-source community efforts; Helping teams adopt scalable Open
Source IaC tools Seonbo Shim Individual Development; open-source community
efforts Kei Vin Cheng Individual Development; open-source community efforts Son
Bui Individual Development; open-source community efforts Samuel Tan Individual
Development; open-source community efforts Bharathkumarraju Individual
Development; open-source community efforts Renjith Pillai Individual
Development; open-source community efforts Aditya Krishnakumar Individual
Development; open-source community efforts Nathanael Demacon Individual
Research; Development; Open-source community efforts; Terraform provider
developer at a cloud provider Rémi FLAMENT Individual Development in opensource
modules; open-source community efforts Maximilian Kratz Individual Development;
Documentation; Open-source community efforts Dr. Ogg Individual Development;
open-source community efforts Lage Berger-Brendryen Individual DevOps; Cloud;
Helping organizations adopt modern IaC practices and principles Koen van Zuijlen
Individual Development; open-source community efforts Robin Opletal Individual
Development; open-source community efforts Stefan Castor Individual Development;
Terraform Advocate; open-source community efforts; Helping teams adopt scalable
Open Source IaC tools Dmitry Averkiev Individual Development; open-source
community efforts Ciprian Ursu Individual DevOps/Cloud Consultant; open-source
community efforts Basil Pozdeev Individual Development; open-source community
efforts KD Puvvadi Individual Open-source community efforts; DevOps;
Documentation; Development Andrew Red Individual Open-source community efforts;
DevOps; Development; Helping companies adopt scalable Open Source IaC practices
and tools Ariel Weiss Individual Open-source community efforts; Development
Adrian Otrębski Individual Open-source community efforts; DevOps; Development;
Testing; Helping companies adopt scalable Open Source IaC practices and tools
Adam Walton Individual Development; open-source community efforts Xavier Mignot
Individual Development; open-source community efforts Carsten Agger Individual
Development; open-source community efforts Dusan Simek Individual
DevOps/Cloud/Infra Aleh Katsuba Individual Documentation; Development; Testing
Ron Hernaus Individual Development; open-source community efforts Chris Simpson
Individual Development; DevOps; open-source community efforts Steven Billington
Individual Documentation; Development; Testing; open-source community efforts
Justin Smith Individual Documentation; DevOps; open-source community efforts
Igor Eulalio Individual Documentation; DevOps; open-source community efforts
David Hill Individual Documentation; Development; Testing

August 17th, 2023