Difference between revisions of "OWASP Summer of Code 2008"

Revision as of 14:45, 7 September 2008

1 Updates 2 Overview 3 Who Can Apply? 4 How To Participate (To Developers) 5 Schedule 6 Jury and Selection Criteria 7 Operational Rules 8 General Rules 9 SoC 2008 Budget		Main Links Press Release OWASP Summer of Code 2008 Blog Applications Jury's evaluation/selection of applications Approved projects, authors, status target and reviewers Half term payments OWASP EU Summit Portugal 2008

Updates

• Clik here to see OWASP Summer of Code's 2008 Previous Updates

• SEPTEMBER 7, 2008

Hello everyone,

I hope you are well.

Time flies, and as you know, we are almost reaching September 15, the initially established OWASP Summer of Code 2008 (SoC’s) deadline.

Therefore, less than ten days to the season of code’s expiring date, we thank those of you that are keeping the schedule and we challenge the remainder to make an effort to make up for this delay.

However, as we are working to have as many of you as possible attending the OWASP EU Summit Portugal 2008, we have decided to postpone the above-referred deadline to the possible maximum – the new SoC’s deadline will be the first day of the Summit, that is to say November 4.

We are still shaping the event wiki page but it was already agreed to hold a four-day OWASP gathering to discuss OWASP strategic issues and present all OWASP relevant projects. This first OWASP Summit will take place in Algarve (Faro is the nearest airport), Portugal, in the well-equipped seaside Hotel Santa Eulália, between the 4th and the 7th of November 2008.

In the first two days, the event will have the format of Working Sessions to openly discuss and decide on several OWASP projects and issues, e.g., OWASP Strategic Planning, OWASP Top 10 2009, Winter Of Code 2009, EASPI Project, Code Review Version 2, Testing Guide Version 4, OWASP Application Security Desk Reference (ASDR), OWASP Certifications, OWASP Awards and OWASP Website. Of course, we count on you to join the discussion and contribute to the final decisions.

As announced before, the remaining period of two days will consist of a two-day conference, where more than 40 OWASP specific presentations will be held. Again, we most definitely count on you to present your project.

Regarding the rules to qualify to have the Summit attendance expenses partially paid, we are also setting up the following:

1. Until September 15, at least the 50% completion point must have been reached, the 50% self-evaluation must have been performed and, at least, one of the two reviews must have been done.
2. Until September 15, both project leaders and reviewers must sign their intention of attending the Summit by adding their names here.
3. Until November 4, the project must be entirely complete, reviewed and ready to be publicly presented at the Summit.
4. Exceptions to these rules can be considered by OWASP Board under formal request made until September 15 by project leaders whose projects are specially extensive and complex.

In what respects to the level of expenses that will be paid, the following rules have been established:

1. With the exceptions below, all accommodation and meal expenses, during all the four days, will be paid.
2. As we are still seeking out for financial sponsorship support, until further notice, none of the dinners will be paid.
3. The meals consist of a pre-negotiated menu and just this will be paid.
4. The accommodation will consist in a place in a shared T 1 (3 people) or T2 (5 people) apartment. Therefore, even though one can choose an individual room, OWASP will pay only for the cost associated with a shared stay.
5. Please note that the nights of 3 and 7 of Nov will be included in the paid accommodation for those of you attending the whole event.
6. Regarding the flight expenses, OWASP will pay a maximum of 900 US dollars to all non-European attendees and 500 to the European ones.
7. The operational model to book accommodations and flights is not finished yet but, as soon as possible, more details will be given.

On the whole, if you accept our challenge to be at the OWASP EU Summit 2008 to present your project and engage the discussion at one, or more, Working Sessions and if you qualify to have your expenses partially paid, please add your name right here. Please do not forget to add the name of your city/airport of departure.

Nevertheless, although we start with a good budget to cover expenses (150,000 USD), it will not be enough to cover the current projected number of OWASP participants. Therefore, if you can convince your company to pay for some or all of your expenses please do so and, on the other flip of the coin, we can advertise its logo at the conference materials - more details about sponsorship opportunities will be sent later on.

To conclude, I will be here if you need further assistance, however, as I am releasing all the information and details already stabilized, the best way to keep yourself up to date and informed about the event is to visit regularly its wiki page.

Keep up the good work - I am looking forward to seeing you in Portugal!

Many thanks, best regards,

Paulo Coimbra, OWASP Foundation Project Manager

• Clik here to see OWASP Summer of Code's 2008 Previous Updates

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:
  • Participants/developers’ own interest and choice, as long as the OWASP main objectives are considered;
  • Projects prioritized by the OWASP Board to be done with SoC 2008 funds;
  • Existing OWASP Projects;
  • Projects directly linked to external individual or company sponsorship.
• 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.