Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

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

Topic Backlog And Notes

  • Packaging (Jarkko) Compliance Level 2 (Nico)

    • BB Candidate to be packed for easy deployment

    • Export/Import of multiple BB configurations/whole instance (Use Case focused?)

  • Configuration and Seed Data

  • Process and Project Management. How to work together.

    • Streamline developer teams to one common team

    • Shared Backlog or Collaboration Board for Division of Goals

  • Most Important Streams? Work on what?

    • DONE Cooperation Soldevelo/Gofore on Adapter Development?

      • Adapter as one key hurdle to have first running GovStack based Instance (Proof of concept running)

      • DONE Work together on OpenIMIS and UNCTAD eRegistration tools?

        • 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…?

    • DONE Using Test Harness in Sandbox - Adding Deployment Test to Test Harness (Pawel)

      • 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

    • SECOND PRIO Software Product Journey

      • Catalog: Very High Level Alignment Check, Automatic pulling of from sources

      • Compliance: API Testing and Manual FitGap Analysis

      • Sandbox: Deployment Readiness,…?

  • Timelines and Resources

    • End of May

      • Endpoint Mapping of Happy Flow

      • Meeting with BB Providers to review timeline and priotize endpoints

    • 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

      • Build: Authentication and Authorization Function for sandbox

    • June/July:

      • BB Providers delivering a pre-version of their candidate only with Happy API

      • “Backend for Frontend” 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

Agenda

Time

Topic

09:00 - 09:15

Intro

Time Horizon <6 months

09:15 - 09:45

Recap of feedback from Governance Committee Review on Wednesday, 10.05.

09:45 - 11:00

Integration of DIAL Catalog, Testing Harness and Sandbox

  • DIAL Catalog integration in Frontend Simulation

  • Using API Tests in Sandbox

  • Showing test compliance for products within DIAL Catalog

  • Idea: Extend Testing Harness to Deployment etc. by Sandbox Team

11:00 - 11:30

Adapters and their use in Sandbox and Testing Procedures

  • Develop plan for building out first adapters with products being used in the Sandbox

  • What tools/technologies should we use to build first adapters?

11:30 - 12:00

Review and update short-term road map of Sandbox (MVP), DIAL catalog and Testing Harness

12:00 - 13:00

Lunch Break

Time Horizon 6-12 months

13:00 - 14:00

Revisit GovStack objectives: Are we on the right path to achieve the following?

  1. Multiple BB candidates tested and listed on the marketplace

  2. Subset deployed and used in Sandbox

  3. Sandbox being reused by Country Partners/Integrators

14:00 - 15:00

Mid-term road map based on discussion on objectives

E.g.

  • Additional (High Impact) Use Cases

  • Workflow/Capacities

  • UX Assets

15:00

Gofore Team Leaving to the Airport

\uD83D\uDDE3 Discussion topics

Brainstorming on agenda topics:

  • Adapters and their use in Sandbox and Testing Procedures

    • Develop plan for building out first adaptors with products being used in the Sandbox

    • What tools/technologies should we use to build first adaptors?

  • Integration of DIAL Catalog, Testing Harness and Sandbox

    • DIAL Catalog integration in Frontend Simulation

    • Using API Tests in Sandbox

    • Showing test compliance for products within DIAL Catalog

    • Idea: Extend Testing Harness to Deployment etc. by Sandbox Team

  • 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)

  • Review/Update deliverables for MVP

  • Review/Update timelines for MVP delivery

  • Discuss the Roadmap after the MVP

    • How do we scale this work so that future use cases do not require significant effort to implement?

  • Discussion on common workflows - how do we identify, create specifications and examples of these workflows in the Sandbox. How do we make them re-usable between use cases?

✅ Action items

⤴ Decisions

  • No labels