A Hack Pod is a 1-2 hour engagement between our GitHub teams and a customer/partner as we uncover places we can create reference architectures that act as starting points for customer adoption. Open source fellows (maintainers of this repo) drive the projects to completion/maintain them.
🗓 This Hack Pod is planned for mid-April from 12-1:30 pm PT.
What is expected of me as a participant?
On Game Day of the Hack Pod we'll convene on Zoom and then fan out in breakout rooms. Each track will have its own breakout and a few additional rooms will be available for areas customers feel passionate about.
Agenda:
Set up and intro Hack Pod
Hack Pod track leads go into breakouts and drive 1-2 examples based on those provided and surface others
Encourage and enable customers to take turns with additional examples to find the best scope for those present
How we hack: Each track breakout room (e.g., SCA/Dependabot) will consist of 2 leads, 2 maintainers and 6-8 customers. Maintainers are there to go 1:1 as needed in extra rooms.
Roles:
Leads:
We will pick a track from what we are hacking on to enable customers. Role: Write out answer keys for 1-2 tasks below before Hack Pod. Drive the examples Game Day of the Hack Pod.
Customer: JPMC
Adds questions to issues which help us make a robust starterkit asset post Hack Pod
What are we hacking on?
This Hack Pod focuses on jumpstarting JPMC's understanding of security through the following:
SCA/Dependabot and how to update your code post PR @momartinjazz @manishapriya94
What is a Hack Pod?
A Hack Pod is a 1-2 hour engagement between our GitHub teams and a customer/partner as we uncover places we can create reference architectures that act as starting points for customer adoption. Open source fellows (maintainers of this repo) drive the projects to completion/maintain them.
🗓 This Hack Pod is planned for mid-April from 12-1:30 pm PT.
What is expected of me as a participant? On Game Day of the Hack Pod we'll convene on Zoom and then fan out in breakout rooms. Each track will have its own breakout and a few additional rooms will be available for areas customers feel passionate about.
Agenda:
How we hack: Each track breakout room (e.g., SCA/Dependabot) will consist of 2 leads, 2 maintainers and 6-8 customers. Maintainers are there to go 1:1 as needed in extra rooms.
Roles:
What are we hacking on? This Hack Pod focuses on jumpstarting JPMC's understanding of security through the following:
SCA/Dependabot and how to update your code post PR @momartinjazz @manishapriya94
CodeQL examples @pwntester
Actions that integrate with other tooling for DAST, reporting, and other use cases @therealkujo @callmegreg
Diagram of context for customers
Resources:
https://user-images.githubusercontent.com/9143339/192820262-3ca9b95e-ff6d-421c-a30f-dcdda6d5c0de.mov
Timeline: