Bring RP documentation/website up to date
What is the nature of the proposed bounty?
This bounty is read through all RP documentation, as well as rocketpool.net, and find outright errors due to age. Things like references to the upcoming merge, active 5-20% commission, 15% default commission, etc, etc.
The outputs are:
- A PR for docs.rocketpool.net
- A document detailing errors in the website with proposed fixes; this can’t be a PR because the repository is not open, but should serve the same purpose
Must the results of this project be entirely open source (MIT, GPL, Apache, CC BY license or similar)? If not, which parts will not be, why, and under what license will they be published?
Yes for the documentation part.
No for the website part. The website part must be a published document with a license that read:
License
Permission is hereby granted to Rocketpool Pty Ltd. to use this content without restriction.
The content is provided “as is”, without warranty of any kind.
Benefits - enter N/A where appropriate
The benefit is less confusion. At a guess this mostly applies to NOs because they use the most documentation, but it applies wherever an update is needed and found.
If the bounty is successfully completed, how does this help people looking to stake ETH for rETH?
See above.
If the bounty is successfully completed, how does this help rETH holders?
See above.
If the bounty is successfully completed, how does this help people looking to run a Rocket Pool node for the first time?
See above.
If the bounty is successfully completed, how does this help people already running a Rocket Pool node?
See above.
If the bounty is successfully completed, how does this help the Rocket Pool community?
See above.
If the bounty is successfully completed, how does this help RPL holders?
See above.
What other non-RPL protocols, DAOs, projects, or individuals, would stand to benefit from the bounty being successfully completed?
None
Will the results of the completed bounty be open source?
Partly.
Work and Verification
What steps would be entailed in completing the bounty? Do successful examples of such work exist elsewhere?
- Document for website issues
- Anything visible that supports copy-paste is ok
- Identify the issue clearly (link to page, section of text)
- Show current status
- Provide suggested improvement
- PR for docs.rocketpool.net
- There have been many PRs along these lines, but no full readthrough for this purpose
- A comment in the PR should link to the website document
How long is the proposed bounty available for? Is it awarded to the first team to successfully claim it, or is it in some way divided among all such successful claims in the proposed availability period?
First to submit gets credit for what they post. The bounty SHALL remain open for 1 month after this first submission. From then on, submitters are only credited for new issues found that have not yet been submitted. The GMC will weight the relative contributions based on the issues each entity is credited with; this may be a little loose, and that’s ok.
Who will test any products submitted for claiming the bounty?
N/A
What is the acceptance criteria for awarding of the bounty?
PR accepted; issues accepted for inclusion on website.
Payment
How much RPL is the applicant requesting for successful completion of the bounty?
$1000
Conflict of Interest
Does the person or persons proposing the bounty have any conflicts of interest to disclose? (Please disclose here if you are a member of the GMC or if any member of the GMC would benefit directly financially from the successful completion of the bounty).
No, though there’s some chance I will participate if it lingers
Will the applicant, or any protocol or project in which the applicant has a vested interest (other than Rocket Pool), benefit financially if the bounty is successfully completed?
No