1 illumos gate README - Sept 12, 2010. |
1 illumos gate README - Sep 16, 2012. |
2 |
2 |
3 This is the illumos gate. This is the illumos source tree. It contains |
3 This is the illumos gate. This is the illumos source tree. It contains |
4 the following subdirectories: |
4 the following subdirectories: |
5 |
5 |
6 usr/src - The actual source code |
6 usr/src - The actual source code |
10 Ideally this directory would consist of |
10 Ideally this directory would consist of |
11 only empty files. |
11 only empty files. |
12 |
12 |
13 Integration Rules: |
13 Integration Rules: |
14 |
14 |
15 All changes must have been reviewed, and approved by and advocate |
15 All changes must have been reviewed, and approved by an advocate |
16 (below). A code review may be performed by someone other than the |
16 (below). A code review may be performed by someone other than the |
17 advocate, but the final integration should still be approved by the |
17 advocate, but the final integration should still be approved by the |
18 advocate. |
18 advocate. |
19 |
19 |
20 The advocate will want to see your webrev and hg outgoing -v. The |
20 The advocate will want to see your webrev and hg outgoing -v. The |
22 build logs. |
22 build logs. |
23 |
23 |
24 All changes must adhere to typical ON style and quality rules. |
24 All changes must adhere to typical ON style and quality rules. |
25 For example, pass full cstyle, applicable lint rules, etc. |
25 For example, pass full cstyle, applicable lint rules, etc. |
26 |
26 |
27 All commits must include either a CDDL license, unless |
27 All new code must be licensed under CDDL, and modifications to existing |
28 approved otherwise by the gatekeeper, or the modified code |
28 code may not alter the original license terms. Integrations of code |
29 already carries a different license. Exceptions shall require |
29 from upstream sources that use another liberal open source license are |
30 the approval of the gatekeeper. |
30 permissible, subject to approval of the advocates or developer council. |
|
31 Exceptions to this policy shall require the approval of the developer |
|
32 council. |
31 |
33 |
32 Hg commits should have comments of the following form: |
34 Commits should have comments of the following form: |
33 |
35 |
34 1234 This is a sample bug report synopsis |
36 1234 This is a sample bug report synopsis |
35 4567 If you have a second bug synopsis... |
37 4567 If you have a second bug synopsis… |
36 Reviewed by: [email protected] |
38 Reviewed by: Frodo Baggins <[email protected]> |
37 Approved by: [email protected] |
39 Reviewed by: Legolas <[email protected]> |
|
40 Approved by: Gandalf The Grey <[email protected]> |
38 |
41 |
39 Each commit must have at least one bug id that is listed in the |
42 Each commit must have at least one bug id that is listed in the |
40 illumos-gate project at www.illumos.org. |
43 illumos-gate project at www.illumos.org. |
41 |
44 |
42 Branches: |
45 RTI Advocates: [email protected] |
|
46 Developer Council: [email protected] |
43 |
47 |
44 Please talk to the gatekeeper about personal branches. In general, |
48 IRC channel: #illumos on irc.freenode.net |
45 they will be allowed as long as we don't go *too* wild on them. |
49 Mailing list: [email protected] |
46 |
|
47 Gatekeeper: [email protected] (Interim) |
|
48 IRC channel: #illumos on irc.freenode.net |
|
49 Mailing list: [email protected] |
|
50 |
|