Replace project limit with boolean flag (can_create_projects)

Created by: dzaporozhets

Based on experience of users in most cases there are 2 options:

1. let users create projects. count does not matter (limit: 10, 100 ..)
2. dont allow some projects to create repo at all (limit: 0)

So its simply convert to boolean field

Created by: riyad

+1

By Administrator on 2013-01-26T19:34:49 (imported from GitLab)

Created by: brodock

I think there are some valid use case scenarios where it's reasonable to have a count limitation. For example at my university, we are evaluating installing Gitlab for our students so they can be able to create repositories, but we are not interested in anyone spamming the system with hundred of thousands repositories just to reserve the namespace.

But there may also be valid use cases for unlimited creating power for example on small companies, etc. So I propose to use "-1" as unlimited, "0" as don't allow (the way it is today) and positive numbers as a max project limitation.

By Administrator on 2013-01-28T17:32:22 (imported from GitLab)

Created by: Philzen

+1 to what brodock said.

The current feature works fine, so it's reasonable to carefully expand it rather than slice it out of the system for good.

By Administrator on 2013-01-31T19:08:20 (imported from GitLab)

Created by: samurailink3

I also agree with @brodock on this. If someone wanted to set up their own hosted GitLab service with limits on free accounts, removing the limit would hurt this objective.

By Administrator on 2013-01-31T14:47:25 (imported from GitLab)

Created by: vsizov

Lets keep it as is :-)

By Administrator on 2013-02-02T11:49:42 (imported from GitLab)

Created by: babs

May I suggest:

• project limit = 0, none allowed
• project limit > 0, user can create up to X
• project limit = -1, no limit

By Administrator on 2014-12-03T12:06:10 (imported from GitLab)

Created by: litui

I realize this is closed but I also find this bothersome. I support -1 for no limit if ever this is revisited.

By Administrator on 2014-12-29T19:28:06 (imported from GitLab)

Created by: ianmartorell

Why was this closed? Has it been implemented?

By Administrator on 2015-03-09T10:16:08 (imported from GitLab)

Created by: dzaporozhets

We decided not to do boolean flag only because project limit counter is important for organizations like University when you want your students to create limited amount of project. THaths why the issue was closed - because idea was declined

By Administrator on 2015-03-09T16:09:30 (imported from GitLab)

Created by: ianmartorell

Obviously, I don't think the limit count should be removed either, but many people suggested here what looks to me like the most sensible solution:

project limit = 0, none allowed
project limit > 0, user can create up to X
project limit = -1, no limit

This way you don't remove the limit counter but you also allow for unlimited number of projects.

By Administrator on 2015-03-09T16:11:49 (imported from GitLab)

Created by: babs

@randx my suggestion was to use -1 as unlimited, 0 as not allowed, any positive number as the limit, keeping both good sides (limit or not, keeping R/O).

By Administrator on 2015-03-09T16:13:15 (imported from GitLab)

Created by: dzaporozhets

Why was this closed? Obviously, I don't think the limit count should be removed either

@ianmartorell thats why I closed it

I am not sure how to represent -1 value in UI but idea makes sense. If you want to extend current project limit functionality - please submit Pull Request or create feedback item at http://feedback.gitlab.com/forums/176466-general.

By Administrator on 2015-03-09T16:25:52 (imported from GitLab)

Created by: babs

Maybe using a hint like text, under the field, like the "* required" text ? maximum project(s) allowed (-1 for unlimited)

By Administrator on 2015-03-09T16:40:24 (imported from GitLab)