Wiki code for Contest FAQ

Hide Line numbers
1: == Community Innovation Awards FAQ ==
2: 
3: >[[Prizes>>#What_are_the_Prizes_]]  
4: >[[Registration>>#Contest_Registration]]  
5: >[[Sun Contributor Agreement>>#Sun_Contributor_Agreement]]  
6: >[[Eligibility>>#Who_can_enter_this_contest_]]  
7: >[[Entries>>#What_kind_of_work_can_I_enter_]]  
8: >[[Submission>>#Contest_Submissions]]  
9: >[[Judging Criteria and Scoring>>#Contest_Judging_Criteria_and_Scoring]]
10: 
11: >Still have a question? Send email to **contest** dash **submit** at **sun** dot **com** or to **awards** dash **program** at **opensolaris** dot **org**.
12: 
13: ===What are the OpenSolaris Community Innovation Awards?===
14: 
15: The OpenSolaris Community Innovation Awards are intended to recognize and reward new, enabling, innovative, and high-performance uses of OpenSolaris technology, or substantial contributions to the OpenSolaris community. This program is part of a broader [[Community Innovation Awards Program>>http://www.sun.com/software/opensource/awards/index.jsp]] whose goals are to "foster innovation and recognize the most interesting initiatives within open source communities worldwide."  Sun is the primary sponsor of this program and intends to contribute over $1 million across six open source communities.
16: 
17: We hope these awards will encourage more people to participate in the OpenSolaris community. Join a [[community>>Main.communities]], a [[project>>Main.projects]], a [[forum>>Main.discussions]] or other [[discussion>>http://mail.opensolaris.org/mailman/listinfo]]. [[Use>>Main.downloads]] OpenSolaris. [[Study>>Community Group edu.curriculum_development]] OpenSolaris.
18: 
19: To that end:
20: * A large chunk of the award money is designated for grants for [[undergraduate research on OpenSolaris>>Project awards.awards_research_land]].
21: * The contest portion of the award money is open to a broad range of entries. You can enter code that will eventually be putback into OpenSolaris (such as a device driver), or you can write a program that runs on top of the OS (such as a tool or game), or your entry can be something that is not code at all. You could enter materials for an operating systems course based on OpenSolaris (lecture notes, student guide, labs). [[Contest Entries>>Project awards.Entries]] lists the entries that users have already registered for this contest.
22: 
23: ====What are the Prizes?====
24: 
25: Entries will be reviewed by a panel of judges. See [[Judging Criteria and Scoring>>#Contest_Judging_Criteria_and_Scoring]] below. In the contest portion of the OpenSolaris awards program, 29 prizes are available:
26: 
27: * One Grand Prize: $30,000
28: * Three First Prizes: $15,000 each
29: * Two Second Prizes: $6,000 each
30: * Third Prizes: $1,000 each
31: 
32: All prizes are in U.S. dollars.
33: 
34: ====Distribution of Prizes to Winners====
35: 
36: Prizes will be awarded in August of 2008. Prize winners will need to sign an affidavit conferring certain rights to Sun Microsystems for the purposes of advertising, etc.
37: 
38: ===Contest Registration===
39: 
40: ====How do I register for this contest?====
41: 
42: To register for the contest, go to the [[registration and submission site>>http://awards.opensolaris.org]] and follow the directions given in Step 1, "Register for the Contest." You will be sent a password that you can then use to sign in to the site. You can sign in at any time and modify your registration.
43: 
44: To register for the contest, you must already be a [[registered user of the OpenSolaris site>>http://www.opensolaris.org/register.jspa]].
45: 
46: If you have any problems with the registration process, send email to **contest** dash **submit** at **sun** dot **com**.
47: 
48: If you registered but did not receive your password:
49: 
50: * Make sure you entered your email address correctly when you registered. Your password will be sent to that email address.
51: * Make sure your spam-blocking tool allows you to receive email from **contest** dash **submit** at **sun** dot **com**.
52: 
53: ====Sun Contributor Agreement====
54: 
55: You must sign and return [[the Sun Contributor Agreement (SCA)>>Main.sun_contributor_agreement]] before you submit your contest entry.
56: 
57: **Note:** Allow 3 days to receive your SCA number after you submit your signed SCA.
58: 
59: ====Registration Information====
60: 
61: Information you will be asked to provide includes your name, your OpenSolaris community user name, your email address, and your SCA number.
62: 
63: Next, complete Step 2, "Add New Contest Entry" or sign in and click the "Add Contest Entry" link in the left hand navigation pane. In this step, information you will be asked to provide includes the type of entry you will be submitting (a kernel module, an application, university curriculum, other documentation, etc.), title of the entry, and a brief description of the entry. You also will be required to read and accept the official rules of the contest.
64: 
65: Informing others of what you are doing gives other entrants a chance to change their plans if they were considering doing the same thing. Similarly, you might like to know if someone else is planning to create an entry like yours. You might want to check the [[list of contest entries that are already registered>>Project awards.Entries]] before you register yours.
66: 
67: **Note:** You must complete both Step 1 and Step 2 before you can submit your entry.
68: 
69: ====DATE:====
70: 
71: Registration is open through June 13, 2008.
72: 
73: ====Who can enter this contest?====
74: 
75: This contest is open to all persons who are not an employee, contractor, including their immediate families, of Sun Microsystems Inc or its subsidiaries.
76: 
77: Sun Campus Ambassadors are eligible to participate with the following additional restrictions:
78: * Ambassador’s participation must be voluntary, and without direction, encouragement, or other involvement from Sun Microsystems, Inc.
79: * Ambassadors must not be paid by Sun Microsystems Inc. for any work conducted in conjunction with the Program.
80: * Ambassadors may not submit any work that they have conducted for Sun Microsystems, Inc. as part of a Proposal or Project.
81: * Ambassadors must work on Proposals and Projects outside of scheduled Sun Microsystems Inc. work hours.
82: * Ambassadors may not use any Sun Microsystems Inc. resources to work on a Proposal or Project.
83: 
84: Please refer to the [[Contest Rules>>Project awards.awards_rules]] for a list of countries which can not participate in this program.
85: 
86: If you have not yet participated in OpenSolaris, join a [[community>>Main.communities]], a [[project>>Main.projects]], a [[forum>>Main.discussions]] or other [[discussion>>http://mail.opensolaris.org/mailman/listinfo]]. [[Use>>Main.downloads]] OpenSolaris. [[Study>>Community Group edu.curriculum_development]] OpenSolaris.
87: 
88: ====Can a team register for this contest?====
89: 
90: You can form a team or collaborate with others. Each member of the team must sign a separate copy of the [[Sun Contributor Agreement>>Main.sun_contributor_agreement]] and the ’Affadavit’. 
91: 
92: Teams must declare the names of their team members and the percentages of how potential prizes will be divided; all team members must sign this document and provide it at the time the entry is submitted.  A digitally scanned image attached as a PDF file is an acceptable form for this document.
93: 
94: ====What kind of work can I enter?====
95: 
96: The OpenSolaris contest is open to a broad range of entries. You can enter code that will eventually be putback into OpenSolaris (such as a device driver), or you can write a program that runs on top of the OS (such as a tool or game), or your entry can be something that is not code at all. You could enter materials for an operating systems course based on OpenSolaris (lecture notes, student guide, labs). [[Contest Entries>>Project awards.Entries]] lists the entries that users have already registered for this contest.
97: 
98: All software components must execute on an OpenSolaris-based operating environment and must be released as open source.
99: 
100: Work on an entry could have started before the contest launched, but the work must be completed or improved after the contest launch.
101: 
102: ====Can I submit work that I did as part of an OpenSolaris community or project?====
103: 
104: Yes, but make sure you submit only the part of that work that is your original work, created solely by you.
105: 
106: ====Can I submit more than one contest entry?====
107: 
108: Yes. For additional entries, just sign in again and click Step 2, "Add New Contest Entry" or click the "Add Contest Entry" link in the left hand navigation pane.
109: 
110: ===Contest Submissions===
111: 
112: ====Sun Contributor Agreement====
113: 
114: You must sign and return [[the Sun Contributor Agreement (SCA)>>Main.sun_contributor_agreement]] before you submit your contest entry. 
115: 
116: **Note:** Allow 3 days to receive your SCA number after you submit your signed SCA.
117: 
118: ====How do I submit my contest entry?====
119: 
120: To submit your contest entry, go to the [[registration and submission site>>http://awards.opensolaris.org]] and follow the instructions in Step 3, "Upload Your Awards Entry Submission(s)." Your contest entry must meet the requirements described below. You must have already [[registered>>#Contest_Registration]] for the contest. If you have any problems with the submission process, send email to **contest** dash **submit** at **sun** dot **com**.
121: 
122: **Note:** You must complete both Step 1 (Register for the Contest) and Step 2 (Declare Your Contest Entry) before you can start Step 3 (Upload Your Awards Entry Submission).
123: 
124: Submit your contest entry in a single compressed archive (for example, .zip or .tar.gz). The archive must include at least the following information:
125: * An image file of a signed scanned [[Sun Contributor Agreement>>Main.sun_contributor_agreement]] signed by you. For team entries, each team member must sign and submit a separate agreement. 
126: * For team entries, an image file of a signed scanned document listing all team members and the percentage of the potential prize each may be awarded signed by all team members.
127: * A README file that contains at least the following information:
128: * * Your name and email address. For team entries, include the name and email address of each team member.
129: * * The original copyright owner’s name(s) and the copyright date(s). Please see the [[clarification below>>#Copyright_Clarification]].
130: * * Description: What problem does this entry solve? What need does this entry fill? How does this entry work? How does someone use this entry? Show that the entry does what the problem statement says it does.
131: * * What OpenSolaris distribution does this work with? What version? What hardware platform? 
132: * * All instructions needed to assemble the contents of the archive into a usable form (such as build instructions).
133: * A usable form of your submission such as an executable binary, package, video, or PDF.
134: * All source materials required to recreate the usable form and build environment such as Makefiles, source code, XML, LaTeX.
135: * If there is any specific hardware that is required to demonstrate the entry, it must be shipped to and from the judges at the entrant’s expense.
136: 
137: If a difference is found between the source and the usable form, that entry will be disqualified.
138: 
139: ====Copyright Clarification====
140: 
141: A couple of entrants have asked what we mean by, "original copyright owner’s name(s) and the copyright date(s)." We cannot give specific advice, but here is a clarification:
142: 
143: The source files you submit should include attribution statements.
144: 
145: Any files that are not original to you should include the copyright notice and any license or license header found in the source files from which you derived your module.
146: 
147: There are various online resources on the subject of copyright notice, or you can consider following the copyright format used by one of the open source license templates. For example, the BSD template uses the following format where "copyright holder" would be your name:
148: 
149: Copyright (c) <year>, <copyright holder>.
150: 
151: ====DATE:====
152: 
153: The final submission date is June 14, 2008.
154: 
155: =====Note:=====
156: 
157: Submitting for the contest is separate from contributing to the OpenSolaris code base.
158: 
159: Your contest entry is not automatically a contribution to the OpenSolaris code base. If you want to contribute your contest entry to the OpenSolaris code base, you must do that separately. First submit your entry to the contest as described above. Then follow the process described below to contribute your entry to the OpenSolaris code base. You do not need to wait until contest judging is complete.
160: ~----
161: 
162: ====How do I contribute to the OpenSolaris code base?====
163: 
164: 1. If you have not already signed the SCA and received a Sun contributor number, first, sign and return the SCA ([[Sun Contributor Agreement>>Main.sun_contributor_agreement]]). Be sure you read and understand it. The SCA is the same for all Sun-sponsored open source projects. You will receive a Sun contributor number.
165: 1. Search the OpenSolaris [[bug database>>http://bugs.opensolaris.org]] to determine whether your contest entry fixes an existing defect or satisfies an existing enhancement request.
166: * * If you find a CR (change request) that is related to your contest entry, note the state of the CR. Is an engineer already assigned to the CR? Does the status indicate that a fix is already available? Check the [[request sponsor table>>Main.request_sponsor]] to determine whether someone else has already started to work on this CR.
167: * * If you do not find any CR that is related to your contest entry, click [[Report a bug or request a feature>>http://bugs.opensolaris.org]] to submit a new enhancement request (RFE) that your contest entry will satisfy. Be sure to select the field that indicates you want to work on this CR.
168: 1. If the CR is ’’not’’ already listed in the [[request sponsor table>>Main.request_sponsor]], send email to request-sponsor AT opensolaris DOT org, stating that you want to work on this CR and asking for a sponsor for this work. Tell them you already have a solution completed. Include the following information in your email:
169: * * CR ID number
170: * * CR category, subcategory, and synopsis/summary
171: * * Your full name
172: * * Your Sun contributor number that you received after you signed the SCA
173: 
174: Your code contribution will be required to be tested (see the [[OpenSolaris testing community>>Community Group testing.WebHome]] and will be required to undergo code review. Your code contribution probably also will undergo design and architectural review. For more information, see [[Improving the OpenSolaris project>>Main.participate]].
175: ~----
176: ===Contest Judging Criteria and Scoring===
177: 
178: Code entries will be judged on the following criteria:
179: * Usefulness to the end users and/or the community (33%)
180: * * competitive need relative to other operating systems
181: * * attractiveness to users
182: * * usability of implementation
183: * * documentation
184: * * timeliness to market
185: * Technical difficulty of implementation (33%)
186: * * depth of knowledge required for implementation
187: * * quantity of code, functions, and features
188: * * quality and cleanliness of code
189: * Innovation (34%)
190: * * impact on market 
191: * * originality of implementation
192: * * market potential for adoption
193: 
194: Non-code entries will be judged on the following criteria:
195: * Usefulness to the end users and/or the community (33%)
196: * * public appeal
197: * * usefulness to the community
198: * Quality (33%)
199: * * quality of work (syntax, diction, grammar, editing, visual artwork)
200: * * style (of writing or artwork)
201: * * publication readiness
202: * * layout, direction, animation
203: * * professionalism
204: * Innovation (34%)
205: * * originality of work
206: * * interpretation of objective or theme
207: * * market potential and impact
208: 
209: Each entry will receive a score from 0 to 10 on each of the criteria. Those scores will be multiplied by their weighting factors and then summed to get the final score.
210: 
211: For example, if a software entry received the following scores:
212: 
213:      usefulness: 9
214:      technical difficulty: 8
215:      innovation: 5
216: 
217: then the final score for that entry would be:
218: 
219:      9x0.33 + 8x0.33 + 5x0.34 = 7.31
220: 
221: out of a possible 10 points.
222: 
223: If necessary, the innovation score will be used as the tie breaker.
224: ~----
OpenSolaris

Top Menu

Wiki code for Contest FAQ

Search

Collectives

Community Group

Project

User Group

Subsites

Project awards Pages
