Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

    • Status
      colourGreen
      titleDone
      Cooperation Soldevelo/Gofore on Adapter Development?

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

      • Status
        colourGreen
        titleDone
        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…?

    • Status
      colourGreen
      titleDone
      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

    • Status
      colourYellow
      titleSecond 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

      • “Pre-warning” to 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)Unclear:

      • 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

      Testing Harness

      • Small Gaps but v1 API Scripts are finished

      • “Backend for Frontend” Development

    • July/August:

      • Integrate all BB and Quality Assurance

      • Documentation being finalized (Gitbook)

    • Mid September: Release 2.0

      • Release: USCT Simulation (purpose: Presentation)

      • Release: USCT Simulation combined with functional backend (purpose: replicatable for tech users)

      • Release: Sandbox Documentation and Tutorials to replicate Sandbox

Actions

...