-
-
Notifications
You must be signed in to change notification settings - Fork 753
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 (37) #5129
Comments
Is this still available? |
@braewoods sure! |
@ThomasWaldmann I noticed the source code includes a copy of the manpage documentation. How is that intended to be updated? |
man pages and parts of the docs are generated from archiver.py. |
Ok, since those 2 are merged now and back-ported, the work for this issue should be all done. Can you close it please? |
thanks! |
@braewoods you can claim the bounty now. |
@ThomasWaldmann Thanks. I've filed a claim. Now if I could just get a cash out... |
You've just to request that from BS. IIRC they process cash outs once a week. |
That's what the official sources say but the reality is they've stopped processing them that I can tell. Their website repository is littered with people complaining about it and I've been waiting over 2 weeks for my cash out request. |
See here: bountysource/core#1539 |
Thanks for informing me about this. Let's hope they get their stuff fixed soon. |
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: