aliasvault/CONTRIBUTING.md

Contributing to AliasVault

Thanks for your interest in contributing to the AliasVault project! There are a lot of ways to help out.

Table of Contents

1. Help spread the word
2. Contributing to Translations
3. Contributing to the Documentation
4. Contributing to the Main Codebase
   • 4.1 Get in contact
   • 4.2 Set up your local development environment
5. License and Contributions

---

1. Help spread the word

Help grow the AliasVault community by:

• Answering questions and helping users in our Discord
• Reporting bugs and suggesting improvements
• Sharing on social media and writing about your experience
• Creating tutorials and documentation
• Spreading the word about privacy and self-hosting

2. Contributing to Translations

Help make AliasVault accessible to users worldwide by contributing translations! AliasVault is currently available in English and Dutch, but we're looking for volunteers to help translate it into other languages such as German, French, Spanish, Ukrainian, Italian, and more.

AliasVault translations are managed through Crowdin, an online translation platform. If you’d like to help translate AliasVault into your native language, please contact us via email or Discord. We’ll be happy to set you up with access to the translation project.

Your translation contributions will help make AliasVault more accessible to privacy-conscious users around the world!

3. Contributing to the Documentation

The docs are built using Jekyll and automatically deploy to GitHub Pages via GitHub Actions. You can build the docs locally by running docker compose up in the ./docs folder.

The docs site is based on the open-source template called Just The Docs. Find more information about how this template works in the official docs.

To make changes to the AliasVault documentation please make a PR that directly edits the docs markdown files in this repository.

4. Contributing to the Main Codebase

4.1 Get in contact

If you're planning to work on a new feature or improvement for AliasVault, we strongly encourage you to get in touch with us first. This ensures that your proposed changes align with the project's direction and increases the likelihood of your work being accepted into the official repository. You can reach us through:

• Opening an issue on GitHub to discuss your proposed changes
• Reaching out via Discord or email
• Contacting the maintainers directly

4.2 Set up your local development environment

You can find instructions on how to get your local development environment setup for the different parts of the AliasVault codebase here:

https://docs.aliasvault.net/misc/dev/

Tip: if the URL above is not available, the raw doc pages can also be found in the docs folder in this repository.

If you run into any issues, feel free to join our Discord to chat with the maintainers and author.

5. License and Contributions

AliasVault is licensed under the GNU Affero General Public License v3.0 (AGPLv3). By submitting code, documentation, or other contributions to this project, you agree that:

1. Your contribution will be licensed under the same AGPLv3 license as the project
2. You have the legal right to grant this license (e.g., you are the author, or have permission)
3. You understand that your contribution will be made public under the AGPLv3 terms
4. You are not expected to provide support or warranties for your contribution

✅ There is no Contributor License Agreement (CLA) required. We believe in a balanced open source model where all contributors are treated equally under the terms of the AGPLv3.

By opening a pull request, you agree to these terms. Your contributions will be published under the AGPLv3 license.