# Contributing to MCPMux Desktop
Thank you for your interest in contributing!
## License
This project is licensed under the [GNU General Public License v3.0 (GPL-3.0)](LICENSE). By contributing, you agree that your contributions will be licensed under the same license.
## Developer Certificate of Origin (DCO)
All contributions must be signed off to certify that you have the right to submit them. This is done by adding a `Signed-off-by` line to your commit messages:
```
Signed-off-by: Your Name <your.email@example.com>
```
You can do this automatically by using the `-s` flag when committing:
```bash
git commit -s -m "Your commit message"
```
By signing off, you certify the following (from [developercertificate.org](https://developercertificate.org/)):
```
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
```
## How to Contribute
### Reporting Issues
- Check existing issues first
- Include steps to reproduce
- Include your OS and app version
### Pull Requests
1. Fork the repository
2. Create a feature branch (`git checkout -b feature/my-feature`)
3. Make your changes
4. Ensure tests pass
5. Sign off your commits (`git commit -s`)
6. Push and create a Pull Request
### Code Style
- Run `pnpm lint` before submitting
- Follow existing code patterns
- Keep changes focused and minimal
## Questions?
Open a discussion or issue if you need help.
