considerations for renaming from team-project to team/project

23 views
Skip to first unread message

Justin Georgeson

unread,
May 4, 2015, 5:36:31 PM5/4/15
to repo-d...@googlegroups.com
I found these two links


and was wondering if there are any extra considerations when introducing a '/' into the project name. I see on the back-end using project names like this creates a folder structure, but the project list in the web UI doesn't become multi-level or hierarchical, so there's no benefit there to such a rename. Also, I don't see that there's any real administrative benefit in the sense that I can give a group ownership of all team/* projects. I would still have to do something like create a permissions-only project called team and remember to create all team/* projects to inherit from that.

So it doesn't seem there's any real user-facing benefit. Am I missing something?

Edwin Kempin

unread,
May 5, 2015, 3:03:52 AM5/5/15
to Justin Georgeson, Repo and Gerrit Discussion
2015-05-04 23:36 GMT+02:00 Justin Georgeson <baron...@gmail.com>:
I found these two links


and was wondering if there are any extra considerations when introducing a '/' into the project name. I see on the back-end using project names like this creates a folder structure,
If you have many projects it's better to structure them in a folder hierarchy, as a single folder that contains all projects as a flat list may result in performance issues on the filesystem.
 
but the project list in the web UI doesn't become multi-level or hierarchical,
Yes, but this may be added in future.
 
so there's no benefit there to such a rename. Also, I don't see that there's any real administrative benefit in the sense that I can give a group ownership of all team/* projects. I would still have to do something like create a permissions-only project called team and remember to create all team/* projects to inherit from that.
True.
 

So it doesn't seem there's any real user-facing benefit. Am I missing something?
Not really. You may benefit if you want to make use of the quota plugin [1], as there you could define a single quota for all 'team/*' projects.

[1] https://gerrit-review.googlesource.com/Documentation/config-plugins.html#quota
 

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages