1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 96-100
      3. Builds 91-95
      4. Builds 86-90
      5. Builds 81-85
      6. Builds 76-80
      7. Builds 71-75
      8. Builds 66-70
      9. Builds 61-65
      10. Builds 56-60
      11. Builds 51-55
      12. Builds 46-50
      13. Builds 41-45
      14. Builds 36-40
      15. Builds 31-35
      16. Builds 26-30
      17. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

6 Integration Procedure

The integration procedure is documented at http://opensolaris.org/os/community/onnv/os_dev_process/.

6.1 Code Review Process

Code review is the ``last defense against brokenness.'' It is a critical part of the development process: no change can be putback by anyone, no matter how knowledgeable or experienced, without first being reviewed. As a version nears release, code review requirements become more strict; more reviewers may be required. The code review process can take anywhere from a few minutes to many hours, depending on the type, size, and intrusiveness of the changes being made. Normally, developers will ask others to review their changes who are familiar with the code being modified.

The purpose of code review is to find subtle and non-obvious problems with the changes being made, not to absolve the implementor of responsibility for his or her changes. Specifically, developers must conduct their own self-review and testing before requesting a formal code review.

6.2 Licensing Requirements

All code integrated into OpenSolaris by a Sun employee must contain the usual Sun copyright notice (see 7.2.3 Non-formatting Considerations). The code will then be licensed by Sun Microsystems both as part of the OpenSolaris project and to other customers via various Solaris and other licenses. Thus, licensing is not a concern for Sun employees.

In order to contribute code to OpenSolaris, developers who are not Sun employees or contractors will need to enter into a contributor agreement. A contributor agreement assures the community that contributors have sufficient rights to the code being contributed, and that any third party intellectual property issues are disclosed. It also allows defense of OpenSolaris should there be a legal dispute regarding the software at some time in the future.

Contributors who add significant changes to an existing file or add new files may include a brief copyright notice similar to the standard Sun copyright notice. See 7.2.3 Non-formatting considerations and the contributor agreement for more information.

---