I'm stuck with TFS here, which is a PITA and broken on so many levels, it's not even funny. Running a GitLab front would solve nearly all of my problems while still complying with the dreaded "everything in TFS" policy. :/
Choose GitLab for your next open source project
151–160 of 289 posts
Re: Choose GitLab for your next open source project
#152Earlier quoted context omitted.
I'm patiently waiting for you all to decide to focus your main interest on making gitlab.com the best place to host open source projects, while the GitLab EE/on premise stuff turns into a quiet side gig that just happens to bring in some extra cash. Any chance of that happening soon? To rephrase: There are folks willing to give you cash right now to be the host for their projects. Would there be a way to convince you…
Thanks for your question! We are trying to make GitLab.com the best place to host open source projects, see https://about.gitlab.com/strategy/ We do not think that paying for hosting itself makes sense, see https://about.gitlab.com/gitlab-com/#why-gitlab-com-will-be-... Instead of giving cash to use I would encourage people to move their projects and contribute by adding the features they need or helping our people,…
I recently started to mirror my repositories between GitHub and GitLab (they're just really small R packages).
It was very simple to update my local git config file so that "git push origin master" now pushes changes to both GitHub and GitLab.
I've also made it clear in the README how to install from GitLab.
Three minor annoyances:
* GitLab doesn't support Rmarkdown in .Rmd files, so my vignettes look great on GitHub, but not GitLab.
* I wanted to start an R Group (and did so), where people could share their R related projects all in one place. Unfortunately, as the projects are only shared with the group, they don't display when publically looking at the group if not signed in.The group image is also broken. [0]
* Relative links don't quite work the same, so some README links still only point to GitHub, as they were broken on the GitLab mirror. (Might just be user error!)
I also have a self-hosted installation running for a couple of private projects. It's on a small DO instance and does thrash resources a little, but generally works fine for two developers.
Thanks for such a useful product!
Re: Choose GitLab for your next open source project
#153Earlier quoted context omitted.
Thanks Alex for posting this. I'm so glad you had a positive experience upgrading. We spend a lot of time making our Omnibus packages a flawless install and upgrade experience. Docker images are great but for many users Docker is not an option. GitLab CE is just as performant and easy to upgrade as EE and we strive to keep it that way https://about.gitlab.com/about/#stewardship Currently our team member Axil is upgra…
Ubuntu 15.10 complains about the bad quality of the package. Is it ok to ignore it and install? Lintian check results for /home/algo/Descargas/gitlab-ce_8.4.4-ce.0_amd64.deb: E: gitlab-ce: maintainer-address-missing GitLab B.V.
Re: Choose GitLab for your next open source project
#154Re: Choose GitLab for your next open source project
#155I don't know, Gitlab seems a little too enterprisey for me. For example their documentation is too 'serious' they link to martin fowler's wiki for "feature branch" and wikipedia for "feature driven development". Their gitlab flow has waterflow development like production branch with things going to "production".I do oss for fun, not to go to another job after the first one. They don't have the cool hipster vibe that…
Re: Choose GitLab for your next open source project
#156I don't know, Gitlab seems a little too enterprisey for me. For example their documentation is too 'serious' they link to martin fowler's wiki for "feature branch" and wikipedia for "feature driven development". Their gitlab flow has waterflow development like production branch with things going to "production".I do oss for fun, not to go to another job after the first one. They don't have the cool hipster vibe that…
It has more features than Gitlab, anyway.
Re: Choose GitLab for your next open source project
#157Earlier quoted context omitted.
I agree that this has been a very positive effect. On the other hand forcing people to make code public when they might not want to might lead to problems when people are haunted by code they didn't intent to be read by others.
Nobody is forcing anybody to make their code public. It's their choice. You can have your code on your machine and on your servers only. Hosting your code is an option.
Re: Choose GitLab for your next open source project
#158Re: Choose GitLab for your next open source project
#159Exist something like this but for mercurial (I use BitBucket. I mean something to download private...)