-
-
Notifications
You must be signed in to change notification settings - Fork 752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update docs bounty (44) #5455
Comments
Might take a look at this. Quick question though, what's the distinction between a "small" and a "bigger" issue? |
there is no strict definition, but I'ld say if you just fix a few typos or grammar errors, that would be a small (but welcome) change. if it is definitely more, then it is a big change. |
All done! |
https://www.bountysource.com/issues/93673046-update-docs-bounty-44 @rpolley claim the bounty there! :-) |
@rpolley do you want to claim the bounty? |
ping @rpolley ... |
Hmm, somehow @rpolley is unresponsive since almost 6 months so I assume not interested in claiming the bounty. So I will claim the bounty in his place and donate it back to borgbackup organization funds. |
I created this bounty and paid for it personally to give back the USD 30, see previous comment: https://www.bountysource.com/issues/99918230-update-docs-30-bounty-48 |
@ThomasWaldmann sorry about being unresponsive, I was a bit busy irl and kind of forgot about this. I'm fine with the bounty being put back in, call it a donation. |
@rpolley thanks! |
there are quite some docs issues: documentation
grab some doc update issues, create a PR against master (and, after discussion, also to 1.1-maint, if applicable, see here, also linked from PR submission template)
the bounty is for fixing 2 small issues or 1 bigger issue.
docs issues that already have a bounty on them do not qualify.
💰 there is a bounty for this
The text was updated successfully, but these errors were encountered: