Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ESCAPE metadata template ESCAPE metadata template
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ESCAPE2020
  • WP3
  • ESCAPE metadata templateESCAPE metadata template
  • Issues
  • #7

Closed (moved)
(moved)
Open
Created Aug 12, 2021 by Vuillaume@vuillaumeOwner

metadata to indicate services to run the software

Exchanging with WP5 raised the idea to have a mybinder entry in the metadata to know that the software can be run by mybinder service. In a more general way, it raises the questions if a OSSR software provider should be aware of ways to run its software in the ESCAPE virtual environment and if yes, how this should be implemented in the metadata schema.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking