2026-02-02 Governance Committee Meeting

2026-02-02 Governance Committee Meeting

Feb 2, 2026

This page describes the GovStack meeting notes. We use this meeting page to both run the meeting and keep notes, actions and decisions.

To avoid long meeting where the current status of each report is read out, we ask all participants to read the links below before the meeting, add in any questions they may have and then ask them in the meeting. This will focus the meeting upon the questions, decisions and actions needed for greatest impact.

Participants:

ITU:

GIZ:

EE: @Hans Christian Ende @Kristo Vaher

Moderator: @Merle Wangerin

0. Celebrate

Item

Read more at…

Notes

Item

Read more at…

Notes

 

 

 

 

 

 

1. Roadmap

https://govstack-global.atlassian.net/wiki/pages/createpage.action?spaceKey=gh&title=GovStack%20Roadmaps&linkCreation=true&fromPageId=1795063809

2. Priority Discussions

Item

Presented by

Notes

Action needed

Item

Presented by

Notes

Action needed

Feedback from bilateral discussions BMZ >< MFA Estonia

No news since last week

 

Update and input on Brussels visit, 9 February

 

Marika shared a document as framework for the preparation. Important to organize meetings asap and be coordinated.

GIZ, BMZ, EstDev, MFA to propose meetings ASAP

Sandbox

Nico

 

POSTPONED (need Jody)

Feedback Loop from Country Engagement

Marika

Country level feedback mainly lies with technical consultants on specifications. Partner countries also need to be involved. Need to get better in tracking how specifications have been used (hard to track open source). Important to know how specifications are used and qualitative review.

Objective: improvements on specifications, learning how specifications are applied, impact stories for communication.

Ideally, EstDev, ITU, GIZ need to collect information from country implementation.

 

Begin with one key country and test “feedback approach”

Actions

3. Team Updates and Opportunities for Strategic Decisions

Every GC meeting one cohort is requested to share updates in written form in this table.

Every team has the opportunity to request direction/decision from the GC.

Put to the cohort which is requested to give updates in this GC meeting. One cohort per weekly GC meeting results in one update from all teams a month.

Cohort 1

Decision Need

Item

Brought in by…

Notes

Item

Brought in by…

Notes

 

 

 

 

 

 

 

 

 

Actions

4. Communications and Events

Item

Read more at…

Notes

Item

Read more at…

Notes

 

 

 

 

 

 

Actions

 

Decisions

5. AOB

Item

Read more at…

Notes

 

 

Item

Read more at…

Notes

 

 

 

 

 

 

 

 

 

 

 

Actions

Decisions