---
title: "Contributing"
space: "Frappe Framework"
url: "https://www.prilk.com/docs/frappe-framework/contributing"
updated: "2026-05-14"
---

## Contributing

Frappe and ERPNext are open source under GPLv3. Anyone can contribute — code, translations, docs, bug reports.

### Reporting bugs
File an issue on the relevant GitHub repository:
- [frappe/frappe](https://github.com/frappe/frappe/issues) — framework
- [frappe/erpnext](https://github.com/frappe/erpnext/issues) — ERPNext
- One repo per Frappe-maintained app

Include: Frappe version (`bench version`), browser, steps to reproduce, and any error log from the desk.

### Submitting code
1. Fork the repo on GitHub
2. Branch from the version your fix targets (usually `develop`)
3. Run the test suite locally (`bench --site test_site run-tests --app frappe`)
4. Open a pull request with a clear description
5. Sign the contributor agreement if prompted

Frappe's review process can take a few days to a few weeks depending on scope.

### Translations
Frappe uses [Crowdin](https://crowdin.com/project/frappe) for translation. Pick your language, propose translations, votes from native speakers gate which strings land. Dutch (`nl`) is well-covered; other languages vary.

### Documentation
The official docs are also on GitHub: [github.com/frappe/erpnext_documentation](https://github.com/frappe/erpnext_documentation). PRs welcome.

### Prilk-specific contributions
For bugs or improvements in any **Prilk** app (Digital Signing, eDocument, Pilot, …), email [support@prilk.com](mailto:support@prilk.com) or open an issue if the repo is public.