Wiki code for How to Participate

Hide Line numbers
1: == Participate in OpenSolaris
2: 
3: === Use It
4: 
5: * [[Download>>Main.downloads]] the latest OpenSolaris release or the latest development build. You can also choose to run one of the many [[distributions>>Main.downloads]] based on OpenSolaris.
6: * [[Download source code>>Main.downloads]]. Pointers to build instructions will be available with download information. Or [[view source code online>>http://src.opensolaris.org]].
7: 
8: === Join a Collective
9: 
10:  There are three types of collectives on opensolaris.org. Pick an area that interests you, find out what’s going on in that area, subscribe to the mailing list(s) for the area of interest, start talking to people, and get involved.
11: 
12: * [[Community Groups>>Main.communities]]: social groups whose members engage in open conversations, that endorse technical projects and that have representation in the governance process.
13: * [[Projects>>Main.projects]]: collaborative technical efforts.
14: * [[User Groups>>Community Group advocacy.ug-leaders]]: independently-run groups around the world that advocate for OpenSolaris.
15: 
16: === Contribute
17: 
18: ==== Packages
19: 
20:  Any OpenSolaris registered user can contribute packages to the OpenSolaris /pending and /contrib package repositories under the [[Package Web Site Terms of Use>>http://pkg.opensolaris.org/license/contrib]]. Refer to the [[overivew>>Community Group sw-porters.contributing]] and the [[OpenSolaris Source Juicer Contrib Process>>Community Group sw-porters.jucrprocess]] for detailed information and instructions.
21: 
22: [[ [[image:reposbutton.png]] >>Community Group sw-porters.contributing]]  [[ [[image:pendingbutton.png]] >>Community Group sw-porters.jucrprocess]]
23: 
24: ==== Code
25: 
26:  The OpenSolaris project requires contributors to jointly assign their copyright on contributed code by signing and submitting a [[Sun Contributor Agreement>>Main.sun_contributor_agreement]]. Refer to the [[SCA FAQ>>Main.sca_faq]] for answers to your questions.
27: 
28:  To get started with software development for the OpenSolaris project, read about the existing [[communities>>Main.communities]] and [[projects>>Main.projects]] on the site and join mailing lists associated with those in which you are interested. After you learn about work in progress and have an idea of what you’d like to do, you can:
29: 
30: * Look for bugs to fix and work through the request-sponsor program.
31: * Get involved in an existing project directly.
32: * Start a project.
33: 
34:  Some ’bite-sized’ bugs have been identified by the Solaris engineers. These bugs are small and self-contained and are a good place to start. They are marked with the ’oss_bite_size’ keyword and are found by searching Sun’s bug database via bugs.opensolaris.org. See the current [[oss-bite-size bug list.>>http://bugs.opensolaris.org/bugdatabase/search.do?process=1&category=&subcategory=&bugStatus=open&type=&keyword=oss-bite-size&maxResults=10&startIndex=1&sortBy=relevance]]
35: 
36:  You can also look in [[defect.opensolaris.org>>http://defect.opensolaris.org]] for bugs filed against projects currently under development.
37: 
38:  If you want to work an existing bug/RFE, even one you filed, send email to **request DASH sponsor AT opensolaris DOT org**. Be sure to include:
39: 
40: * the Bug ID,
41: * the bug synopsis,
42: * your full name,
43: * the number assigned to your contributor agreement
44: 
45:  Someone will respond on list to volunteer to sponsor your work.
46: 
47:  Code being contributed via the Request Sponsor program is tracked on the [[request-sponsor table>>Main.request_sponsor]]. This table should be checked before requesting a sponsor to be sure work on it is not already in progress. Contributors can also send email to the request-sponsor list to ask for confirmation that no Sun engineer is already working on the particular bug/RFE.
48: 
49:  Your responsibilities with regard to contributing code include the following high-level phases (the number of steps in each phase will vary depending on the size and complexity of the change:
50: 
51: * development/implementation
52: * test
53: * reviews: code review (required); design and architectural review (if needed)
54: * documentation changes (if needed)
55: 
56:  Refer to the [[OpenSolaris Development Process document>>Community Group on.os_dev_process]] for more information.
57: 
58:  You can also join a project or start a new project. Refer to the instructions for starting a new project on the [[projects page>>Main.projects]].
59: 
60: ==== Bug Reports
61: 
62: There are two bug-tracking mechanisms available on opensolaris.org:
63: 
64: * [[bugs.opensolaris.org>>http://bugs.opensolaris.org]] allows the submission of bugs to Sun’s internal bug database and searching a subset of bugs from that bug database.
65: * [[defect.opensolaris.org>>http://defect.opensolaris.org]] is a public Bugzilla database. Many projects being developed on opensolaris.org use this database, and users of Sun’s OpenSolaris distributions are encouraged to use this database.
66: 
67:  For questions or discussion about specific code, the discussion list for the related project or community, or the opensolaris-code mailing list can be used.
68: 
69: ==== Documentation
70: 
71:  The long term goal of Sun’s Information Products department is to open source its Solaris feature documentation. In the interim, the [[Documentation community>>Community Group documentation.WebHome]] was set up to broaden the involvement in this initiative.
72: 
73: * Join the conversation by subscribing to the OpenSolaris Documentation discussion list.
74: * Contribute comments to current Solaris documentation that you find on docs.sun.com. Your input will eventually be rolled into the open source documents.
75: * Work as a subject matter expert with current Solaris writers who will document features, bug fixes and features that you contribute to OpenSolaris.
76: 
77:  In order to contribute to future OpenSolaris feature documentation, you will need to work through a sponsor. To obtain a sponsor, send a request through the OpenSolaris documentation discussion.
78: 
79: ==== Test
80: 
81:  Test development, frameworks, and execution are all important aspects of high quality software engineering efforts. The [[Testing community>>Community Group testing.WebHome]] is devoted to discussing and planning initiatives such as:
82: 
83: * OpenSolaris Test Suites: Test suites and benchmarks used to test the Solaris OS will be open sourced so they can be used by OpenSolaris developers to test their code.
84: * OpenSolaris Test Development: Test developers will be able to develop selected OpenSolaris test suites and start new OpenSolaris test projects.
85: * Self-Service Testing: A self-service regression and performance test capability is being developed that will allow OpenSolaris developers to submit test runs and review results.
86: * Build/Test Farm: A build server and test machine farm where OpenSolaris developers can build and test their code on a range of platforms is planned.
87: * Unit Test Repository: OpenSolaris developers will be able to submit unit tests as part of the integration process. These unit tests will be included in OpenSolaris test suites.
88: 
89:  Join the community to help define the test strategy and contribute tests for the OpenSolaris project and code base.
90: 
91: ==== Translations
92: 
93:  Visit the [[Internationalization and Localization Community Group>>Community Group int_localization.WebHome]] to find information about how to get involved in multiple areas.
94: 
95: ==== Other
96: 
97:  Efforts for and around the OpenSolaris project continue to grow outside of this website. Community efforts like [[blastwave.org>>http://blastwave.org]], [[cuddletech>>http://www.cuddletech.com]], [[genunix.org>>http://genunix.org]], [[sunfreeware.com>>http://www.sunfreeware.com]] are examples.
OpenSolaris

Top Menu

Wiki code for How to Participate

Search

Collectives

Community Group

Project

User Group

Subsites

Main Pages
