jobvandervoort

9 ms·

31.
by jobvandervoort 8y ago
Thanks gorset for the great response and the new insight you gave me into this. I now understand what you mean and see how the changes have negatively affect patch-series style MRs. I created an issue on this and I encourage you to contribu
32.
by jobvandervoort 8y ago
Cool feature. Makes total sense. Pinged the relevant people.
33.
by jobvandervoort 8y ago
Thanks for the feedback. To address each point: 1. I'd love to see everything versioned in GitLab. We're working on the issue descriptions, but I agree we should move toward versioning everything. There's an epic here [0], th
34.
by jobvandervoort 8y ago
I just checked, user Vinnl is correct that you can already do this for every commit, and targeting every branch.
35.
by jobvandervoort 8y ago
What is the output you get? Consider creating an issue here so we can help you debug: https://gitlab.com/gitlab-org/omnibus-gitlab/issues
36.
by jobvandervoort 8y ago
Thanks for the feedback gorset. I'm curious to dig a little deeper. With the irrelevant information, you mean the top part of the merge requests (ie description, CI status, etc)? And as far as I can see, in the current version, we only
37.
by jobvandervoort 8y ago
We got extensive feedback regarding the `Master` title. Renaming it to `Maintainer` is a relatively cheap thing to do, strengthened by the fact that it's a better reflection of the permission level: this is what Maintainers of repos wi
38.
by jobvandervoort 8y ago
Thanks for the feedback. To address some of it: Regarding batch review: We wanted to ship this way sooner. We spent an unfortunate amount of time refactoring our merge requests to use Vue. That is now done, so work on this has started and s
39.
by jobvandervoort 8y ago
We've not spent a lot of time on making this publicly readable, but the migration is moving forward steadily. We don't have a planned switchover data yet, but it's safe to say that it'll happen this summer. We're wr
40.
by jobvandervoort 8y ago
Not yet, but I think it makes sense to support VIM keybindings in the long term. Issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/47930
41.
by jobvandervoort 8y ago
August 22nd: https://gitlab.com/gitlab-org/gitlab-ce/issues/46334
42.
by jobvandervoort 8y ago
We called it IDE from the first commit, as we intend for it to be a full replacement of a local IDE in the future. Besides having a vision ourselves of that, we also want to encourage and motivate others to contribute.
43.
by jobvandervoort 8y ago
If you're not a software engineer, cloning, editing, staging, committing, pushing, creating a merge request is a lot to learn. I believe we can make this much easier, and that's the first problem we hope to solve with the Web IDE.
44.
by jobvandervoort 8y ago
If you push a new branch to a GitLab project, we return a URL to immediately create a merge requests, which appears in the Git output in your terminal. So rather than going to GitLab, then clicking on a button, you just click the link in yo
45.
by jobvandervoort 8y ago
GitLab is built on Ruby on Rails and a sprinkle of Go. We have no relation to Oracle.
46.
by jobvandervoort 8y ago
We currently run on Azure. GitLab integrates deeply with Kubernetes and specifically GKE, so it makes sense to run GitLab.com there: https://about.gitlab.com/2018/04/05/gke-gitlab-integration/
47.
by jobvandervoort 8y ago
I have not heard it mentioned by any user / customer / other community member in the last year, but I think it makes sense to support it.
48.
by jobvandervoort 8y ago
On GitLab: we do, but only if you host it yourself for now. See: https://news.ycombinator.com/item?id=17226432
49.
by jobvandervoort 8y ago
On the comparison with GitLab you mention we don't support IPv6. We do if you host your own. We will enable it for GitLab.com once we're done with the migration to GCP [0]. Our pricing is per user, tiered. Not per-user and then pe
50.
by jobvandervoort 8y ago
If you're moving from GitHub to GitLab, create an issue if one doesn't already exist [0] and send me a message (here, @JobV on GitLab.com, Twitter). I will make sure it ends up in the product. [0]: https://gitlab.com&#x
51.
by jobvandervoort 8y ago
If your project is public on GitLab.com, you can also mirror it for free to GitHub, bi-directional. Meaning you can receive contributions on both repos. Docs: https://docs.gitlab.com/ee/workflow/repository_mirrorin
52.
by jobvandervoort 8y ago
People told us the logo was scary, that was a good motivator. When we changed, I wrote about it: https://about.gitlab.com/2015/05/18/a-new-gitlab-logo/
53.
by jobvandervoort 8y ago
Exactly. Or at least teach them to use GitLab, which is a good motivator to make the product easy to use.
54.
by jobvandervoort 8y ago
Yes, everyone == every single person employed by GitLab Inc.
55.
by jobvandervoort 8y ago
Ours is here: about.gitlab.com/handbook - it's open source: gitlab.com/gitlab-com/www-gitlab-com/ My tips: 1. Maintain a clear single source of truth 2. Make sure everyone can contribute to it. We do this by requiri
56.
by jobvandervoort 9y ago
You can run GitLab yourself, for free. Or even just supply your runner on GitLab.com: the builds run on your own equipment, but you don't need to host your own GitLab instance.
57.
by jobvandervoort 9y ago
Is a world without Facebook one with a real alternative (everyone in the same place), or one where there are many alternatives? Reddit is a single platform with many mostly-independent communities. Could a similar thing in the shape of a so
58.
by jobvandervoort 9y ago
In short: 1. We mirror your project 2. We set up the integration with GitHub 3. We report the status and link back on GH's pull requests
59.
by jobvandervoort 9y ago
We don't have a lot of incentives to turn down contributions. Quite the opposite. We not only encourage this, we actively help people contributing to GitLab. It's humbling to be a steward to an open source project and something we
60.
by jobvandervoort 9y ago
So as landing page? That is an interesting idea. I've created an issue. Would love to get your thoughts there: https://gitlab.com/gitlab-org/gitlab-ce/issues/38954

More ›