Skip to content

Latest commit

 

History

History
109 lines (89 loc) · 4.37 KB

File metadata and controls

109 lines (89 loc) · 4.37 KB

Why join a hack pod?

Make new friends across the industry in similar roles as you Opportunities to practice leadership: It is also a great opportunity for those who wish to gain more experience in handling the responsibilities of a more senior engineer or team lead Each hour counts towards donation credits since you’re volunteering with GitHub Education Use this in your next reflection for customer facing activity (template)

What are hack pods?

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. We aim to continue giving back to open source by fostering the next generation of developers. Learn more

Mentor Pair Process:

What to expect in each pair hour?

Review discussion standup to prepare for questions beforehand.

Structure of the hour: Each pair hours has pair hour mentors and one external team/GitHub team

Fellows Pair Hour Mentor: Maintainer participants
  • Will have copilot prompts to follow for their issue
  • Templates what to write down from mentors post pair hour
Before:

Will have a calendar invite

Rewatch Series has the discussion from prior week

During: Drive the pair session with fellow

After: review PR

This can include maintainers or company partners (like a Batch DRI) communicating any changes during the execution of the batch, such as unexpected issues or a revised target date.

What is the stack?

🖼 🎨 ⚙️ Fullstack development stack uses Vue, Node, and Postgres. 🔍 QA uses Jest and Typescript.

What is a successful pair hour/overall program look like?

  • learning has happened! Whether its about the stack or the SDLC in general
  • Sometimes that looks like..
    • having an outline of tasks to accomplish on an issue debugging and getting people
    • 'unstuck' within a rough draft PR
    • code review of a PR
    • What experience do students have? students are coming with some GitHub experience and stacks related to Javascript and Ruby.

Some resources before the meeting:

  • you should have a calendar invite for weeks you've signed up for

  • Join the #pair-hours-mentor channel in ProgramEquity slack , internal GitHub channel is #open-source-mentors

  • Check out the project view for the hour here

  • Project Repo (please ensure you've set up codespaces before the session)

Issue Labels

  • good first issue - we’re ramping and learning about the stack with copilot having most answers
  • intermediate - we’re implementing and it might require us to check copilot answers + debug with mentors
  • research - time to compare solutions and lean into mentors to compare and contrast

Epics & Batches

    • Data models
    • Lob cardinality
    • Lob bugs
    • Letter customization
    • Constituent data
    • From a form?
    • Refresh Checkout
    • Auth0 and User login
    • User notifications: Twilio
      • Constituent data structure look at
      • Message from from group to users
      • Analytics for user education
    • Feature Flags
    • Cloud/hosting
    • Audits: logging when anything goes down
    • Actions workflows
    • Repo Setup and Permissions
    • Security:
      • Dependabot
      • Advisories