Skip to content

Latest commit

 

History

History
50 lines (32 loc) · 1.99 KB

File metadata and controls

50 lines (32 loc) · 1.99 KB

Drips Wave Contributor Guide

Overview

The Drips Wave program rewards contributors for fixing issues in the Checkmate-Escrow project. This guide explains how to participate, claim wave-ready issues, understand point values, and submit your work.

How to Participate

  1. Find Wave-Ready Issues: Look for issues labeled with "wave-ready" in the GitHub repository. These issues have been vetted and are ready for contribution.

  2. Claim an Issue: Comment on the issue you'd like to work on with "/wave claim" to indicate your intent to fix it. First-come, first-served.

  3. Work on the Issue: Fork the repository, create a feature branch, and implement the fix. Follow the project's coding standards and include tests where appropriate.

  4. Submit Your Work: Create a pull request with your changes. Include a clear description of what was fixed and how.

Point Values

Issues are assigned point values based on complexity and impact:

  • Low (1-5 points): Simple bug fixes, documentation updates, minor improvements
  • Medium (6-15 points): Feature additions, moderate refactoring, test coverage improvements
  • High (16-30 points): Major features, significant architectural changes, security fixes

Point values are listed in each wave-ready issue description.

Submission Process

  1. Ensure your code follows the project's style guidelines
  2. Include appropriate tests for any code changes
  3. Update documentation if necessary
  4. Create a pull request with a descriptive title and body
  5. Reference the original issue number in your PR description

Rewards

Points earned through contributions can be redeemed for various rewards, including:

  • Direct payments via Stellar
  • Project merchandise
  • Recognition on the contributor leaderboard
  • Priority access to future features

Getting Help

If you need assistance:

  • Check the README.md for setup instructions
  • Review existing issues and PRs for examples
  • Ask questions in the issue comments or project discussions

Happy contributing!