Notes from 2023-10-27 Pod Meeting

Focus: Reviewing Gitcoin Passport New Feature Launch Checklist (November 2023 Edition)
Attendees
  • Gary
  • Jeremy
  • Dan
  • Laura
  • Gerald
  • Erich
  • Owocki
Introduction (1 min)
  • Brief Overview: Silent read-through and discussion of the Gitcoin Passport New Feature Launch Checklist for November 2023.
Silent Read-Through (5 mins)
  • Team members silently read the Gitcoin Passport New Feature Launch Checklist document to prepare for discussion.
Open Discussion: Points of Contention/Objection (19 mins)
Process
  1. Each attendee can briefly mention their points of contention or objection related to the document; or if it the document looks good to them.
  1. Open the floor for discussion on each point raised, aiming to clarify or resolve issues.
Issues + Other Notes
  • Jeremy: Size of features are very different
    • Some of the items in the engineering complete feel like a lot of overhead for engineering team if it’s like a score algo update or UI change
      • Not fan of PRD / C&E brief as default
  • Gerald:
    • Very important from my point of view: API changes must go through a "Feature launch" and we must align with Daniel
      • no changes without consulting devrel first
  • Jeremy:
    • Small eng effort might be big marketing effort
  • Jeremy:
    • Every change must be documented on GitHub at minimum
  • Daniel:
    • How can we make sure these product details are curated in a low burden way, and in a way that works with our distributed team?
    • Async first culture
  • Erich:
    • We deploy new things to staging.passport.gitcoin.co on early morning Europe time Monday, and push to prod on Wednesday
      • we can test on review environment earlier
    • Jeremy: The more people playing and testing with staging and review the better, we'll be WAY more likely to catch things!
Β 
Action Items
Note down unresolved issues for future meetings or action
  • Consider changing GitHub Issue (Not Now)
    • Does it have end user impact, developer impact, or both? (
  • Update Weekly Update to link to GitHub issues
  • Update Weekly Update to share something coming up in the next month
  • Weekly Marketing Meeting can go over upcoming backlog items that will have end user impact, developer impact, or both
Β 
Summary and Next Steps (1 min)
Quick summary of points covered and action items identified.
Β 

Notes from 2023-10-27 Pod Meeting

Focus: Reviewing Gitcoin Passport New Feature Launch Checklist (November 2023 Edition)
Attendees
  • Gary
  • Jeremy
  • Dan
  • Laura
  • Gerald
  • Erich
  • Owocki
Introduction (1 min)
  • Brief Overview: Silent read-through and discussion of the Gitcoin Passport New Feature Launch Checklist for November 2023.
Silent Read-Through (5 mins)
  • Team members silently read the Gitcoin Passport New Feature Launch Checklist document to prepare for discussion.
Open Discussion: Points of Contention/Objection (19 mins)
Process
  1. Each attendee can briefly mention their points of contention or objection related to the document; or if it the document looks good to them.
  1. Open the floor for discussion on each point raised, aiming to clarify or resolve issues.
Issues + Other Notes
  • Jeremy: Size of features are very different
    • Some of the items in the engineering complete feel like a lot of overhead for engineering team if it’s like a score algo update or UI change
      • Not fan of PRD / C&E brief as default
  • Gerald:
    • Very important from my point of view: API changes must go through a "Feature launch" and we must align with Daniel
      • no changes without consulting devrel first
  • Jeremy:
    • Small eng effort might be big marketing effort
  • Jeremy:
    • Every change must be documented on GitHub at minimum
  • Daniel:
    • How can we make sure these product details are curated in a low burden way, and in a way that works with our distributed team?
    • Async first culture
  • Erich:
    • We deploy new things to staging.passport.gitcoin.co on early morning Europe time Monday, and push to prod on Wednesday
      • we can test on review environment earlier
    • Jeremy: The more people playing and testing with staging and review the better, we'll be WAY more likely to catch things!
Β 
Action Items
Note down unresolved issues for future meetings or action
  • Consider changing GitHub Issue (Not Now)
    • Does it have end user impact, developer impact, or both? (
  • Update Weekly Update to link to GitHub issues
  • Update Weekly Update to share something coming up in the next month
  • Weekly Marketing Meeting can go over upcoming backlog items that will have end user impact, developer impact, or both
Β 
Summary and Next Steps (1 min)
Quick summary of points covered and action items identified.
Β