Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • sentinel-legacy sentinel-legacy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • SASC
  • sentinel-legacysentinel-legacy
  • Issues
  • #23
Closed
Open
Created Jul 22, 2015 by bow@w.arindrarto

Split core functionalities and LUMC-specific code into different packages

To make Sentinel more extensible, we should clearly separate the packages which are of general usage and packages specific to LUMC.

Something like this would be preferrable:

  • Core

    • Adapters
    • Processors
    • Internal data models
  • LUMC

    • All LUMC pipeline-related code
    • Current HTTP endpoints
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking