Community
TrailCurrent is built by people who use it—engineers, makers, RV owners, and anyone who believes vehicles should be smarter. You don't need to write code to make a difference here.
Ways to Get Involved
There is no single way to contribute. Pick what matches your skills and interests.
Share Your Build
No coding requiredBuilt the system in your vehicle? Share photos, write about your experience, and help others see what's possible. Real installs inspire new contributors.
Test in Your Vehicle
No coding requiredReal-world testing feedback is the most valuable contribution we receive. Install a module, use it on a trip, and tell us what worked and what didn't.
Report Issues
Low barrierIf something in the docs doesn't make sense, that's a bug worth reporting. Found a problem? Open an issue. Clear bug reports save everyone time.
Improve Documentation
MediumBetter documentation helps everyone. Fix typos, add examples, clarify setup instructions, or write a tutorial about your experience.
Write Code
TechnicalFix bugs, add features, improve tests, or build new integrations. Fork the repo, make changes on a branch, and submit a pull request.
Design Hardware
TechnicalReview PCB layouts, suggest improvements, design new modules, or create better enclosures. All hardware designs are in KiCAD and FreeCAD.
How to Contribute
A few simple guidelines to keep things organized. Don't worry if you're new to this—we'll help you through your first contribution.
1. Fork & Branch
Fork the repository and create a feature branch from main. Name it
something descriptive like
feature/add-temperature-alert or
fix/can-bus-timing.
2. Make Your Changes
Write clear commit messages that explain what changed and why. Reference issue numbers when applicable. Small, focused changes are easier to review.
3. Test When You Can
For firmware: build with PlatformIO and test on hardware if possible. For software: verify the Docker stack starts cleanly. For documentation: check that links work and instructions are clear.
4. Open a Pull Request
Submit a PR against main with a clear description. Link any related issues. We review everything and provide constructive feedback.
5. Be Kind
We're all here because we care about making vehicles better. Treat everyone with respect, be patient with newcomers, and assume good intentions.
First time contributing to open source? That's great—everyone starts somewhere. Open an issue, introduce yourself, and we'll point you toward a good first task.
Quick Links
Jump directly to where you need to go.
GitHub Organization
Browse all repositories, star your favorites, and follow for updates.
Documentation
Architecture guides, CAN bus definitions, setup instructions, and reference material.
Report an Issue
Found a bug, confusing docs, or have a feature idea? Open an issue and let us know.
Getting Started Guide
Prerequisites, quick-start paths, and setup instructions for different areas of the platform.
Licensing
Everything is open source under the MIT license.
MIT License
All repositories use the MIT license. Permissive—use, modify, and distribute with minimal restrictions. Just include the license notice.
- Commercial use allowed
- Modification and distribution allowed
- Private use allowed
- Only requires license notice
What This Means
You can use TrailCurrent in personal and commercial projects. Fork it, modify it, build products on it. Just keep the license notice.
- Build custom vehicle systems
- Create derivative hardware designs
- Integrate into commercial products
Join the Community
Whether you're sharing a build photo, reporting a confusing instruction, or submitting your first pull request—you're making vehicles smarter.