5 ms·
I agree that putting projects under repositories looks counterintuitive. In BitBucket you have multiple repositories under one project https://confluence.atlass
by sytse 10y ago
I agree that putting projects under repositories looks counterintuitive. In BitBucket you have multiple repositories under one project https://confluence.atlassian.com/bitbucket/projects-792497956.html https://confluence.atlassian.com/bitbucket/projects-79249795...
We at GitLab are trying to keep it simple by having only one repository, one wiki, one issue tracker, one CD pipeline, and one set of milestones per project. Projects always below to a group. We aggregate on the group level, for example issues https://gitlab.com/groups/gitlab-org/issues https://gitlab.com/groups/gitlab-org/issues, merge requests https://gitlab.com/groups/gitlab-org/merge_requests https://gitlab.com/groups/gitlab-org/merge_requests and milestones https://docs.gitlab.com/ce/workflow/milestones.html#groups-and-milestones https://docs.gitlab.com/ce/workflow/milestones.html#groups-a...
There are several things we're still considering to solve this problem better, comments are very welcome:
1. Multi project pipelines https://gitlab.com/gitlab-org/gitlab-ce/issues/17069 https://gitlab.com/gitlab-org/gitlab-ce/issues/17069
2. Group level issue boards https://gitlab.com/gitlab-org/gitlab-ee/issues/928 https://gitlab.com/gitlab-org/gitlab-ee/issues/928
3. Nested groups https://gitlab.com/gitlab-org/gitlab-ce/issues/2772 https://gitlab.com/gitlab-org/gitlab-ce/issues/2772
- bhldr 10y agoEnough with the ads here.
- luan42 10y ago"Gitlab CEO here"
- tyre 10y agoMeta-comment: As a founder and engineer, I used to give a lot of shit to Social Media as a growth channel. GitLab staff are "on point" by commenting on anything relevant to their industry (code creation/management) where their target customers are (HN). To other founders, this is what good marketing looks like.
- sytse 10y agoThanks Chris. It is a tricky balance not being too noisy (I understand the sentiment of https://news.ycombinator.com/item?id=12502468 https://news.ycombinator.com/item?id=12502468 ) but I tried to add to the conversation by by sharing our thoughts about the project <=> repo dilemma.
- hitekker 10y agoA willingness to engage with the community as often and as effectively as you guys have is surely not commonplace. Hope you can keep it up! :)
- marklgr 10y agoI thought HN frowned on metacomments, and here it goes, talking about GitLab again, in a Github topic...
- dijit 10y agoI'm in no way affiliated with gitlab, but I do like the product. But the facts are such: 1) GitLab is a YCombinator incubated company. 2) GitLab and GitHub are direct competitors 3) It's almost always relevant to the discussion, in this case; "How could it be done differently, how /has/ it been done differently" In this case I think it's fair to bring up the direct comparison of github and gitlab. The only thing I would say could improve the situation was having github representation on here too.
- TeMPOraL 10y agoI enjoy threads like these; this is how healthy competition looks like. GitLab peoples' comments are relevant, and their discuss technical issues and merits of their solution, instead of comparing to GitHub ("we're better than the competitor!"). If this is how all marketing would always look like, I wouldn't hate it like I now do.
- deleted 10y ago[deleted]
- notatoad 10y ago> In BitBucket you have multiple repositories under one project however, unless i'm missing something, a "project" in bitbucket is basically just a folder to group your repositories in. there's no real features associated with it. A github project is project management tools based on a repository. If GitHub had called their feature something else, (for example, call it "the board") and nobody would be expecting it to be anything other than per-repo.
- jschumacher 10y agoThat's correct, right now projects in Bitbucket help to organise your repositories into projects. With the raise of microservices, it's quite common that a project or product is made up of many repositories. In the future you will see us adding more capabilities to projects, such as permission management [1] or settings on a project level, which already exist in Bitbucket Server. [1]https://confluence.atlassian.com/display/BitbucketServer/Using+project+permissions https://confluence.atlassian.com/display/BitbucketServer/Usi...
- w_t_payne 10y agoIt would be nice if there were a taxonomy of different organisational approaches so that we could have a common terminology to discuss the pros and cons of each. E.g. I come at things from the intersection of (embedded) product line engineering and continuous integration, which leads me towards a different place than somebody coming at things from (e.g.) consulting or web services ... but it is difficult to have a meaningful discussion about the pros & cons of each approach without the language / terminology that we need.