README (2ad72058bc680e30f084e9f9ba8ceb0f77386821) README (bde2df36223c26750e6e5e801907d885e088ee30)
1illumos gate README - Sept 12, 2010.
1illumos gate README - Sep 16, 2012.
2
3This is the illumos gate. This is the illumos source tree. It contains
4the following subdirectories:
5
6 usr/src - The actual source code
7
8 exception_lists - These are lists of exceptional cases
9 used to limit noise during builds.
10 Ideally this directory would consist of
11 only empty files.
12
13Integration Rules:
14
2
3This is the illumos gate. This is the illumos source tree. It contains
4the following subdirectories:
5
6 usr/src - The actual source code
7
8 exception_lists - These are lists of exceptional cases
9 used to limit noise during builds.
10 Ideally this directory would consist of
11 only empty files.
12
13Integration Rules:
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
17 advocate, but the final integration should still be approved by the
18 advocate.
19
20 The advocate will want to see your webrev and hg outgoing -v. The
21 advocate will also ask about your testing, and may ask to see your
22 build logs.
23
24 All changes must adhere to typical ON style and quality rules.
25 For example, pass full cstyle, applicable lint rules, etc.
26
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
18 advocate.
19
20 The advocate will want to see your webrev and hg outgoing -v. The
21 advocate will also ask about your testing, and may ask to see your
22 build logs.
23
24 All changes must adhere to typical ON style and quality rules.
25 For example, pass full cstyle, applicable lint rules, etc.
26
27 All commits must include either a CDDL license, unless
28 approved otherwise by the gatekeeper, or the modified code
29 already carries a different license. Exceptions shall require
30 the approval of the gatekeeper.
27 All new code must be licensed under CDDL, and modifications to existing
28 code may not alter the original license terms. Integrations of code
29 from upstream sources that use another liberal open source license are
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
34 1234 This is a sample bug report synopsis
35
36 1234 This is a sample bug report synopsis
35 4567 If you have a second bug synopsis...
36 Reviewed by: codereviewer@somewhere.net
37 Approved by: gatekeeper@somewhere.else.com
37 4567 If you have a second bug synopsis…
38 Reviewed by: Frodo Baggins <frodo.baggins@underhill.net>
39 Reviewed by: Legolas <elf-coder@mirkwood.org>
40 Approved by: Gandalf The Grey <rti-advocate@white-council.com>
38
39 Each commit must have at least one bug id that is listed in the
40 illumos-gate project at www.illumos.org.
41
41
42 Each commit must have at least one bug id that is listed in the
43 illumos-gate project at www.illumos.org.
44
42Branches:
45RTI Advocates: advocates@lists.illumos.org
46Developer Council: developer-council@lists.illumos.org
43
47
44 Please talk to the gatekeeper about personal branches. In general,
45 they will be allowed as long as we don't go *too* wild on them.
46
47Gatekeeper: garrett@nexenta.com (Interim)
48IRC channel: #illumos on irc.freenode.net
49Mailing list: developer@lists.illumos.org
50
48IRC channel: #illumos on irc.freenode.net
49Mailing list: developer@lists.illumos.org