User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
cppdev:submitpatches [2010-11-04 16:44] Carsten Fixed e-mail links |
cppdev:submitpatches [2012-04-10 22:32] Carsten [Mechanics of Patch Submission] clarified the text |
||
|---|---|---|---|
| Line 50: | Line 50: | ||
| === Make atomic patches === | === Make atomic patches === | ||
| - | Do not split a single code change into multiple patches. A patch should be self-contained -- //one patch for one thing//. | + | A patch should be self-contained -- //one patch for one thing//. |
| - | A patch that adds bitmaps to menu items and fixes a bug in the network code is a bad patch. It should be splitted into two patches. On the other hand, two patches, one of them being "implementation of new member-functions", the other "changes in class description to accommodate new members" are two bad patches. They are related to one, logically indivisible thing, so they should be part of one patch. | + | Do not combine multiple new features in a single patch: |
| + | A patch that adds bitmaps to menu items and fixes a bug in the network code is a bad patch. It should be splitted into two patches. | ||
| - | Another example: if you adapted the build system to work on a new, previously unsupported platform, we would gladly accept your patch. Just send us single patch, not 10 patches, one for each modified file. | + | On the other hand, do not split a single code change into multiple patches: |
| + | Two patches, one of them being "implementation of new member-functions", the other "changes in class documentation to accommodate new members" are two bad patches. They are related to one, logically indivisible thing, so they should be in one common patch. | ||
| Line 94: | Line 96: | ||
| * The authorship and all credits remain with you. Your contributions will clearly carry your name and everything gets properly documented in our changelog (unless you tell us otherwise). | * The authorship and all credits remain with you. Your contributions will clearly carry your name and everything gets properly documented in our changelog (unless you tell us otherwise). | ||
| + | |||
| + | * Once your code has been integrated into Cafu, we assume maintenance for it as for everything else. That means that we make sure that the code will still work after future changes, in future releases, on future platforms, etc. | ||
| * Any money we earn from selling commercial licenses is spent on the development and continued enhancement of Cafu. The code, insight and knowledge that we obtain from additional budget or manpower is directly given back to the community (most prominently in the form of commits to the [[cppdev:gettingstarted|Cafu source code repository]]). | * Any money we earn from selling commercial licenses is spent on the development and continued enhancement of Cafu. The code, insight and knowledge that we obtain from additional budget or manpower is directly given back to the community (most prominently in the form of commits to the [[cppdev:gettingstarted|Cafu source code repository]]). | ||
cppdev/submitpatches.txt · Last modified: 2017-02-05 13:37 by Carsten