-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Establish Zarf Goals, Non-Goals and Norms #369
Labels
documentation 📘
Improvements or additions to documentation
Comments
jeff-mccoy
added
documentation 📘
Improvements or additions to documentation
community
labels
Mar 7, 2022
This should be finished alongside #174 |
5 tasks
Racer159
added a commit
that referenced
this issue
Nov 7, 2023
## Description This updates the Zarf overview to be more clear about what the project is and how to use it. ## Related Issue Relates to: #369 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [X] Other (security config, docs update, etc) ## Checklist before merging - [X] Test, docs, adr added or updated as needed - [X] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per multiple team meetings, we have agreed to establish a set of boundaries around what zarf is, isn't and how we want to build/use zarf. This issue will serve as a tracking for that. Use comments (vs editing the issue) to track that and we will summarize in a PR to put into the repo going forward.
The text was updated successfully, but these errors were encountered: