...
Item | Read more at… | Notes |
|---|---|---|
Advisory Board meeting | December 5th 3-4:30pm.
Comments Hani: Need to ensure that GovStack remains relevant in the DPI space and work with the advisory board to better connect with groups progressing in this space Margus: Important to note that many of the others in the DPI space are working on specific products/implementations so the focus is slightly different. May be helpful to discuss one question more deeply with the Advisory Board rather than multiple questions Yolanda: Some of these DPI products have already started in the GovStack compliance process. Suggestion that there is too much content to pre-read, a higher level summary could be more helpful Nora: Initial slides are just for working and will be removed before it is sent out to the Advisory Board Yolanda: Question about the run-of-show for the meeting. Nora is sharing the agenda Decisions Will work to find a specific question to focus on for this board meeting | |
Collaboration with CDPI | Hani´s email con CPDI | Joint specs for VC&Wallets, Payments Margus: Interesting opportunity but need to ensure that we have a broad representation of products in these spaces Nora: Helpful to define, in writing, how this relationship will work Wes: Seems like a great idea. Need to get clarity on how we should engage and how we can best support in this work. ++ to Margus comments Hani: My role is to make the connection, Wes/Ramkumar to organize the working group until a coordinator. Will prepare some potential working arrangements, goal to start the working group early 2024. Margus: Suggest that we reply with “Yes, we are interested” but we need to figure out the broad working group before getting started. Could specifically reach out to those involved with the EU Digital Identity/Wallet Andrea: Do we share the same principles and CoC with C4DPI? |
Information Classification: Document Storing | GIZ will be reviewing who has access to the various resources in the coming weeks. Contact Puja Raghavan if access needs to be reviewed after the updates | |
Template for Team Update Sharing Nico Lueck | Changes: Instead of non-defined groups like “GovTest” use Team structure to share recent updates. Each team only once a month. Decision taken: Teams are split between GC and PC and where to share updates. Comments Wes: The GC is better for strategic decisions and we spend much of our time in the priority discussions and would not have time to hear from the team. Updates from teams is better placed in the “operations” meetings (Country, PC, TC). Hani: The GC is not a decision-making meeting, except for the SGC. Do not want to add an additional meeting now that we are shrinking. Suggests that the updates are done in the “coordination meeting.” | |
Updates on Estoniafrom Margus | Role will be changing starting in 2024 and will be off all of December. |
Actions
- Nico Lueck will add Sandbox to the TC team list, since technical aspects are discussed there.
- Nico Lueck Add a section in the Governance Committee template for team updates/sharing progress.
- Sarah Fischer to set up meeting to discuss how the branding and collaboration processes can be reflected on the GovStack web site
- Wes Brown and Sarah Fischer to add Hans Christian Ende to Confluence and GIZ resources (Wes - Done)
...