3 ms·

Is there any resource somewhere explaining why they migrated away from gitolite ? Not trying to sound negative, I'm just interested in the reasoning behind and

by rakoo 6y ago

Is there any resource somewhere explaining why they migrated away from gitolite ? Not trying to sound negative, I'm just interested in the reasoning behind and see what really differentiates the two in this kind of usage.

jamesu 6y ago
Following on from this, why didn't they use, say, gogs/gitea?
- input_sh 6y ago
  Took a quick look into their GitLab account and they seem to use some continuous integration, which is a native GitLab feature. Gitea does integrate with some external CI/CD services, but it's not a part of the core product: https://docs.gitea.io/en-us/ci-cd/ https://docs.gitea.io/en-us/ci-cd/. Gogs makes no mention of CI/CD in its documentation. I've switched from Gitea to GitLab for that same reason for my personal projects, and I'd bet that's by far the largest selling point of GitLab when compared to other self-hosted solutions. You just do a "git push" and stuff gets automatically tested in a VM or even deployed in a live environment.
  - ViViDboarder 6y ago
    > You just do a "git push" and stuff gets automatically tested in a VM or even deployed in a live environment. Yea, same with my Gitea + Drone servers. It’s cool that GitLab has everything built in, but I don’t mind having distinct tools. Especially when both are very performance static binaries in a language I’m fond of working in (Golang) so that I can patch upstream. Truth be told, if it weren’t for GitLabs sluggishness on my very cheap VPS, I’d probably give it more of a go so I’d have less to maintain.
bsdubernerd 6y ago
My first hot guess would be: "issues". Gitolite is just managing raw git repositories. I'm using gitolite for personal (read: non-public) projects, and I wouldn't want to use anything else. I love how minimal it is, and the way it works. However, how do you manage issues? Bugzilla is, IMHO, horrible. You can replace it with something much more lean, such as Mantis, but you still lack true integration with the repository (ie: knowing when a bug has been closed and which versions/branches it was dealt with). This is something I struggle with even when working alone on a simple project. I've used both sd (simple defects) and bugs-everywhere, however it seems that development on these has pretty much stalled, which is A Great Shame. I keep using "be" in these cases. However as soon as you have 2-3 devs, it's easier to fire up something like gitlab and have all features such as reviews/CI in a single shot than having to setup these separately.
- buovjaga 6y ago
  Bugzilla is still superior to GitLab/-Hub style issues, at least for bigger projects. Especially regarding search queries. Saying this from experience working in LibreOffice QA. Sadly upstream Bugzilla has been deprived of all the Mozilla-developed goodness for years, but finally the harmonisation is being wrapped up: https://dylan.hardison.net/2020/02/09/bugzilla-project-updates-2020/ https://dylan.hardison.net/2020/02/09/bugzilla-project-updat...
  - bsdubernerd 6y ago
    I'm pretty fond of Mantis, as mentioned, but I've seen effective usage of both github/lab issues with good usage of labels and a little bit automation. Since much more automation is required to integrate even a lean bugtracker into your source, I cannot recommend using a separate bugtracker unless you have an extremely good reason for it. Factor in that ease of reporting both for you and for your users should be in the top #3 reasons for using a specific bug tracker. Bugzilla IMHO only works as an internal-only tracker for developers or testers directly involved with the code and decent overview/discipline of the triaging process.
- rakoo 6y ago
  "Issues" is a very good reason for switching, it's very nice to be able to link them and code directly. I know Gitlab also offers easy CI/CD, but I don't know what the workflow of Xfce is so I don't know if they would benefit from it.
gitolite 6y ago
Gitolite author here. Indeed, gitolite doesn't support anything except permissions on raw git repos, plus all the customisation features you may have seen in the docs. There are plenty of good tools if you need issues, reviews, comments, etc.; no need for little old me to jump in there! In fact, at one time I changed the topic of #gitolite on freenode to "Social coding. Without the social" :-)

by rakoo 6y ago

jamesu 6y ago

Following on from this, why didn't they use, say, gogs/gitea?

input_sh 6y ago
Took a quick look into their GitLab account and they seem to use some continuous integration, which is a native GitLab feature. Gitea does integrate with some external CI/CD services, but it's not a part of the core product: https://docs.gitea.io/en-us/ci-cd/ https://docs.gitea.io/en-us/ci-cd/. Gogs makes no mention of CI/CD in its documentation. I've switched from Gitea to GitLab for that same reason for my personal projects, and I'd bet that's by far the largest selling point of GitLab when compared to other self-hosted solutions. You just do a "git push" and stuff gets automatically tested in a VM or even deployed in a live environment.
- ViViDboarder 6y ago
  > You just do a "git push" and stuff gets automatically tested in a VM or even deployed in a live environment. Yea, same with my Gitea + Drone servers. It’s cool that GitLab has everything built in, but I don’t mind having distinct tools. Especially when both are very performance static binaries in a language I’m fond of working in (Golang) so that I can patch upstream. Truth be told, if it weren’t for GitLabs sluggishness on my very cheap VPS, I’d probably give it more of a go so I’d have less to maintain.

bsdubernerd 6y ago

My first hot guess would be: "issues". Gitolite is just managing raw git repositories. I'm using gitolite for personal (read: non-public) projects, and I wouldn't want to use anything else. I love how minimal it is, and the way it works. However, how do you manage issues? Bugzilla is, IMHO, horrible. You can replace it with something much more lean, such as Mantis, but you still lack true integration with the repository (ie: knowing when a bug has been closed and which versions/branches it was dealt with). This is something I struggle with even when working alone on a simple project. I've used both sd (simple defects) and bugs-everywhere, however it seems that development on these has pretty much stalled, which is A Great Shame. I keep using "be" in these cases. However as soon as you have 2-3 devs, it's easier to fire up something like gitlab and have all features such as reviews/CI in a single shot than having to setup these separately.

buovjaga 6y ago
Bugzilla is still superior to GitLab/-Hub style issues, at least for bigger projects. Especially regarding search queries. Saying this from experience working in LibreOffice QA. Sadly upstream Bugzilla has been deprived of all the Mozilla-developed goodness for years, but finally the harmonisation is being wrapped up: https://dylan.hardison.net/2020/02/09/bugzilla-project-updates-2020/ https://dylan.hardison.net/2020/02/09/bugzilla-project-updat...
- bsdubernerd 6y ago
  I'm pretty fond of Mantis, as mentioned, but I've seen effective usage of both github/lab issues with good usage of labels and a little bit automation. Since much more automation is required to integrate even a lean bugtracker into your source, I cannot recommend using a separate bugtracker unless you have an extremely good reason for it. Factor in that ease of reporting both for you and for your users should be in the top #3 reasons for using a specific bug tracker. Bugzilla IMHO only works as an internal-only tracker for developers or testers directly involved with the code and decent overview/discipline of the triaging process.
rakoo 6y ago
"Issues" is a very good reason for switching, it's very nice to be able to link them and code directly. I know Gitlab also offers easy CI/CD, but I don't know what the workflow of Xfce is so I don't know if they would benefit from it.

gitolite 6y ago

Gitolite author here. Indeed, gitolite doesn't support anything except permissions on raw git repos, plus all the customisation features you may have seen in the docs. There are plenty of good tools if you need issues, reviews, comments, etc.; no need for little old me to jump in there! In fact, at one time I changed the topic of #gitolite on freenode to "Social coding. Without the social" :-)