Versions Compared

Old Version 2

changes.mady.by.user Mark Cornall

Saved on

compared with

New Version 3

changes.mady.by.user Casey Cain

Saved on

Key

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

...

Community: Herbert Damker  @Gabriel Iklaga Sachin kumar Tanja de Groot Rafal Artych Mark Cornall Samuel Adeyemo 

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

...

  • Work products needed:
    • Commonalities
    • Identity & Consent Management
    • Release Management
      • Overview of released APIs and their version and status
      • Release management process
    • For each (API) sub projects: 
      • API Definition(s)
        • Following the Commonalities guidelines
        • Successful linting check (with latest rules provided by Commonalities
        • Inline documentation, usable together with swagger editor and redoc
      • Test definitions
        • .feature files according to guideline from Commonality (comes with v0.2.0)
      • Supplementary documentation if needed to use or implement the API definition(s)
        • User documentation should be including the API Definition
  • Dependencies:
    • Release Management <= Commonalities, API Sub Projects
      • Needs information (e.g. scope definitions) about the planned and done releases from the sub projects
      • This information has to be provided in a way that can be automated collected
    • API sub project(s) <= Commonalities
      • all API Sub Projects need to know the release of the Commonalities documents and artefacts which they have follow for their release
    • Commonalities <= Identity & Consent management
      • Commonalities (a release of Commonalities is referring to documents within a release of I&CM)
  • Potential milestones:
    • Kick-off
      • Scope of I&CM and Commonalities
      • 4 weeks
    • Release candidates of Commonalities
      • Scope defined per sub projects (could be part of one the previous lines)
      • 4 weeks
    • Release of CommonalitiesScope planned per
      • 4-6
    • (First) Release Candidates of sub projects
      • 4-6 weeks
    • Sub project releases
      • 2 weeks
    • Common Release Date ("packaging done for the community release")
    • Release Retro
  • Release cadence:
    • 2 releases per year as a target
  • Initial schedule:

Guidelines towards Sub Projects regarding releases and versioning

...