プロジェクト

全般

プロフィール

Rule of Shared Repository » 履歴 » バージョン 8

Kousuke Ebihara, 2014-01-30 20:06

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 6 Kousuke Ebihara
h2. "push" privilege to handle shared repository
12 1 Kousuke Ebihara
13 6 Kousuke Ebihara
GitHub accounts that are in the following list, can execute "push" operations to shared repository (as of Nov 22, 2012):
14 1 Kousuke Ebihara
15
* "balibali":https://github.com/balibali
16 6 Kousuke Ebihara
* "imamura623":https://github.com/imamura623
17
* "kashiwasan":https://github.com/kashiwasan
18 1 Kousuke Ebihara
* "kawahara":https://github.com/kawahara
19 6 Kousuke Ebihara
* "martini2002jp":https://github.com/martini2002jp
20
* "niryuu":https://github.com/niryuu
21
* "nise-nabe":https://github.com/nise-nabe
22
* "ShinichiU":https://github.com/ShinichiU
23
* "tejima":https://github.com/tejima
24
* "touri":https://github.com/touri
25
* "upsilon":https://github.com/upsilon
26 1 Kousuke Ebihara
27 8 Kousuke Ebihara
If you think that you are worthy of getting "push" privilege, please tell your GitHub account to balibali, or ShinichiU.
28 1 Kousuke Ebihara
29
h2. Committing
30
31
h3. Direct Committing
32
33
Committing direct is not allowed excepting few cases.
34
35
Release Manager can directly commit when he works for releasing.
36
37
In other cases, anyone must work in his own clone.
38
39
h3. Commit Messages
40
41
In merging, commit messages must follow the following rule:
42
* A message must be written in English. A message can contain other languages, but that must be explained in English.
43 2 Kousuke Ebihara
* A message must contain related ticket ID. The ID must be specified with "refs" or "fixes" keyword. We have useful hook script for keeping it: http://gist.github.com/202866
44 1 Kousuke Ebihara
   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)"
45
* A message must tell everyone what the commit is.
46
47
A commit that doesn't follow this rule, most likely is rejected.
48
49
h2. Merging
50
51
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.
52
53 3 Kousuke Ebihara
If changes looks fine, push it to shared repository, and change a status of the related ticket to "Pending Review". (Changing status is doing automatically if a commit is related with a ticket by the "fixes" keyword in its message)
54 5 Kousuke Ebihara
55
h2. Branches
56
57
Branches of the shared repository must limit the release branches (they contain the master branch). Don't push a branch for your work. You should create such a branch to your repository.