...
Location
https://goo.gl/maps/NToNbqDtfdXDA2dk9 5. OG
Please be aware, that the Governance Committee Meeting on the days before will be located here: https://goo.gl/maps/ZpSkae2ks8nkMqLS6
Evening meeting in Beer Garden: https://goo.gl/maps/QPpXtf9T7k1dV9Av9 or https://goo.gl/maps/JU35qBzyLtbByG6o7
\uD83E\uDD45 Goals
\uD83D\uDDE3 Discussion topics
Brainstorming on agenda topics:
Adapters and their use in Sandbox and Testing Procedures
Practical enactment of compliance concept, detailed instructions to give partners
Additional UX assets: Reusable UX patterns
Learnings from bringing Specs into practice
Reality Check: With all the assets planned so far (compliance concept, testing harness, adapters,...), can we forecast, if the envisioned marketplace or software products is realistic? Or will we get stuck with 1-2 solutions because of the needed resource Investments.
Feedback to Spec work: From an implementer perspective, what would be expected?
Collaboration and general principles for the future (what could speed up the Govstack idea to evolve)
✅ Action items
⤴ Decisions
Topic Backlog And Notes
Packaging (Jarkko)Status colour Green title Done BB Candidate to be packed for easy deployment
Export/Import of multiple BB configurations/whole instance (Use Case focused?)
At least first version in GovStack Release 2.0
Configuration and Seed DataStatus colour Green title Done Share Test Data between Soldevelo and Gofore
Collaborate on common source of synthetic data
Process and Project Management. How to work together.Status colour Green title Done Streamline developer teams to one common team
Shared Backlog or Collaboration Board for Division of Goals
Common Backlog Planning with Arch WG, Soldevelo and Gofore Team. On work described in the timeline below, assign issues to either Meelis Zujev (Deactivated) or Dominika Bieńkowska (Deactivated)
Most Important Streams? Work on what?Status colour Green title Done
Cooperation Soldevelo/Gofore on Adapter Development?Status colour Green title Done Adapter as one key hurdle to have first running GovStack based Instance (Proof of concept running)
Work together on OpenIMIS and UNCTAD eRegistration tools?Status colour Green title Done Mifos: Share needed Endpoints
Mosip: Share needed Endpoints
UNCTAD eRegistration (=Registry)
Pick OpenCRVS or UNCTAD
OpenIMIS (=Registration)
Soldevelo already working on OpenIMIS → Synergy
Develop adapter together: Soldevelo + Gofore Team
Focus of Soldevelo? Example Implementations, Adapters, Extend Test Harness…?
Using Test Harness in Sandbox - Adding Deployment Test to Test Harness (Pawel)Status colour Green title Done Where is testing gone live? Owner?
Resources are in BB repositories
Possible limit of CircleCI Free. Who will own the subscription in future?
Integration of Exchange: Testing Results in Exchange
Docker Scripts and Files will be shared with Sandbox. Sandbox Team does not have to build new docker scripts
No further assets from the sandbox team are shared with Testing Team and vice versa
Software Product JourneyStatus colour Yellow title Second Prio Catalog: Very High Level Alignment Check, Automatic pulling of from sources
Compliance: API Testing and Manual FitGap Analysis
Sandbox: Deployment Readiness,…?
Timelines and ResourcesStatus colour Green title Done End of May
Endpoint Mapping of Happy Flow
Meeting with BB Providers to review timeline and priotize endpoints
Discuss in Arch WG how to design Cross-BB Authentication and Authorization Function for sandbox, basic principles
June
Soldevelo, Gofore, possibly OpenIMIS developers to work on integrating OpenIMIS (adapter) (1-2 sprints)
Potentially write adapter for Registry BB
Check compliance of the relevant endpoints with test harness (1 sprint)
After Azure PoC: Present Infrastructure Setup in Architecture WG
Implement Cross-BB Authentication and Authorization in Sandbox
Common repository/structure of synthetic data for each BB/use case
June/July:
BB Providers delivering a pre-version of their candidate only with Happy API
“Backend for Frontend”, Middleware Development
July/August:
Integrate all BB and Quality Assurance
Documentation being finalized (Gitbook)
Mid September: Release 2.0
Release: USCT Simulation, possibly with Online Construction Permit (purpose: Presentation)
Release: USCT Simulation combined with functional backend (purpose: replicatable for tech users)
Release: Sandbox Documentation and Tutorials to replicate Sandbox
Actions
- Involve contracted BB Providers (Mifos, MOSIP, XRoad, [Consent]) early on in piloting the Testing Harness Paweł Gesek
- Create a list of 2-3 candidates for each BB Steve Conrad
- Create draft of software journey to be shared in Tech/Product Committee or Architecture Group Nico Lueck Software Provider Journey
- List expectations from BB Providers and pain points for Gofore Team on integration work Meelis Zujev (Deactivated)
- Gofore will map all needed BB endpoints on Happy Flow Meelis Zujev (Deactivated)
- Required Happy Flow Endpoints will be shared with Mifos and Mosip Meelis Zujev (Deactivated)
- Required Happy Flow Endpoints will be served with non-contracted BB candidates and adapter developments Meelis Zujev (Deactivated) Paweł Gesek
- Wes Brown to set up meeting with Steve Conrad and Satya to discuss BB provider scope (APIs and deployment?) and prioritizing APIs for sandbox use cases
- Include security aspects in adapter concept, Authentication/Authorization Steve Conrad
- UNCTAD Licence useable for replication of Sandbox by others? Nico Lueck
- Soldevelo shares data used so far and creates common repository of synthetic data with Gofore and BB Providers Paweł Gesek