OWASP Season of Code 2009 - Revision history

Paulo Coimbra at 14:21, 17 June 2009

2009-06-17T14:21:04Z

Paulo Coimbra: /* OPERATIONAL RULES */

2009-06-15T22:29:50Z

‎OPERATIONAL RULES

Paulo Coimbra: /* OPERATIONAL RULES */

2009-06-15T22:29:30Z

‎OPERATIONAL RULES

Jason Li: Fixing bullets

2009-06-08T03:26:19Z

Fixing bullets

Jason Li: Added new strategic shift

2009-06-08T03:24:30Z

Added new strategic shift

Paulo Coimbra: /* UPDATES */

2009-06-01T22:10:43Z

‎UPDATES

Paulo Coimbra: /* SCHEDULE */

2009-06-01T22:10:21Z

‎SCHEDULE

Paulo Coimbra: /* UPDATES */

2009-05-26T15:25:46Z

‎UPDATES

Paulo Coimbra: /* UPDATES */

2009-05-26T15:25:14Z

‎UPDATES

Paulo Coimbra: /* SCHEDULE */ Second deferment.

2009-05-26T15:15:58Z

‎SCHEDULE: Second deferment.

@@ Line 24: / Line 24: @@
 <br>
 * '''Main Links'''
 * [[OWASP Season of Code 2009 - Press Release|Press Release ]]
 * [[OWASP Season of Code 2009 - Applications|View Submitted Applications]]

@@ Line 113: / Line 113: @@
 == OPERATIONAL RULES ==
 * Proposals are submitted using online form (with all details publicly posted).
-* The participant should propose one reviewer (for details on the proposed reviewer responsibilities, see TDB see {assessment criteria reviewer role link})
+* The participant should propose one reviewer (for details on the proposed reviewer responsibilities, see TDB see {assessment criteria reviewer role link}).
 * Each and every project release should have its SoC Project Release page always completely updated with all information regarding the project release status.
 * The SoC Project Release's final deliveries will be evaluated by the assigned reviewers. However, the Jury will provide final oversight.

@@ Line 112: / Line 112: @@
 == OPERATIONAL RULES ==
-* Proposals are submitted using online form (with all details publicly posted)
+* Proposals are submitted using online form (with all details publicly posted).
 * The participant should propose one reviewer (for details on the proposed reviewer responsibilities, see TDB see {assessment criteria reviewer role link})
 * Each and every project release should have its SoC Project Release page always completely updated with all information regarding the project release status.

@@ Line 49: / Line 49: @@
 Although we welcome any project proposals (from improving Quality of [[:Category:OWASP Project|existing OWASP projects]] to new innovative research), the areas below will be preferred:
-** '''1. OWASP Education Pack''' - ([[:Global Education Committee|Education Committee]])
+# '''OWASP Education Pack''' - ([[:Global Education Committee|Education Committee]])
-** '''2. Enterprise usability of OWASP projects''' - ([[:Category:Global Projects Committee|Projects Committee]])
+# '''Enterprise usability of OWASP projects''' - ([[:Category:Global Projects Committee|Projects Committee]])
-** '''3. Additional Sources of Funding''' - ([[:Global Membership Committee|Membership]] & [[Global Chapter Committee|Chapters Committee]])
+# '''Additional Sources of Funding''' - ([[:Global Membership Committee|Membership]] & [[Global Chapter Committee|Chapters Committee]])
-** '''4. Marketing & PR''' - ([[:Global Industry Committee|Industry]] & [[:Global Conferences Committee|Conferences Committee]])
+# '''Marketing & PR''' - ([[:Global Industry Committee|Industry]] & [[:Global Conferences Committee|Conferences Committee]])
 In particular, any projects that wishes to participate in the current SoC with the goal of improving their project quality is welcome to submit an application. Several project leaders have already indicated that they would like to do this even without SoC grant funds. For proposals that do not request SoC grant funds, we will do our best to offer alternative rewards in the form of project promotion (recognition, featured placement on the OWASP website, speaking slots to highlight projects at OWASP conferences, etc).
@@ Line 132: / Line 132: @@
 == FAQ ==
-# Why are you changing the way SoC Grants work?
+=== Why are you changing the way SoC Grants work? ===
-# But I like getting paid for my work for OWASP!
+===  But I like getting paid for my work for OWASP! ===
-# What if I don't want
 [[Category:OWASP Season of Code]]

@@ Line 41: / Line 41: @@
 == OVERVIEW ==
-*OWASP is now launching its Season of Code 2009 (OWASP SoC 09) with a provisional budget US$90,000, following the previous [[:OWASP Summer of Code 2008|OWASP Summer of Code 2008]], in which 33 projects were approved and a budget of more than US$125,000 have been made available, the [[OWASP Spring Of Code 2007|OWASP Spring of Code 2007]] (SpoC 07), in which 21 projects were sponsored with a budget of US$117,500, and the [[OWASP Autumn Of Code 2006|OWASP Autumn of Code 2006]] (AoC 06), in which 9 projects were sponsored with a budget  of US$20,000.
+OWASP is now launching its Season of Code 2009 (OWASP SoC 09) with a provisional budget US$90,000, following the previous [[:OWASP Summer of Code 2008|OWASP Summer of Code 2008]], in which 33 projects were approved and a budget of more than US$125,000 have been made available, the [[OWASP Spring Of Code 2007|OWASP Spring of Code 2007]] (SpoC 07), in which 21 projects were sponsored with a budget of US$117,500, and the [[OWASP Autumn Of Code 2006|OWASP Autumn of Code 2006]] (AoC 06), in which 9 projects were sponsored with a budget  of US$20,000. The OWASP SoC 2009 is an OWASP grant program to encourage participants/developers to work together on OWASP (and web security) related projects.
-*The OWASP SoC 2009 is an open sponsorship program were participants/developers are paid to work on OWASP (and web security) related projects. Although we welcome any project proposals (from improving Quality of [[:Category:OWASP Project|existing OWASP projects]] to new innovative research), the areas below will be preferred:
+=== Strategic Focus ===
 ** '''1. OWASP Education Pack''' - ([[:Global Education Committee|Education Committee]])
 ** '''2. Enterprise usability of OWASP projects''' - ([[:Category:Global Projects Committee|Projects Committee]])
 ** '''3. Additional Sources of Funding''' - ([[:Global Membership Committee|Membership]] & [[Global Chapter Committee|Chapters Committee]])
 ** '''4. Marketing & PR''' - ([[:Global Industry Committee|Industry]] & [[:Global Conferences Committee|Conferences Committee]])
-−
 * On the allocated projects areas the respective committee, above pointed out, will be involved on the application selection and will act as the 2nd reviewer accordingly with the [[:Assessment Criteria v2.0|OWASP Assessment Criteria V2]].
 *The OWASP SoC 2009 is also an opportunity for external individual or company sponsors to challenge the participants/developers to work in areas in which they are willing to invest additional funding - see [[OWASP Season of Code Sponsorship]] for further information.
@@ Line 90: / Line 96: @@
 == SELECTION CRITERIA ==
 * The participant must create a roadmap for the project release that includes technical requirements, functional requirements, and quality requirements. Preference will be given to proposals that use the existing [[:Assessment_Criteria_v2.0|OWASP Beta and Stable requirements]] for quality supplemented with their own technical and functional requirements.
 * There are two methods to select OWASP SoC 09 project releases:
 ** By direct majority vote by the Jury;
@@ Line 109: / Line 116: @@
 * Each and every project release should have its SoC Project Release page always completely updated with all information regarding the project release status.
 * The SoC Project Release's final deliveries will be evaluated by the assigned reviewers. However, the Jury will provide final oversight.
-* Payments will be made, via Pay Pal, in two instalments, respectively 50% halfway and 50% on completion of the project release. (basically, if you do not deliver you will NOT be paid)
+* Invoicing of expenses can be done directly through Alison, our OWASP accountant. Grants amounts will be approved by the SoC Jury. Participants are expected to stay reasonably close to their line item budgets; significant deviations or re-allocations from individual line items will be approved by the respective Global Committee managing the project so long as the deviation does not result in the costs exceeding the original grant amount. Any costs above and beyond the original grant amount must be approved by the SoC Jury.
 == GENERAL RULES ==
@@ Line 123: / Line 130: @@
 * Note: The referred budget allocation is just a guideline and the final values will be adjusted based on the successful proposals.
 [[Category:OWASP Season of Code]]

@@ Line 38: / Line 38: @@
 *'''MAY 6:''' DRUM ROLL!!!!!!!!!!!!!!!!!!!! '''THE OWASP SEASON OF CODE 2009 HAS BEEN PRE LAUNCHED AT [[OWASP AppSec Europe 2009 - Poland|OWASP APPSEC EUROPE 2009 - POLAND]]!'''
-** '''Deadline for project release applications: 29th June.'''
+** '''Deadline for project release applications: TBD'''
 == OVERVIEW ==

@@ Line 79: / Line 79: @@
 == SCHEDULE ==
 * 13th May – OWASP SoC 09 is pre launched at [[OWASP AppSec Europe 2009 - Poland|OWASP AppSec Europe 2009 - Poland]]!'''
-* 3rd June - OWASP SoC 09 is officially launched. Start date for submitting applications.
+* TBD - OWASP SoC 09 is officially launched. Start date for submitting applications.
-* 29th June - Deadline for project release applications.
+* TBD - Deadline for project release applications.
-* 14th July – Publishing of selected applications and start of OWASP SoC 09 project releases.
+* TBD – Publishing of selected applications and start of OWASP SoC 09 project releases.
-* 14th October - Participants to report on project status - 50% mark.
+* TBD - Participants to report on project status - 50% mark.
-* 14th January - Project completion. Participants should deliver final project release report.
+* TBD - Project completion. Participants should deliver final project release report.
 == JURY ==

@@ Line 37: / Line 37: @@
 == UPDATES ==
-*'''MAY 6:''' DRUM ROLL!!!!!!!!!!!!!!!!!!!! '''THE OWASP SEASON OF CODE 2009 WILL BE PRE LAUNCHED AT [[OWASP AppSec Europe 2009 - Poland|OWASP APPSEC EUROPE 2009 - POLAND]]!'''
+*'''MAY 6:''' DRUM ROLL!!!!!!!!!!!!!!!!!!!! '''THE OWASP SEASON OF CODE 2009 HAS BEEN PRE LAUNCHED AT [[OWASP AppSec Europe 2009 - Poland|OWASP APPSEC EUROPE 2009 - POLAND]]!'''
 ** '''Deadline for project release applications: 29th June.'''