SUPPORT.md

Support Guidelines

We strive to create clear guidelines on communication to the Zarf team to provide a good community experience.

Questions

For guidance on using Zarf, the documentation should cover most use cases. For all questions documentation may not cover, we suggest utilizing Github Discussions.

Standard Process

All code issues should be a Github Issue that follows the issue template.

Following the templates provides the Zarf community a foundation of understanding to be able to assist quickly. After an issue is made, this issue can be brought into other chanels such as the Kubernetes Slack #Zarf channel or the bi-weekly Zarf Community Meeting.

            Github Issue 
            /          \
Zarf Slack Channel    Zarf Community Call

Sensitive Information Process

For issues from those who are unable to post on Github, you may send an email using the following issue template filled out to zarf-dev-private@googlegroups.com

The response time to emails may be delayed as they are not able to receive community help, so we encourage participation into Github Issues as much as possible.

### Environment
Device and OS:
App version:
Kubernetes distro being used:
Other:

### Steps to reproduce
1.

### Expected result

### Actual Result

### Visual Proof (screenshots, videos, text, etc)

### Severity/Priority

### Additional Context
Add any other context or screenshots about the technical debt here.