OLD | NEW |
(Empty) | |
| 1 ============ |
| 2 Contributing |
| 3 ============ |
| 4 |
| 5 For more information, please see the official contribution docs at |
| 6 http://docs.pythonboto.org/en/latest/contributing.html. |
| 7 |
| 8 |
| 9 Contributing Code |
| 10 ================= |
| 11 |
| 12 * A good patch: |
| 13 |
| 14 * is clear. |
| 15 * works across all supported versions of Python. |
| 16 * follows the existing style of the code base (PEP-8). |
| 17 * has comments included as needed. |
| 18 |
| 19 * A test case that demonstrates the previous flaw that now passes |
| 20 with the included patch. |
| 21 * If it adds/changes a public API, it must also include documentation |
| 22 for those changes. |
| 23 * Must be appropriately licensed (New BSD). |
| 24 |
| 25 |
| 26 Reporting An Issue/Feature |
| 27 ========================== |
| 28 |
| 29 * Check to see if there's an existing issue/pull request for the |
| 30 bug/feature. All issues are at https://github.com/boto/boto/issues |
| 31 and pull reqs are at https://github.com/boto/boto/pulls. |
| 32 * If there isn't an existing issue there, please file an issue. The ideal |
| 33 report includes: |
| 34 |
| 35 * A description of the problem/suggestion. |
| 36 * How to recreate the bug. |
| 37 * If relevant, including the versions of your: |
| 38 |
| 39 * Python interpreter |
| 40 * boto |
| 41 * Optionally of the other dependencies involved |
| 42 |
| 43 * If possible, create a pull request with a (failing) test case demonstrating |
| 44 what's wrong. This makes the process for fixing bugs quicker & gets issues |
| 45 resolved sooner. |
| 46 |
| 47 |
OLD | NEW |