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 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 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. 33 34 Commits should have comments of the following form: 35 36 1234 This is a sample bug report synopsis 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> 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 45RTI Advocates: advocates@lists.illumos.org 46Developer Council: developer-council@lists.illumos.org 47 48IRC channel: #illumos on irc.freenode.net 49Mailing list: developer@lists.illumos.org 50