Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
dune-amdis
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Praetorius, Simon
  • dune-amdis
  • Issues
  • #18

Closed
Open
Opened Feb 24, 2019 by Praetorius, Simon@spraetorMaintainer

Naming of new amdis repository

As already discussed in some other issues, we want to move this repository into a new namespace away from spraetor. It is suggested to use the newly created namespace amdis to collect several amdis related modules, like the main repository, extensions, compositeFEM, ALE... But the question remains how to name the repository that will host the main amdis code. It should be kind of different from the current iwr/amdis, and should maybe highlight that it is related to the dune-library. Some Alternatives that you can vote for in the comments below:

  1. amdis/amdis. Pros: simple and clear naming, Cons: collides with the current AMDiS 1.2, and name doubling
  2. amdis/amdis2. Pros: Also very short and simple and resolves collision as in 1., Cons: You always have to add a version number to the name of the repo
  3. amdis/core. Pros: More descriptive than just amdis and allows for future structuring and amdis modules, Cons: by default a git clone will create the directory core and does not include the name amdis
  4. amdis/amdis-core. Pros: as in 3. but additionally resolves the cons and is more in a dune module style, Cons: more verbose to write
  5. amdis/dune-amdis. Prod: directly highlights the relation to dune framework, Cons: the structure of AMDiS is a lot different from other dune modules. This could be irritating for other dune users.

What do you think is the best solution? Or, do you have a better idea, then let me know in the comments section.

Edited Feb 25, 2019 by Praetorius, Simon
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: spraetor/dune-amdis#18