Difference between revisions of "Projects Summit 2013/Working Sessions/001"

From OWASP
Jump to: navigation, search
Line 3: Line 3:
 
| summit_track_logo = [[Image:Working_Session.jpg]]
 
| summit_track_logo = [[Image:Working_Session.jpg]]
 
| summit_ws_logo = [[Image:Working_Session.jpg]]
 
| summit_ws_logo = [[Image:Working_Session.jpg]]
| summit_session_name = ESAPI Hackathon
+
| summit_session_name = ESAPI Hackathon: 1st Session
 
| summit_session_url = http://www.owasp.org/index.php/Projects_Summit_2013/Working_Sessions/001
 
| summit_session_url = http://www.owasp.org/index.php/Projects_Summit_2013/Working_Sessions/001
 
| mailing_list = Google Groups: [https://groups.google.com/forum/#!forum/owasp-project-summit-2013 owasp-project-summit-2013]
 
| mailing_list = Google Groups: [https://groups.google.com/forum/#!forum/owasp-project-summit-2013 owasp-project-summit-2013]
Line 37: Line 37:
 
| summit_session_objective_name3 =  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.  
 
| summit_session_objective_name3 =  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.  
  
| summit_session_objective_name4 = 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).
+
| summit_session_objective_name4 =  
  
| summit_session_objective_name5 =  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.
+
| summit_session_objective_name5 =   
The prize will be awarded at the closing of the conference.
+
  
 
|-
 
|-

Revision as of 23:04, 26 September 2013

Global Summit 2013 Home Page
Global Summit 2013 Tracks

Working Session.jpg ESAPI Hackathon: 1st Session
Please see/use the 'discussion' page for more details about this Working Session
Working Sessions Operational Rules - Please see here the general frame of rules.
WORKING SESSION IDENTIFICATION
Short Work Session Description Coordinate a Hackathon where ESAPI Project Goals are worked on and delivered based on the roadmap.
Related Projects (if any)


Email Contacts & Roles Chair
Chris Schmidt @

Operational Manager
Kevin Wall @
Mailing list
Google Groups: owasp-project-summit-2013
WORKING SESSION SPECIFICS
Objectives
  1. 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.
  2. 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.
  3. 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.

Venue/Date&Time/Model Venue/Room
AppSec USA 2013: Times Square, New York City
Date & Time
Monday, November 18th: 1PM - 3PM


Discussion Model
participants and attendees

WORKING SESSION OPERATIONAL RESOURCES
Projector, whiteboards, markers, Internet connectivity, power

WORKING SESSION ADDITIONAL DETAILS

NEW-PROJECTS-BANNER2.jpg

Chair: Chris Schmidt

Chris is currently the Project Leader for the OWASP ESAPI Projects and also serves on the OWASP Global Projects Committee. He has been involved with OWASP for 4 years and has spoken at many OWASP events about the benefits of the Enterprise Security API as well as participated in Leadership discussions amongst the organization. During the day, Chris is an Application Security Engineer and Senior Software Engineer for Aspect Security where he has been since fall 2010. Prior to joining the team at Aspect Security he spent 5 years as 'Black Ops Beef' for ServiceMagic Inc with the official title of Software Engineer. Before getting involved in software professionally, Chris worked in hardware as a Senior Field Service Engineer providing hardware and software support for PC’s, Servers, Midrange Systems and Peripherals for 9 years.

Operational Manager: Kevin Wall

Experienced Application Security developer, OWASP ESAPI Project co-owner.

WORKING SESSION OUTCOMES / DELIVERABLES
Proposed by Working Group 'Delivered by Working Group

Identify the primary goals to deem the hack-a-thon a success.

After the Meeting - fill in here.

Layout the overall architecture vision for ESAPI 3.0.

After the Meeting - fill in here.

Lay down the infrastructure (Git, Continuous Integration, Testing Framework, etc.).

After the Meeting - fill in here.

Design the specification for the components that will be required.

After the Meeting - fill in here.

Close down all inactive ESAPI Projects.

After the Meeting - fill in here.

After the Meeting - fill in here.

After the Meeting - fill in here.

After the Meeting - fill in here.

Working Session Participants

(Add you name by clicking "edit" on the tab on the upper left side of this page)

WORKING SESSION PARTICIPANTS
Name Company Notes & reason for participating, issues to be discussed/addressed

{{{summit_session_attendee_company21}}}
{{{summit_session_attendee_notes,_reason_for_participating_and_issues_to_be discussed21}}}
Dennis Groves @


Dinis Cruz @


Samantha Groves @


Johanna Curiel @


Seba @


Chris Schmidt @


Kevin Wall @


Jeff Williams @