You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in the RC5 Retrospective document, there needs to be governance processes to manage components. I have a few ideas on how this could work, so will write those up for feedback.
The text was updated successfully, but these errors were encountered:
Email sent to GA4GH groups ga4gh-discovery-networks, discovery, ga4gh-discovery-search, beacon on 26th February 2019:
Hi All,
Please find the following two links in regards to the Schema Blocks governance discussion.
Please note these are both still just drafts (some editorial notes remain), and not necessarily accepted or approved by anyone as of yet.
Both are open for comments. Please speak your mind and feel free to ask questions.
A brief primer for the workflow diagram:
The workflow diagram is split into four sections.
The first two sections contains a valid end point, where a schema is published by a workstream or group for wider use, and doesn’t go through any formal review outside of what that group require.
The last two sections express a space where groups look to converge and standardise on schemas, looking to move to GA4GH product approved status.
A brief primer for the long document:
The overarching goal of the document is to describes the processes, workflows, and community expectations of how SchemaBlocks does work.
Much of the document outlines details on best working practices relating to working as a collaborative on Github, which will likely be familiar to technical individuals.
These processes and expectations are based on:
Best practices strongly recommended by the GA4GH product approval document
Recognising that driver projects and workstream products / projects need to have autonomy but support available
Existing similar scale schema stores / library project policies, such as the (huge) Human Cell Atlas JSON Schema store
As mentioned in the RC5 Retrospective document, there needs to be governance processes to manage components. I have a few ideas on how this could work, so will write those up for feedback.
The text was updated successfully, but these errors were encountered: