Suggestion for better project organisation
Closed
Suggestion for better project organisation
Created by: jameswritescode
I sent this in an email to the mailing list, but didn't receive any responses and it was suggested I go ahead and post this here:
Hi all,
Using Gitlab for a handful of projects within my organisation and I've began to realize how it would be nice to have a feature similar to the GitHub organisations, (Gitlab Categories?) just not as in-depth.
Currently I'm working on two large projects with two separate groups of people, and both have multiple repos for various aspects of the projects. The downside of this is the naming scheme we're having to adopt for both projects so they do not have project name conflicts, so we're naming all projects starting with the project name and then what the repo is for, for example:
AlphaProj Website AlphaProj Client BetaProj Website BetaProj Client
It would be useful to be able to maybe categorize repositories. The example I have in my head right now goes along the lines of: Create a new repository Optionally create a category or select an existing one to file the repo under Other optional stuff like clone/url that already exist. Then something along the lines of this could exist after creation:
http://git.domain.tld/alpha/website vs http://git.domain.tld/alpha_website.git http://git.domain.tld/beta/website vs ... ...
Then in the projects sidebar the non-categorized projects could go under "Projects" and other div's for the projects that are in a category.
This would probably go nicely with the teams future addition, too.
Just a suggestion but I wouldn't mind discussion on this if anyone is open to it.
As I stated later in the email, I think this would go nicely with the teams addition, from issue #739
Thanks.
Created by: Vrtak-CZ
Seems like same as my issue #770 (closed)
By Administrator on 2012-05-30T10:43:46 (imported from GitLab project)
Created by: drf
Another interesting part of this is cascading permissions: suppose to have this structure:
alpha/ | --- first | --- second beta/ | --- third
What would be great (and is currently possible in bare gitolite via the "repo alpha/..*" wildcard) is to have a set of default permissions cascading to every repository under a specific dir. Moreover, allowing just a user/team to create repos would be another amazing feature.
Moving on with the suggestions, this would also open the path for global vs. personal repos, so that
repo1 repo2 alpha/ | --- first | --- second beta/ | --- third user/ | --- myuser/ | --- myrepo
would be possible - again, bare gitolite already allows this with a syntax like: "repo user/CREATOR/..*".
Just my 2c, should these + teams feature be implemented, Gitlab would totally rock my world :) (and allow to use some of the most amazing features in gitolite)
By Administrator on 2012-08-22T15:38:18 (imported from GitLab project)
Created by: lavoiesl
Groups, as of 3.0, are working only as tags; they do not modify the project in any way. It is useful to say things like "ongoing" or "R&D", but I still want proper directories (or namespace). I work with several clients and right now I am prefixing every project like
acme-mainwebsite. I would be nice to haveacme/mainwebsiteand give users permissions based on this namespacing, as said by @drf. That way, a client can view all projects in his namespace.To do this, and be backward compatible, as @mmikulicic said, when no namespace is given, it stays at root. When a namespace is given (or modified), it is moved to the new folder. Old URLs become invalid, but one can slowly migrate everything or only migrate new projects.
Cheers
By Administrator on 2012-10-24T14:31:07 (imported from GitLab project)
