Permalink
Browse files

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 <msw@amazon.com>
  • Loading branch information...
mswilson authored and acatangiu committed Nov 21, 2018
1 parent fa9b89a commit 068befdab5156c03ab610b8e7e22c2760444e41a
Showing with 6 additions and 7 deletions.
  1. +6 −7 CHARTER.md
@@ -5,7 +5,7 @@
Enable secure, multi-tenant, minimal-overhead execution of container and
serverless workloads.

## Tenets
## Tenets (unless you know better ones)

These tenets guide Firecracker's development:

@@ -21,13 +21,12 @@ These tenets guide Firecracker's development:
1. **Compute Oversubscription**: All of the hardware compute resources exposed
by Firecracker to guests can be securely oversubscribed.

## Contributions & Governance
## Contributions & Project Roles

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 [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.

0 comments on commit 068befd

Please sign in to comment.