Repository navigation
docs(contributing): add a Drips Wave contribution section - #496
Merged
Merged
Conversation
Roughly 40 open issues carry the Stellar Wave label but CONTRIBUTING.md never mentions the Wave workflow. Add a section covering what the label means, the difficulty-to-points mapping (Trivial 100 / Medium 150 / High 200) as sizing rather than a payout promise, and the Wave-specific requirement that the issue be assigned in the Wave app before work starts so the contribution can be credited. Also adds the table-of-contents entry.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs-only change.
Roughly 40 open issues in this repository carry the
Stellar Wavelabel, butCONTRIBUTING.mdnever explains what that label means or how the Wave workflow differs from a normal contribution. Contributors arriving from the Drips Wave app get the labels and the issue-selection rules, but miss the one Wave-specific requirement: the issue must be assigned to you in the Wave app before you start, otherwise the work cannot be credited.What changed
## Drips Wave contributionssection toCONTRIBUTING.mdcovering:Stellar Wavelabel means, and howdifficulty/*maps to the program's base point values (Trivial 100 / Medium 150 / High 200) as sizing, with the actual points set by the maintainer in the Drips dashboard when the issue is added to the program;Closes #123, tests, conventions);ruff/black/commit conventions, tell maintainers early if you cannot finish).The wording matches how the Wave program actually works per the Drips Wave docs (applying notifies the maintainer, "the issue is only yours once the maintainer officially assigns you", points 100/150/200 by complexity), and it mirrors the equivalent guide already in the sibling repository (
AyinkxLab/stellar-contract-platform,docs/WAVE.md).No code, tests, or configuration touched, so CI should be unaffected.