---
title: "Process — Spiff Arena 0.1 documentation"
description: "We use GitHub projects to manage our work. You can find our board here , and issues can be filed here ."
source_url: https://spiff.works/docs/spiff-arena/explanation/dev/process.html
---

☰ Menu

# Process[](#process "Link to this heading")

## Ticket Management[](#ticket-management "Link to this heading")

We use GitHub projects to manage our work.
You can find our board [here](https://github.com/orgs/sartography/projects/3), and issues can be filed [here](https://github.com/sartography/spiff-arena/issues).

## CI[](#ci "Link to this heading")

We use GitHub Actions for CI.
The workflows are defined in the `.github/workflows` directory.
The main things that happen, not necessarily in this order, are represented in this chart:

flowchart LR
subgraph "backend\_tests"[Backend Tests]
pytest[Pytest]
mypy[MyPy]
safety[Safety]
black[Black]
typeguard[TypeGuard]
end
subgraph "frontend\_tests"[Frontend Tests]
vitest[Vitest]
eslint[ESLint]
prettier[Prettier]
cypress[Cypress]
end
backend\_tests --> frontend\_tests
frontend\_tests --> docker\_images

## Security[](#security "Link to this heading")

We have security checks in place for both the backend and the frontend.
These include the security library in the backend, and Snyk in the frontend and backend.
Two independent security reviews have been performed on the codebase, and mitigations have been implemented to the satisfaction of the reviewers.

## Contributing[](#contributing "Link to this heading")

This is the last page in the Technical Documentation section, where we keep content mainly intended for developers.
And that seems like as good a place as any to mention that it would be great to have you contributing to the project!
There is a [Contributing doc](https://github.com/sartography/spiff-arena/blob/main/CONTRIBUTING.rst) that you can follow.
You can find other like-minded people in our [Discord](https://discord.gg/F6Kb7HNK7B).
Thank you!

graph LR
code[Hammer code] --> PR
PR --> Profit