Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #21

Closed
Open
Created Oct 16, 2011 by Administrator@rootOwner

Suggestions for gitlabhq

Created by: sairam

I have suggestions for the future versions of gitlabhq. I am not including those already requested.

Some suggestions could be weird and localized though. Please ignore them.

Allow gitlabhq to

  1. manage repositories from multiple servers
  2. config files (config/gitosis.yml or any other repo config or email from field in devise ) should be editable from admin interface
  3. handle cases with permissions properly . Example(see #19 (closed)): If I do not have access to a repository , instead of a 50x or 40x response pages, display detailed error messages
  4. Allow managers like gitosis and gitolite to be pluggable
  5. Configurable attachment size and location(S3/other cloud/free repos etc) on Wall
  6. Limit repo sizes
  7. Limit total size of all repos
  8. Integrate wiki pages or allow a system to be pluggable
  9. Allow user login to be integrated with other systems (devise should take care of this already), but should be configurable from website by admin
  10. Provide a default root password to be longer
Assignee
Assign to
Time tracking