2023-01-04 - Product Committee

 Date

Jan 4, 2023

 Participants

  • @Wes Brown

  • @Nico Lueck

  • @Steve Conrad

  • @Sainabou Jallow

  • @Sarah Farooqi

  • @Shukla, Ayush

  • @Dominika Bieńkowska (Deactivated)

  • Farina Carolina Owusu

  • @Taylor Downs

  • @Meelis Zujev (Deactivated)

  • @Moritz Fromageot

Meeting Recording

Recording URL:

 Discussion topics

Item

Presenter

Time

Notes

Review Action Items

@Wes Brown

5 min

 

GovStack Product Typology

@Moritz Fromageot

10 min

Sharing Compliance Concept with Governance Committee on Monday (Jan-9). How do we represent software related to GovStack but not specifically implementing a building block (Complementary Software vs Compliant Software)?

Version 0.9 of the compliance document has been created: Software Compliance Concept

Questions/Comments

  • Taylor: Complementary software?

    • Moritz: Some partners are interested in becoming “a part” of GovStack and have existing systems

  • Taylor: Attest vs Declare

    • Nico: Must vs should

  • Taylor: Native vs Adapter?

  • Wes: Remove mention to ansible as a required scripting tool

  • Wes: Propose that we remove the Architecture and BB requirements until they are reviewed and updated

Clarifying Country, “Product”, Technical, and Application Roles

@Wes Brown

15 min

The currently defined relationship:

Country Requirements → “Product” Use Cases → Technical Specifications → Application Development

The “Product” Committee Name

@Wes Brown

10 min

Using the term “product” for this committee has been confusing for a long time. Let’s figure out a better (or at least less overloaded) term and use it instead

GovStack Data Standards

@Taylor Downs / @Steve Conrad

5 min

Comments:

Nico: Might be helpful to get feedback from gofore team (sandbox)

Meelis: More specific is good but understand the use cases that drive the APIs

Sarah: Could be helpful to align BB to a specific DPG (or DPGs) as potential candidate systems and then broaden

Not Discussed

 

 

 

Documentation System of Country Engagement Activities on Confluence

@Shukla, Ayush

5 min

 

DPG / DPI and GovStack

 

10 min

Wes - Is there confusion around this and, if so, what needs to be clarified?

Terminology

@PSRAMKUMAR

5 min

Wes - What actions, if any, are still required on this?

GovStack Release Update

@Wes Brown

5 min

Based on feedback from the various partners, we are going to target the end of March, 2023 for our GovStack 1.0 release.

 Action items

@Wes Brown to break apart use case steps into individual document pages
@Jaume DUBOIS to translate GovStack slides into French
@Shukla, Ayush to create a live master directory document with links to all relevant GovStack folders/files across the technical and non-technical workstreams. @PSRAMKUMAR to then circulate this master directory link to all team members.
@PSRAMKUMAR to share notes on the terminology process presented during the Product Committee meeting.

 Decisions

  1. Mortiz will share Compliance process with GC and will set a deadline for self-assessment requirements to be ready