Skip to content

Commit

Permalink
Adjust manifesto (#127)
Browse files Browse the repository at this point in the history
  • Loading branch information
damianstasik authored Sep 19, 2023
1 parent 050108e commit 9c16d50
Show file tree
Hide file tree
Showing 2 changed files with 71 additions and 41 deletions.
36 changes: 29 additions & 7 deletions src/components/TextContent/index.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -3,19 +3,41 @@ import clsx from "clsx";

type TextContentProps = HTMLProps<HTMLDivElement>;

const classNames = [
"prose",
"lg:prose-lg",
"text-gray-900",
"dark:text-gray-100",
"mx-auto",
"mb-10",
"px-4",
"md:px-0",

// <h2>
"prose-h2:text-gray-900",
"dark:prose-h2:text-gray-50",
"prose-h2:text-2xl",
"prose-h2:leading-snug",
"md:prose-h2:text-4xl",
"md:prose-h2:leading-normal",

// <li>
"prose-li:marker:text-inherit",

// <a>
"prose-a:text-inherit",

// <strong>
"prose-strong:text-inherit",
];

export default function TextContent({
children,
className,
...rest
}: TextContentProps) {
return (
<div
className={clsx(
"prose lg:prose-lg mx-auto prose-h3:text-gray-900 dark:prose-h3:text-gray-50 prose-h3:text-2xl prose-h3:leading-snug md:prose-h3:text-5xl md:prose-h3:leading-normal prose-li:marker:text-inherit prose-a:text-inherit px-4 md:px-0 text-gray-600 dark:text-gray-500 mb-10 prose-strong:text-inherit",
className
)}
{...rest}
>
<div className={clsx(classNames, className)} {...rest}>
{children}
</div>
);
Expand Down
76 changes: 42 additions & 34 deletions src/pages/manifesto.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ import Layout from "@theme/Layout";
import Jumbotron from "../components/Jumbotron";
import TextContent from "../components/TextContent";
import Headline from "../components/Headline";
import Link from "@docusaurus/Link";

export default function Manifesto() {
return (
Expand Down Expand Up @@ -34,7 +35,7 @@ export default function Manifesto() {
that's built up around Terraform over the last 9 years.
</p>

<h3>Our concern: the BUSL license is a poison pill for Terraform.</h3>
<h2>Our concern: the BUSL license is a poison pill for Terraform.</h2>

<p>
Overnight, tens of thousands of businesses, ranging from one-person
Expand Down Expand Up @@ -83,7 +84,7 @@ export default function Manifesto() {
top of solid and predictable underpinnings.
</p>

<h3>Our goal: ensure Terraform remains truly open source—always.</h3>
<h2>Our goal: ensure Terraform remains truly open source—always.</h2>

<p>
Our aim with this manifesto is to return Terraform to a fully
Expand All @@ -95,60 +96,67 @@ export default function Manifesto() {
license change putting everything at risk.
</p>

<h3>
Our request to HashiCorp: switch Terraform back to an open-source
license.
</h3>
<h2>Why we forked Terraform.</h2>

<p>
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.
After HashiCorp switched Terraform from an open-source license to a
Business Source License (BSL), we asked HashiCorp to switch back to an
open-source license to ensure a single, impartial, reliable home for
Terraform where the whole community could unite to keep building this
amazing ecosystem. With no response from Hashicorp by August 25, we{" "}
<Link
href="https://github.com/opentffoundation/opentf"
target="_blank"
>
created a fork of Terraform
</Link>
, which is now public. You can read more about the fork announcement{" "}
<Link href="https://opentf.org/fork" target="_blank">
here
</Link>
.
</p>

<h3>Our fallback plan: fork Terraform into a foundation.</h3>
<h2>Why the Linux Foundation will maintain the fork.</h2>

<p>
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
Forking the legacy MPL-licensed Terraform and maintaining the fork in
the Linux Foundation under the name OpenTofu is similar to the way
Linux is managed by the Linux Foundation under the stewardship of
multiple companies. This ensures the tool stays truly open source and
neutral and not at the whim of any one company.
</p>

<p>
In particular, we want to create a foundation for Terraform that is:
Now that we are part of the Linux Foundation, we can guarantee that
OpenTofu will remain:
</p>

<ul>
<li>
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
<strong>Truly open source</strong> - 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
</li>
<li>
Community-driven - so that the community governs the project for the
community, where pull requests are regularly reviewed and accepted
on their merit
<strong>Community-driven</strong> - so that the community governs
the project for the community, where pull requests are regularly
reviewed and accepted on their merit
</li>
<li>
Impartial - so that valuable features and fixes are accepted based
on their value to the community, regardless of their impact on any
particular vendor
<strong>Impartial</strong> - so that valuable features and fixes are
accepted based on their value to the community, regardless of their
impact on any particular vendor
</li>
<li>
Layered and modular - with a programmer-friendly project structure
to encourage building on top, enabling a new vibrant ecosystem of
tools and integrations
<strong>Layered and modular</strong> - with a programmer-friendly
project structure to encourage building on top, enabling a new
vibrant ecosystem of tools and integrations
</li>
<li>
Backwards-compatible - so that the existing code can drive value for
years to come
<strong>Backwards-compatible</strong> - so that the existing code
can drive value for years to come
</li>
</ul>
</TextContent>
Expand Down

0 comments on commit 9c16d50

Please sign in to comment.