We're building technology that enables, not enslaves. Contributions are welcome from everyone who shares this mission.
- Fork the repository
- Create a feature branch (
git checkout -b feature/your-idea) - Make your changes
- Sign the CLA (first-time contributors)
- Submit a pull request
First-time contributors must accept our CLA.
How to sign: Add a comment to your first PR:
I have read and agree to the Thoughtful App Co. CLA v1.0
This grants TACo the rights to use your contribution while you retain ownership of your work.
Tacos are our way of tracking contribution history. They're like reputation points — a record of what you've contributed to TACo. As a way of making things easier, you an make a PR with your suggested Taco. If the MR is request is accepted, your ledger is also updated.
| Contribution Type | Tacos 🌮 | Examples |
|---|---|---|
| Tiny fix | 0.01 - 0.10 | Typo, formatting |
| Helpful comment | 0.05 - 0.25 | Issue clarification, reproduction |
| Bug fix (minor) | 0.10 - 0.50 | Small fixes, edge cases |
| Code review | 0.10 - 1 | Thoughtful review comments |
| Documentation | 0.25 - 2 | Guides, examples, API docs |
| Bug fix (major) | 1 - 5 | Complex debugging, security |
| Feature (small) | 2 - 10 | New component, utility |
| Design work | 2 - 15 | UI/UX designs, assets |
| Feature (medium) | 10 - 50 | Significant capability |
| Feature (large) | 50 - 150 | Major new functionality |
| Exceptional | 150 - 500 | Heroic, foundational work |
Final amounts determined by maintainers based on actual impact.
| Tacos | Status |
|---|---|
| 1+ | Contributor |
| 10+ | Regular |
| 50+ | Core Contributor |
| 100+ | MVP |
| 500+ | Legend 🏆 |
- A record of your contribution history
- A "thank you" from the community
- Possibly considered for future opportunities (no promises)
- Not money (no cash value)
- Not transferable
- Not a guarantee of anything
View the Contributor Ledger (or ask a maintainer).
- Use Prettier defaults
- Write meaningful commit messages
- Keep PRs focused and reviewable (<400 lines preferred)
type(scope): description
[optional body]
[optional footer]
Types: feat, fix, docs, style, refactor, test, chore
- Add tests for new features
- Ensure existing tests pass
- Manual testing notes appreciated
- ADHD productivity tools (see roadmap)
- Legal empowerment features
- Accessible, thoughtful UI/UX
- Local-first data patterns
- Expanding mobile apps to a web application and vice versa
- Recommending best practices that aren't be executed on
- Recommending code efficiencies and refactorization
- Bug fixes and performance improvements
- Documentation and examples
- Accessibility improvements
- Test coverage
- Large architectural changes
- New dependencies
- Scope changes to existing features
Open an issue or discussion before starting major work.
- Update documentation if needed
- Add tests for new functionality
- Ensure CI passes
- Request review from maintainers
- Respond to feedback constructively
PRs are usually reviewed within 1 week. Complex PRs may take longer. Be ready to explain your code. We do not shy from vibe coding but you need to make sure you explain your code. If you make large commits be prepared to spend a significant amount of time on it.
- Be respectful and constructive
- Assume good intent
- Help others learn
- Credit others' work
- See Code of Conduct
Contributors are recognized in:
CONTRIBUTORS.mdfile- Release notes for significant contributions
- TACO Token ledger
- Annual contributor highlights
Thank you for helping build technology that respects people.