AppVolumes Naming Standards

The idea behind the AppVolumes Naming Standards

The reason why we need to have some naming standards is to avoid mess and duplication.

Note that with the transition AppVolumes 4 we switch from appstacks to Applications and Packages. However, naming standard for both old and new system is included here.

Unlicensed software, open for everyone

If you make an Application containing Packages with only one unlicensed program, like e.g. Firefox, use the following standard:

• Application name: Program name
  • e.g. Firefox
• Package name: Program Name + Version Name
  • e.g.: Firefox ESR 5.0
• Appstack name: same as Package name

The idea is that, for every such program, UiO users can make use of the same shared Package/Application. If you need some program via a Package/Application, start by checking whether a suitable Package/Application already exists - that way we can avoid unnecessary double-work :)

Licensed software, faculty/department specific AppVolumes or LABs

If you have a program that uses a license server which belongs to your faculty/department or you want a collection of non-default programs for a lab, use the following format: 

• Application name: Faculty name abbreviated (med, hf, mn, etc.) + "something meaningful of your own choosing" (department name, course name, overall program theme, etc.), preferably with words/abbreviations separated by hyphens
  • e.g. mn-geo-geo42709  
• Package name: Same as Application name + indexing, seeing as the first Package normally is followed by updated Package versions
  • e.g. mn-geo-geo42709-v1, mn-geo-geo42709-v2, etc. or
  • if the Application name is already very verbose, it is possible for the Packages to have shorter names, so long as they are sufficiently descriptive and it is clear which Application the Packages belong to
• Appstack name: same as Package name, in general
  • e.g. mn-geo-geo42709 or mn-geo-geo42709-v1, etc.