Contributing: Getting Started
Thank you for your interest in contributing to Trial Submission Studio!
Ways to Contribute
Code Contributions
- Bug fixes
- New features
- Performance improvements
- Documentation updates
Non-Code Contributions
- Bug reports
- Feature requests
- Documentation improvements
- Testing and feedback
- Helping other users
Before You Start
Prerequisites
- Rust 1.92+ - Install via rustup
- Git - For version control
- Basic familiarity with Rust programming
- (Optional) Understanding of CDISC SDTM standards
Read the Documentation
Familiarize yourself with:
Finding Issues to Work On
GitHub Issues
- Check GitHub Issues
- Look for labels:
good-first-issue- Great for newcomershelp-wanted- We’d love assistancebug- Known issues to fixenhancement- New features
Claiming an Issue
- Find an issue you want to work on
- Comment on the issue expressing interest
- Wait for maintainer feedback before starting
- Fork the repository
- Create a branch and start working
Contribution Workflow
Overview
1. Find Issue → 2. Comment → 3. Fork → 4. Branch → 5. Code → 6. Test → 7. PR
Detailed Steps
- Find an issue (or create one)
- Comment to claim it
- Fork the repository
- Clone your fork
- Create a branch (
feature/my-featureorfix/my-fix) - Make changes
- Test your changes
- Commit with conventional commit messages
- Push to your fork
- Create a Pull Request
Communication
Where to Discuss
- GitHub Issues - Bug reports, feature requests
- GitHub Discussions - Questions, ideas, general discussion
- Pull Requests - Code review discussion
Guidelines
- Be respectful and constructive
- Assume good intentions
- Welcome newcomers
- Focus on the code, not the person
Code of Conduct
Please read and follow our Code of Conduct.
Key points:
- Be respectful and inclusive
- Welcome newcomers
- Focus on constructive feedback
- Assume good intentions
Getting Help
Stuck on Something?
- Check existing documentation
- Search GitHub Issues/Discussions
- Ask in GitHub Discussions
- Open an issue with your question
Review Process
After submitting a PR:
- Automated checks run (CI)
- Maintainer reviews code
- Address any feedback
- Maintainer merges when ready
Recognition
Contributors are recognized in:
- GitHub contributor list
- Release notes (for significant contributions)
- THIRD_PARTY_LICENSES.md (if adding dependencies)
Next Steps
- Development Setup - Set up your environment
- Coding Standards - Code style guide
- Testing - Testing guidelines
- Pull Requests - PR guidelines