-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Created an ISSUE_TEMPLATE folder with the bounty.md file
- Loading branch information
1 parent
12a6651
commit 4f7c835
Showing
1 changed file
with
34 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
**Bounty description** | ||
|
||
A clear and concise description of the project; should be accessible to a contributor with minimal context. | ||
|
||
**Implementation requirements** | ||
|
||
A clear and comprehensive list of the requirements for the bounty to be considered complete. | ||
|
||
- [ ] Task 1 | ||
- Subtasks (if relevant) | ||
- [ ] Task 2 | ||
- Subtasks (if relevant) | ||
- [ ] Task 3 | ||
- Subtasks (if relevant) | ||
|
||
**Bonus features** | ||
|
||
Any additional features that will enhance the value of the bounty. | ||
|
||
- [ ] Bonus Feature 1 | ||
- [ ] Bonus Feature 2 | ||
|
||
**Resources** | ||
|
||
A list of potentially-useful resources. This list should be less than 5 total resources. | ||
|
||
**Criteria** | ||
|
||
For timely submissions of bounties that meet the implementation requirements, a bounty of at least $250 will be awarded to the contributor. Additional bounty amounts are available and will be rewarded based on the following criteria: | ||
|
||
1. Completion of any of the bonus features listed above and/or other bonus features that improve the quality of the submission. | ||
2. Correctness and security: A thorough review of the implementation should convince our team that they are correct and secure, with all requirements met. | ||
3. Code clarity and quality: Succinct, easy-to-follow code with appropriate naming conventions. Utilize Rust’s type system for flexibility and security (e.g., compile-time checks where possible), and avoid external crates. Optimizations should be a lower priority than clarity, but can be included behind a feature flag as a bonus. | ||
4. Documentation quality: Provide comprehensive README’s, Cargo docs, and inline comments where code itself is not self-explanatory. Prioritize clarity and readability. |