| Line | Revision | Contents |
| 1 | 10 | Coding Style |
| 2 | ------------ |
|
| 3 | 5 | |
| 4 | Please keep the existing coding style. |
|
| 5 | You should see http://www.python.org/dev/peps/pep-0008/ |
|
| 6 | 6 | We recomend you use Pylint (http://www.logilab.org/857/) to check code. |
| 7 | 5 | |
| 8 | All documentation and code should be in US English. |
|
| 9 | ||
| 10 | 10 | Source Code Repository |
| 11 | ---------------------- |
|
| 12 | 5 | |
| 13 | Nhopkg uses Bazaar as version control system (http://bazaar-vcs.org/). |
|
| 14 | You can access the code repository in several ways. |
|
| 15 | ||
| 16 | With write permissions. |
|
| 17 | $ bzr+ssh://<your_user>@nhopkg.bzr.sourceforge.net/bzrroot/nhopkg |
|
| 18 | ||
| 19 | Without write permissions. |
|
| 20 | $ bzr co bzr://nhopkg.bzr.sourceforge.net/bzrroot/nhopkg |
|
| 21 | ||
| 22 | If you prefer, you can access the code through web interface at |
|
| 23 | http://nhopkg.bzr.sourceforge.net/bzr/nhopkg/changes |
|
| 24 | ||
| 25 | 10 | Create and Send Patches |
| 26 | ----------------------- |
|
| 27 | 5 | |
| 28 | You can create patches in two ways, using 'bzr diff' or gnu 'diff' |
|
| 29 | commands. We prefer first option. |
|
| 30 | ||
| 31 | An example using first option. |
|
| 32 | $ cd nhopkg-bzr |
|
| 33 | ||
| 34 | (make your changes here) |
|
| 35 | [...] |
|
| 36 | ||
| 37 | $ bzr diff nhopkg-some-explaining-name-1.patch |
|
| 38 | ||
| 39 | If you prefer to use the second way, the last command should be |
|
| 40 | $ diff -Naur nhopkg-bzr.orig nhopkg-bzr > nhopkg-some-explaining-name-2.patch |
|
| 41 | ||
| 42 | To send us your new patch, write a mail to our Development Mailing List |
|
| 43 | at <nhopkg-svn@lists.sourceforge.net> and add a short description of |
|
| 44 | 9 | your changes. |
| 45 | ||
| 46 | 10 | Translations |
| 47 | ------------ |
|
| 48 | 9 | |
| 49 | To Do ... |
Loggerhead 1.17 is a web-based interface for Bazaar branches