|
|
Line 32: |
Line 32: |
| =[[Image:Summit_Banners_2013_Education.jpg]] <br><span style="font-size:50%"></span>= | | =[[Image:Summit_Banners_2013_Education.jpg]] <br><span style="font-size:50%"></span>= |
| <noinclude>{{:Template:Summit_2011_Working_Sessions/Columns}} | | <noinclude>{{:Template:Summit_2011_Working_Sessions/Columns}} |
| + | {{:Projects_Summit_2013/Working_Sessions/008 | Projects_Summit_2013_Working_Sessions/Rows}} |
| + | {{:Projects_Summit_2013/Working_Sessions/009 | Projects_Summit_2013_Working_Sessions/Rows}} |
| | | |
| |}</noinclude> | | |}</noinclude> |
− |
| |
− | ...list of working sessions will go here ....
| |
| | | |
| | | |
Revision as of 05:50, 27 September 2013
Back to main Summit 2011 page
Introduction
The OWASP Project Summit is a smaller version of the much larger OWASP Summits. This event activity gives our project leaders the opportunity to showcase their project progress, and have attendees sit down and work on project tasks during the event. It is an excellent opportunity to engage the event attendees, and it gives project leaders the chance to move forward on their project milestones while meeting new potential volunteers that can assist with future milestones.
For more details see also the main Project Summit pages at the main OWASP AppSecUSA website: http://appsecusa.org/2013/activities/owasp-project-summit/
Working Sessions
Click on the working session name to see the home page for that particular session. During the Summit those working session home pages will be used to document discussions and outcomes.
If you're interested in adding a Working Session for the 2013 Summit, there still is time to start a session! Please review the Working Session methodology for Working Session rules.
NOTE: The current banners below are placeholders. Track topics are subject to change.
|
Name of Working Session
|
Objective(s)
|
Outcome(s) / Deliverable(s)
|
Owner/Leader
|
Members/Attendees
|
view edit
|
Project Workshop
|
- The objectives of this working session are to focus on finishing off the project assessment criteria which we will use to assess all of our OWASP Projects in our inventory.
- The second objective is to design and develop 3 wiki templates for our projects.
- The third objective is to consolidate all of the repositories used by all of our project leaders, and add them to Ohloh.
|
- Complete the final version of the Global Project Review Criteria.
- Complete the graduation process.
- Finish collecting all of our project repositories.
- Discuss and complete project wiki templates for our Tool, Documentation, and Code Library Projects.
|
Samantha Groves @
|
|
view edit
|
Project Reviews
|
- Introduction to new assessment criteria to conduct reviews.
- Team in small groups (2 to 3 max) based on experience and background to asses a set of Projects (Code, Tool or Documentation).
- Fill in the Questionnaire (Google Forms) to complete assessment of Projects and provide the review with a final score and results (Project defined as Incubator, Lab or Flagship).
- Review results of questionnaire with your team.
- Present results and conclusions of assessment session.
|
- Review of all the current Flagship, some Lab, and some Incubator projects. Find here.
- Assign them an appropriate stage designation based on the review.
- Update the inventory based on reviews.
- Create banners that show what stage each project is on. To be placed on the wiki.
|
Johanna Curiel @
|
|
|
Name of Working Session
|
Objective(s)
|
Outcome(s) / Deliverable(s)
|
Owner/Leader
|
Members/Attendees
|
view edit
|
ESAPI Hackathon
|
- Planning to sponsor 2 "senior developers" to attend the hack-a-thon and take the lead role on the development effort, they will be involved in the architecture aspect of the project and goal-building and attendees will be able to choose a component from the architecture to work on.
- We will purchase a prize for the developer/team that accomplishes the most quality work scored based on complexity of the component(s) they will be working on. The judges for the prizes will be Jeff Williams, Kevin Wall and Chris Schmidt.
- There will be a set of guidelines for entries – primarily, backwards compatibility and/or clear upgrade path from ESAPI 2.x, testability, and distribution model of the component.
|
- Identify the primary goals to deem the hack-a-thon a success.
- Layout the overall architecture vision for ESAPI 3.0.
- Lay down the infrastructure (Git, Continuous Integration, Testing Framework, etc.).
- Design the specification for the components that will be required.
- Close down all inactive ESAPI Projects.
|
Chris Schmidt @
|
Chris Schmidt @
Kevin Wall @
Jeff Williams @
|
view edit
|
ESAPI Hackathon: 2nd Session
|
- Teams will be 1-4 developers; scores will be curved based on the size of the teams submitting the components. For example, a team of 4 developers submitting a key management component will score lower than a single developer submitting a key management component dependent on the quality of the submitted component. (These scoring guidelines are still under consideration).
- Jeff Williams will be "kicking off" the hackathon by giving a short speech about ESAPI as the founding member of the project. I will also be giving a short speech on the future vision of ESAPI to set up the teams. The prize will be awarded at the closing of the conference.
|
- Identify the primary goals to deem the hack-a-thon a success.
- Layout the overall architecture vision for ESAPI 3.0.
- Lay down the infrastructure (Git, Continuous Integration, Testing Framework, etc.).
- Design the specification for the components that will be required.
- Close down all inactive ESAPI Projects.
|
Chris Schmidt @
|
Chris Schmidt @
Kevin Wall @
Jeff Williams @
|
|
Name of Working Session
|
Objective(s)
|
Outcome(s) / Deliverable(s)
|
Owner/Leader
|
Members/Attendees
|
view edit
|
OWASP Training Development Session
|
- OWASP Boot camp development.
- OWASP Training events brainstorming session and planning.
|
- Develop a roadmap for an OWASP Bootcamp Program.
- Develop a handfull of ideas for an OWASP Training Program.
|
Konstantinos Papapanagiotou @
|
Martin Knobloch @
Konstantinos Papapanagiotou @
|
view edit
|
OWASP Academies Development Session
|
- OWASP Academies discussion.
- OWASP University Outreach.
- OWASP Student Chapter.
|
- Develop a roadmap for OWASP Academies Program for 2014.
|
Martin Knobloch @
|
Konstantinos Papapanagiotou @
Martin Knobloch @
|
|
Name of Working Session
|
Objective(s)
|
Outcome(s) / Deliverable(s)
|
Owner/Leader
|
Members/Attendees
|
view edit
|
Project Guide Review Session
|
- Figure out what else needs to be done for each project.
- Assign sections to each participant.
- Finish various sections assigned to you.
- Consolidate all finished sections.
|
- Finished content for AppSensor Book.
- Finished content for Development Guide Book.
- Finished content for Code Review Guide Book. .
- Finished content for Testing Guide Book.
|
Michael Hidalgo @
|
|
view edit
|
Technical Editing Session
|
- Proof read AppSensor Guide, Dev Guide, Code Review Guide, and Testing Guide.
- Finish technical editing for all 4 guides.
|
- Finish proof-reading, and technical editing for AppSensor Book.
- Finish proof-reading and technical editing for Development Guide Book.
- Finish proof-reading and technical editing for Code Review Guide Book. .
- Finish proof-reading and technical editing for Testing Guide Book.
|
Michael Hidalgo @
|
|
|
Name of Working Session
|
Objective(s)
|
Outcome(s) / Deliverable(s)
|
Owner/Leader
|
Members/Attendees
|
...list of working sessions will go here ....
|
Name of Working Session
|
Objective(s)
|
Outcome(s) / Deliverable(s)
|
Owner/Leader
|
Members/Attendees
|
view edit
|
ZAP Hackathon Session
|
- Explain how people can contribute to ZAP
- Demonstrate how to set up a ZAP development environment
- Explain ZAP code structure
- Show people how to code scripts, active/passive scan rules, add-ons, core changes and improve the docs and localization
- Let people hack the ZAP code and docs with full support and guidance
|
- Identify set of enhancements attendees can work on
- Everyone with access to a ZAP dev environment
- An understanding of the ZAP code structure
- An understanding of how to develop ZAP code
- A set of small enhancements that can be committed immediately
|
Simon Bennetts @
|
Johanna Curiel
|
Summit Organisation Pages
These are pages with organization details about this event
Reference Links: