Difference between revisions of "OWASP Summer of Code 2008"

From OWASP
Jump to: navigation, search
(Updates)
(Updates)
Line 3: Line 3:
 
* '''July 2'''
 
* '''July 2'''
 
*[[OWASP EU Summit 2008 - updates|OWASP EU Summit 2008 - update]].
 
*[[OWASP EU Summit 2008 - updates|OWASP EU Summit 2008 - update]].
 
+
<br>
 
+
 
* '''June 26'''
 
* '''June 26'''
 
*As you know, we have almost reached the time to perform the 50% review.
 
*As you know, we have almost reached the time to perform the 50% review.

Revision as of 05:50, 2 July 2008

Contents

Updates


  • June 26
  • As you know, we have almost reached the time to perform the 50% review.
  • However, it’s time to recognize that we have been somewhat imprecise in our definition of the 50% review‘s deadline. To have all projects reviewed, we should have defined a period, a start and an end date, instead of a specific day. Therefore, regarding this matter, we will not be strict.
  • On the contrary, please be aware that we expect the final deliveries ready by, maximum, 15th September, as we are planning to set up an International Conference to publicly present them.
  • However, we are still recommending June 29 to be assumed as the reference date to begin this process.
  • In accordance, we would like to see each project template being updated until the referred date (June 29) by uploading in there all project main links and documentation as can be seen, for example, here or here. Thereafter, both author’s project and reviewers should begin the assessment task. – As we are still receiving questions inquiring about the assessment/review methodology, I am sending again a couple of guidance lines (see please the page bottom).
  • Regarding the provisory pointed out reviewers, as not everybody have yet done what was asked in the previous SoC’s update, I must reiterate the following requests:
    • Please add the note ‘Confirmed’ or ‘Unconfirmed’ directly on this page, just below the reviewers names. Please, pay special attention if you find the reference TBC (To be confirmed).
    • Please, ask your reviewers for them to add, as soon as possible, just below their names, a link with a couple of lines mentioning their professional background - as you know this information will be needed to achieve OWASP Board’s confirmation.
  • Please, send me off your postal address and Pay Pal reference. Once the 50% review is finished, we will need it to pay.
  • To conclude, regarding the projects that haven’t yet found the required reviewers, I take the opportunity to ask the authors to drop me a line if assistance is needed.
  • I wish you all good work.

Many thanks, best regards

Paulo Coimbra,

Logo&Main Links

Logo Main Links
SoC 08 Logo.jpg

Overview

  • OWASP is now launching the Summer of Code 2008 (SoC 2008), following the previous 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 (AoC 06), in which 9 projects were sponsored with a budget of US$20,000.
  • The SoC 2008 is an open sponsorship program were participants/developers are paid to work on OWASP (and web security) related projects.
  • The SoC 2008 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.
  • The Open Web Application Security Project (OWASP) is a worldwide free and open community focused on improving the security of application software. Our mission is to make application security "visible," so that people and organizations can make informed decisions about application security risks.

Who Can Apply?

  • The only requirement is that the candidate shows the potential to accomplish the project's objectives/deliveries and the commitment to dedicate the time required to complete it in the appropriate period.
  • Current active OWASP Project Contributors (including Project leaders) are encouraged to apply.
  • No member of the OWASP board is allowed to apply for a SoC 2008 sponsorship.
  • There are no any other restrictions on who can apply for a SoC 2008 sponsorship.

How To Participate (To Developers)

  • Ideas to work can be chosen from:
  • To submit a project you have to post it on the OWASP Summer of Code 2008 Applications Page.
    • Please see AoC 06 and SpoC 07 for contents to be included in the Application
    • Note that no sensitive personal details should be posted in that page, i.e., full name, postal address, email, and so on.
  • Once your application is published on the WIKI, send an email to Paulo Coimbra with the following details:
    • Project name;
    • Contact details, i.e., full name, postal address and email.
  • Both Paulo Coimbra and Dinis Cruz can also be contacted for further discussion on issues related to SoC 2008 applications, i.e., project ideas, review of draft applications, etc..

Schedule

  • 3rd March – SoC 2008 season of code is officially launched. Start date for submitting applications.
  • 25th March - Deadline for project applications.
  • 16th April – Publishing of selected applications and start of SoC 2008 projects.
  • 29th June - Participants to report on project status.
  • 15th September - Project completion. Participants should deliver final project report.

Jury and Selection Criteria

  • Jury: OWASP Board Members (Jeff Williams, Dave Wichers, Tom Brennan, Sebastien Deleersnyder and Dinis Cruz).
  • There are two methods to select SoC 2008 projects:
    • By direct majority vote (3 out of 5) by the Jury;
    • By selection rating using the criteria defined below.
      • Each project will receive a rating from 1 to 5 on the following categories by each Jury. The final result will be the total value.
        • On the Project:
          • Complete status - What will be the final Completeness State?
          • Complexity - What is the project Complexity and Size?
          • Member Value - How big is the potential added value to Owasp Members?
          • Brand Value - How big is the potential added value to the Owasp Brand?
        • On the Candidate:
          • Past Work - Value of past contributions to OWASP Projects;
          • Deliverability - Proven capability to deliver;
          • Qualitty of Proposal - Global quality of the proposal submited.

Operational Rules

  • Whenever possible the participant should suggest a SoC 2008 Project Reviewer, which will be responsible for reviewing the project’s deliverables and authorize payments.
  • All and each Project Reviewer suggested by participants has to be confirmed by majority vote of the OWASP Board.
  • Whenever the participants fail to suggest a SoC 2008 Project Reviewer, the OWASP Board, by majority vote, will appoint one. The same will happen whenever the reviewer suggested by the participant does not have the required approval.
  • Each and every project should have its Project Progress page always completely updated with all information regarding the project status.
  • The Project Reviewer will provide his assessment twice for each project, respectively with 50% and 100% claimed completion. The Project Reviewer will deliver his evaluation filling in his Project Reviewer Page.
  • Each new project should obtain Reviewers’ agreement that, at least, a Beta Quality stage was achieved.
  • Each project built on previous work done within OWASP (Existing OWASP Projects) should obtain Reviewers’ agreement that a Release Quality stage was achieved.
  • Projects Final Deliveries will be evaluated by an assigned SoC 2008 Reviewer. 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.
  • Basically, if you do not deliver you will NOT be paid.

General Rules

  • By taking part on SoC 2008, the participant will authorize OWASP to host and advertise without any limitations his participation and all related contents including proposal and all deliveries.
  • All tools, documentation, or any other materials whatsoever, created by the participants within SoC 2008 context must be released under an Open Source Initiative approved license. However, the participant may mirror development on her/his personal infrastructure at her/his option.
  • Participants and OWASP is free to use the results, including code, of the SoC's 2008 code in any way they choose provided it is not in conflict with the license under which the code was developed.
  • OWASP reserves the right, at its sole discretion, to revoke any, and all, privileges associated with participating in this program, and to take any other action it deems appropriate, for no reason or any reason whatsoever. OWASP reserves the right to cancel, terminate or modify the program if it is not capable of completion as planned for any reason.
  • Any situation arising not included in the above mentioned set of rules will be decided according to the discretionary judgement of OWASP Board.

SoC 2008 Budget

  • The initial Budget for SoC 2008 will be US$100,000, and it is funded by OWASP.
  • In parallel with the Request for Proposals, OWASP is also doing a membership drive where all membership fees committed during that period will be allocated to SoC 2008 projects (the new members have the option to choose which projects they would like to sponsor).
  • The funds available will be allocated to select projects. However, strong proposals will be accepted by majority vote of the OWASP Board before the final project selection. Remaining budget will be allocated to remaining projects.
  • Note: The referred budget allocation is just a guideline and the final values will be adjusted based on the successful proposals.