This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP Project Summit 2014"
(→Working Sessions) |
(→Working Sessions) |
||
| Line 128: | Line 128: | ||
| style="background: #F5F5F5" align="center"| Gary Robinson | | style="background: #F5F5F5" align="center"| Gary Robinson | ||
| + | |style="background: #F5F5F5" | | ||
| + | |} | ||
| + | |||
| + | |||
| + | {| | ||
| + | | width="50pt" align="center" style="background: #DCD0FF" | | ||
| + | | width="200pt" align="center" style="background: #DCD0FF" | '''Name of Working Session''' | ||
| + | | width="200pt" align="center" style="background: #DCD0FF" | '''Objective(s)''' | ||
| + | | width="200pt" align="center" style="background: #DCD0FF" | '''Outcome(s)/Deliverable(s)''' | ||
| + | | width="150pt" align="center" style="background: #DCD0FF" | '''Owner/Leader''' | ||
| + | | width="150" align="center" style="background: #DCD0FF" | '''Members/Attendees''' | ||
| + | |- | ||
| + | | style="background: #F5F5F5" align="center" | [[Projects Summit 2014/Working Sessions/006 | View]] | ||
| + | | style="background: #F5F5F5" align="center" | [https://www.owasp.org/index.php/Category:OWASP_PCI_Project PCI Toolkit] | ||
| + | | style="background: #F5F5F5" | | ||
| + | | style="background: #F5F5F5" | | ||
| + | |||
| + | | style="background: #F5F5F5" align="center"| Johanna Curiel | ||
|style="background: #F5F5F5" | | |style="background: #F5F5F5" | | ||
|} | |} | ||
Revision as of 17:18, 6 May 2014
| |
|
|---|---|
|
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.
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.
| Name of Working Session | Objective(s) | Outcome(s)/Deliverable(s) | Owner/Leader | Members/Attendees | |
| View | OWASP Education Project | 1. Re-thinking the concept of OWASP University Supporter
2. Expand the concept of the OWASP Student Chapters. 3. Establish and expand the OWASP University Challenge. 4. Suggested application security curriculum. 5. Discuss and establish the concept of OWASP Academic Advocate. |
1.
2. 3. 4. |
Konstantinos Papapanagiotou, Vasileios Vlachos, Martin Knobloch |
| Name of Working Session | Objective(s) | Outcome(s)/Deliverable(s) | Owner/Leader | Members/Attendees | |
| View | OWASP Media Project | 1. Present the official OWASP YouTube channel
2. Involve project leaders to promote their content |
1. Create live and recorded video contents for OWASP projects | Jonathan Marcil |
| Name of Working Session | Objective(s) | Outcome(s)/Deliverable(s) | Owner/Leader | Members/Attendees | |
| View | OWASP 24/7 Podcast Series | 1. Have four(4) Project Leaders volunteer to be interviewed for the series. | Mark Miller |
| Name of Working Session | Objective(s) | Outcome(s)/Deliverable(s) | Owner/Leader | Members/Attendees | |
| View | OWASP Developer Guide | 1. More actively engaged volunteers and rebuild the project within OWASP so it can become self-sustaining.
2. More DevGuide text (at the very least, I hope to finish one chapter during my remote hack-a-thon). 3. More awareness of the Dev Guide's importance and history to OWASP. 4. To work with volunteers to discuss and refine the roadmap. |
Andrew van der Stock |
| Name of Working Session | Objective(s) | Outcome(s)/Deliverable(s) | Owner/Leader | Members/Attendees | |
| View | OWASP Code Review Guide | 1. Collect a number of bad coding examples to show readers code they should avoid writing.
2. Collect a number of good coding examples to show readers how security code should be written. 3. Collect the above for Java, PHP and C# languages, plus possibly C/C++, Ruby, Python, Perl, etc. 4. Raise awareness of the ongoing Code Review Guide and encourage OWASP members to participate in the project. |
Gary Robinson |
| Name of Working Session | Objective(s) | Outcome(s)/Deliverable(s) | Owner/Leader | Members/Attendees | |
| View | PCI Toolkit | Johanna Curiel |
