Difference between revisions of "Contribute"
Jump to navigation
Jump to search
PeterSurda (talk | contribs) (Created page with "==Code contributions to the Bitmessage project== The best code contributions are pull requests on https://github.com/Bitmessage/PyBitmessage. Here are some rules to follow:...") |
PeterSurda (talk | contribs) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Code contributions to the Bitmessage project== | ==Code contributions to the Bitmessage project== | ||
| − | The best code contributions are pull requests on https://github.com/Bitmessage/PyBitmessage. Here are some rules to follow: | + | The best code contributions are pull requests on [https://github.com/Bitmessage/PyBitmessage GitHub]. Here are some rules to follow: |
* try to explain what the code is about | * try to explain what the code is about | ||
| − | * try to follow https://www.python.org/dev/peps/pep-0008/ | + | * try to follow [https://www.python.org/dev/peps/pep-0008/ PEP0008] |
| − | * make the pull request against the | + | * make the pull request against the [https://github.com/Bitmessage/PyBitmessage/tree/v0.6 "v0.6" branch] |
| − | * it should be possible to do a fast-forward merge of the pull requests | + | * it should be possible to do a fast-forward merge of the pull requests. I.e. if possible, do a rebase of a pull request after another is merged ahead of yours. However, if it can be merged without having to manually resolve a conflict, that's acceptable as well. |
* PGP-sign the commits included in the pull request | * PGP-sign the commits included in the pull request | ||
| + | * You can get paid for merged commits if you register at [https://tip4commit.com/github/Bitmessage/PyBitmessage Tip4Commit] | ||
If for some reason you don't want to use github, you can submit the patch using Bitmessage to the "bitmessage" chan, or to one of the developers. | If for some reason you don't want to use github, you can submit the patch using Bitmessage to the "bitmessage" chan, or to one of the developers. | ||
| Line 13: | Line 14: | ||
==Translations== | ==Translations== | ||
| − | For helping with translations, please use https://www.transifex.com/bitmessage-project/pybitmessage/. There is no need to submit pull requests for translations. | + | For helping with translations, please use [https://www.transifex.com/bitmessage-project/pybitmessage/ Transifex]. There is no need to submit pull requests for translations. |
| + | |||
| + | For translating technical terms it is recommended to consult the [https://www.microsoft.com/Language/en-US/Default.aspx Microsoft Language Portal]. | ||
Revision as of 00:51, 28 February 2018
Code contributions to the Bitmessage project
The best code contributions are pull requests on GitHub. Here are some rules to follow:
- try to explain what the code is about
- try to follow PEP0008
- make the pull request against the "v0.6" branch
- it should be possible to do a fast-forward merge of the pull requests. I.e. if possible, do a rebase of a pull request after another is merged ahead of yours. However, if it can be merged without having to manually resolve a conflict, that's acceptable as well.
- PGP-sign the commits included in the pull request
- You can get paid for merged commits if you register at Tip4Commit
If for some reason you don't want to use github, you can submit the patch using Bitmessage to the "bitmessage" chan, or to one of the developers.
Translations
For helping with translations, please use Transifex. There is no need to submit pull requests for translations.
For translating technical terms it is recommended to consult the Microsoft Language Portal.
