Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
Docs Publisher
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Documentation
  • Docs Publisher
  • Issues
  • #25

Closed
Open
Created Jan 25, 2017 by Sean Colsen@seanmadsenDeveloper

Clarify role (user / admininstrator / developer) terminology

Created by: michaelmcandrew

The words user and developer are pretty clear.

Administrator is ambigious since it can refer to

  • an advanced user that sets things up for other users using the UI
  • a system administrator that does stuff like install, host, and is familiar with CLI, SSH, FTP, DNS, etc.

I'm not sure that coming up with a rule like "administrator MUST only be used to signify system administrator" is a good idea since language is nuanced. On the other hand, if we could could up with an acceptable phase for an "advanced user that does set up" that might change my mind.

Alternatively, just some sensible guidance on how we refer to different roles would be good to have in the documentation guidelines.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None