Rule of Shared Repository » 履歴 » バージョン 1
Kousuke Ebihara, 2009-10-06 20:53
Wrote Rule of Shared Repository
| 1 | 1 | Kousuke Ebihara | h1. Rule of Shared Repository |
|---|---|---|---|
| 2 | |||
| 3 | h2. Overview |
||
| 4 | |||
| 5 | This document provides rule of handling shared repository of developing OpenPNE3. |
||
| 6 | |||
| 7 | In this document, the "shared repository" means that is git://github.com/openpne/OpenPNE3.git. |
||
| 8 | |||
| 9 | Everyone must follow this rule to handle the shared repository. |
||
| 10 | |||
| 11 | h2. Repository Collaborators |
||
| 12 | |||
| 13 | Repository collaborators can handle the shared repository. |
||
| 14 | |||
| 15 | The following is the list of current collaborators (as of October 6, 2009): |
||
| 16 | * "ebihara":https://github.com/ebihara |
||
| 17 | * "balibali":https://github.com/balibali |
||
| 18 | * "ShinichiU":https://github.com/ShinichiU |
||
| 19 | * "fukamachi":https://github.com/fukamachi |
||
| 20 | * "uzura8":https://github.com/uzura8 |
||
| 21 | * "nothan":https://github.com/nothan |
||
| 22 | * "kawahara":https://github.com/kawahara |
||
| 23 | |||
| 24 | If you think that you are worthy of repository collaborators, please tell your GitHub account to ebihara@tejimaya.com. |
||
| 25 | |||
| 26 | h2. Committing |
||
| 27 | |||
| 28 | h3. Direct Committing |
||
| 29 | |||
| 30 | Committing direct is not allowed excepting few cases. |
||
| 31 | |||
| 32 | Release Manager can directly commit when he works for releasing. |
||
| 33 | |||
| 34 | In other cases, anyone must work in his own clone. |
||
| 35 | |||
| 36 | h3. Commit Messages |
||
| 37 | |||
| 38 | In merging, commit messages must follow the following rule: |
||
| 39 | * A message must be written in English. A message can contain other languages, but that must be explained in English. |
||
| 40 | * A message must contain related ticket ID. The ID must be specified with "refs" or "fixes" keyword. We have useful hook for keeping it: http://gist.github.com/202866 |
||
| 41 | e.g. "Added ability to delete member from the mobile_backend application (refs #1)", "Added ability to configure gadgets from the mobile_backend application. Adding support to manage SNS from mobile is now completed. (fixes #1)" |
||
| 42 | * A message must tell everyone what the commit is. |
||
| 43 | |||
| 44 | A commit that doesn't follow this rule, most likely is rejected. |
||
| 45 | |||
| 46 | h2. Merging |
||
| 47 | |||
| 48 | If you developed something or got "Pull Request", please merge it. After merging, you must check changes. If the changes has some faults, contact author about it to fix them. |
||
| 49 | |||
| 50 | If changes looks fine, push it to shared repository, and change a status of the related ticket to "Pending Review". |