2023-09-27 - Product Committee

5 min

@Aleksander Reitsakas & @Rachel Lawson (Unlicensed)

15 min

ITU have funded a number of software products that implement building blocks.

• Where should the repos for these products be stored?

• If we place them in GovStackWorkingGroup, are we saying that we will maintain them?

• How do we decide on which products form the GovStack product set? The Product Owner?

Discussions

The products that were adapted/updated for GovStack compliance will need to be maintained over time. Who is responsible for that work? How will it be tracked?

Ramkumar: The contracted companies have not yet delivered their goods. The general question is where we store this content (whether coming from contracted work or from others) in the future. Also want to encourage and support Product Owners who will do this themselves

Steve: GovStack should not be responsible to maintain specific providers. This could create a conflict of interest and we don’t (currently) have capacity to do this anyway. Suggest that each contracted company be responsible to create an accessible repo for the BB provider they implemented

Margus: These providers could also be contributed back to the project in question. There are some legal questions about the IP (Wes: this is true for much of GovStack). The maintenance of the provider can be with the contracted company

Rachel: Discussion on Slack here: https://govstack.slack.com/archives/C02UJ17TQH2/p1695815884428459 . There are various types of content related to BB software (detailed in the Slack messages). Provider code should be located at ITU (the contract owner)

Nico: Originally the expectation was that BB software config (and code?) would reside in the examples folder in the BB repo. That does not seem to be feasible now. As much as possible try to locate at the project owner.

Wes: I would have a priority list:

1. Project (e.g. Mosip)

2. Contract Vendor (Nortal)

3. GovStack (host repo but no maintenance)

One and two are very unlikely to continue maintaining code

Margus: The overhead may not be very much for the project (Wes: I strongly disagree here). Vendor may have a vested interest to maintain their provider

Ramkumar:

@Nico Lueck

15 min

Purpose: Sharing status and sync of all products being development within GovStack

Example: @Nico Lueck can do a 5 min update on compliance team status

Wes: I suggest that we change the focus of the PC to Operations and Team Updates. The Reference Use Cases becomes another team that provide an update

Margus: In favor of changing the focus of the PC but worried about managing the time. Teams should prepare simple bulleted list of updates prior to meeting, unless a presentation (or something) is needed.

Ramkumar: Viewpoint should be on specific products (GovGood) and what needs to be done with them. Not just status updates. Align it to the product roadmap

Wes: I purpose that we make changes to the meeting after the 23Q3 publication

@Sainabou Jallow

20 min

Business taxation use case: GitBook

• Some questions on detailed aspects of the taxation process.

@Steve Conrad

15 min

@Sainabou Jallow

20 min

Use Case: GitBook

@Wes Brown

5 min

• Discuss the eMarketplace building block and how to include it in the Market Linkage use case

• Discuss working on a procurement platform reference use case

GIZ, Estonia, Dial, ITU