# Firecracker Charter

## Mission

Enable secure, multi-tenant, minimal-overhead execution of container and
serverless workloads.

## Tenets

These tenets guide Firecracker's development:

1. **Built-In Security**: We provide compute security barriers that enable
   multitenant workloads, and cannot be mistakenly disabled by customers.
   Customer workloads are simultaneously considered sacred (shall not be
   touched) and malicious (shall be defended against).
1. **Light-weight Virtualization**: We focus on transient or stateless workloads
   over long-running or persistent workloads. Firecracker's hardware resources
   overhead is known and guaranteed.
1. **Minimalist in Features**: If it's not clearly required for our mission, we
   won't build it. We maintain a single implementation per capability.
1. **Compute Oversubscription**: All of the hardware compute resources exposed
   by Firecracker to guests can be securely oversubscribed.

## Contributions & Governance 

All contributions must align with this charter and follow Firecracker's
[contribution process](CONTRIBUTE.md).

Only Firecracker [maintainers](MAINTAINERS.md) may merge contributions into the
master branch and create Firecracker releases. Maintainers are also subject to
the mission and tenets outlined herein. Anyone may submit and review
contributions.


# Firecracker Charter

## Mission

Enable secure, multi-tenant, minimal-overhead execution of container and
serverless workloads.

## Tenets (unless you know better ones)

These tenets guide Firecracker's development:

1. **Built-In Security**: We provide compute security barriers that enable
   multitenant workloads, and cannot be mistakenly disabled by customers.
   Customer workloads are simultaneously considered sacred (shall not be
   touched) and malicious (shall be defended against).
1. **Light-weight Virtualization**: We focus on transient or stateless workloads
   over long-running or persistent workloads. Firecracker's hardware resources
   overhead is known and guaranteed.
1. **Minimalist in Features**: If it's not clearly required for our mission, we
   won't build it. We maintain a single implementation per capability.
1. **Compute Oversubscription**: All of the hardware compute resources exposed
   by Firecracker to guests can be securely oversubscribed.

## Contributions & Project Roles

All contributions must align with this charter and follow Firecracker's
[contribution process](CONTRIBUTE.md).

Firecracker [maintainers](MAINTAINERS.md) merge contributions into the
master branch and create Firecracker releases. Maintainers are also
subject to the mission and tenets outlined above. Anyone may submit
and review contributions.

Adjust tenets and project role description
docs: Adjust tenets and project role description

We are always gathering new information, and therefore project tenets
are not set in stone. We want to thoughtfully adopt tenets that help
us make tough calls so they should not change often. But we want to
make sure that it is known that the door is always open to refine our
thinking.

For this reason, we traditionally include "unless you know better
ones" when we state our tenets.

Signed-off-by: Matt Wilson <260f5074942ca36dab941199ff6b19fcaa26ccde@amazon.com>
