[chetanahuja]

One of the biggest weaknesses of gitlab, that becomes glaring as you add more and more projects, is that a code repository and a project are considered one and the same thing. It's quite common to want two or more separate repositories for an actual development project (e.g. frontend/backend or client/server etc.).

Of course gitlab's problems arise from the fact that their whole reason for existence is being an open-source copy of github. (And github is designed first and foremost as a public facing opensource management tool... which forces a lot of their product design choices).

Does phabricator work on a different paradigm that's more conducive as an internal tool to manage dev projects for a single organization?

[lima]

Yes, that's exactly how Phabricator works.

Issues, project management and repositories are fully decoupled.

Instead of copying GitHub with all its flaws, Phabricator was built from scratch for the enterprise usecase.

[prh8]

BTW, Gitlab is working on big improvements to organization wide features. This was discussed on here after their big release last month.