airship/governance
Code Issues Proposed changes

Add Core Principles

Browse Source 
Our governance refers to the "Core Principles" of Airship, but we've been
lax in formally defining what those are.  This patchset adds a general
definition, based on discussion from the Working Comittee meeting on
2020-06-29.

Change-Id: Ia912d14913dd540d9c3550b40ab22536e40431ab
This commit is contained in:
Matt McEuen 2020-07-07 09:56:56 -05:00
parent c6b2d9e36e
commit 8601fa9be7
2 changed files with 35 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -39,7 +39,8 @@ drive end-to-end provisioning of a site, from bare metal to fully functioning cl
Airship is working to build a global, diverse and collaborative community. Anyone interested in supporting the technology Airship is working to build a global, diverse and collaborative community. Anyone interested in supporting the technology
is welcome to participate. We are seeking different expertise and skills, ranging from development, operations, is welcome to participate. We are seeking different expertise and skills, ranging from development, operations,
documentation, marketing, community organization and product management. documentation, marketing, community organization and product management. The core principles of the Airship community
can be found [here](principles.md).
### Join Us ### Join Us

33
principles.md Normal file
View File

@ -0,0 +1,33 @@
# Airship Core Principles
* [Community Principles](#community-principles)
* [Technical Principles](#technical-principles)
The Airship project follows several technical principles which guide what we build, and community
principles which guide how we build it.
## Community Principles
The Airship community is fully committed to the OpenStack Foundation
[Community Code of Conduct](https://www.openstack.org/legal/community-code-of-conduct). We are
a welcoming, respectful, and inclusive community, and believe treating one another in this way
is both the right thing to do and the best way to craft valuable software.
Airship is also committed to the [Four Opens](https://wiki.openstack.org/wiki/Open) of software
development: Open Source, Open Design, Open Development, and Open Community.
## Technical Principles
The Airship project uses the following guiding principles in design and development, to ensure
that the software we author is valuable and solves the right problems.
* Airship is a declarative and automated toolset for the lifecycle management of
open infrastructure.
* Airship is Repeatable, Predictable, Approachable, Flexible, Composable, and Reusable.
* Airship follows
[cloud-native principles](https://github.com/cncf/toc/blob/master/DEFINITION.md)
and uses standardized, open-source components, avoiding technology lock-in.
* Airship is small and focused, incorporating best-in-class open-source tooling and employing the
principles above to integrate it in and make it valuable to operators. The Airship community
prefers to enhance general-purpose projects, working within their communities, over crafting
Airship-specific solutions.