Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • SA3LI Trial SA3LI Trial
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SA3
  • SA3LI TrialSA3LI Trial
  • Issues
  • #6
Closed
Open
Issue created Mar 18, 2020 by carignani@carignaniOwner

Repository structure

Context

We have created a Trial area to explore the possibilities of the Forge. When we transition to using the Forge for real, we need to establish how we organise our deliverables (TS 33.128 and TS 33.108) as "projects" in the Forge.

A proposal is to have one project per deliverable, under the 3GPP "Group". Additionally, we may wish to maintain an SA3LI "Shared" or "Common" project for things which are common to both - principally test tools for checking ASN.1 and XSD.

This would give us the following projects, which we can ask ETSI Forge maintainers to create for us.

  • SA3LI TS 33.128
  • SA3LI TS 33.108
  • SA3LI Shared Resources

Question

Is this the right repository structure?

Edited Mar 18, 2020 by carignani
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking