Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M Memri
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • memri
  • Memri
  • Wiki
  • Schema Maintainer Role

Last edited by Ruben Daniels Jun 18, 2021
Page history

Schema Maintainer Role

As a schema maintainer you work together with other schema maintainers to keep the memri schema in a good state. The memri schema is a central repository of agreed items, properties and edges that are used across various plugins and front-ends. By having a central repository we ensure interoperability between the plugins and front-ends.

Each plugin is able to define their own schema. However, when there is too much drift between plugins that store the same data it will be hard to impossible for other plugins and front-ends to offer a consistent experience or analysis on that data. Having a consistent schema solves this problem.

As a schema maintainer you work with plugin developers on their schema design and you approve their schema by accepting their merge requests to the schema repository. As a schema maintainer you will get merge access to that repository and it is your responsibility to validate the schema for internal consistency, common sense and a good understanding of how the schema is used for analysis and display of items in the various user interfaces.

A fixed percentage of 5% of each bounty goes to the schema maintainer.

Clone repository
  • Acceptance criteria for plugins
  • Authentication Proposal for Plugins (Q2 2021)
  • Available UI Elements and their properties
  • CVU Expression Language
  • Community Liaison Role
  • Contribution Guidelines
  • FAQ | Plugin Development
  • Getting Started | Plugin Development
  • Home
  • How to setup a gitlab runner
  • List of Actions
  • List of possible plugins to build
  • List of supported CVU definitions
  • Memri overview & components
  • Mentor
View All Pages