271–280 of 289 posts
Earlier quoted context omitted.
Glad to hear you're happy with your self-hosted instance.We're working on single user subscriptions (before either 8.5 or 8.6), our license key doesn't call home and our license will stay proprietary but already allows for modification and publishing patches.
Allowing your customers to publish their patches is super cool :-)
Earlier quoted context omitted.
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,…
One thing that more recent code hosting sites miss out is mailing list hosting, for less structured discussions between users and developers, or for providing a private group contact address for the developers.
Earlier quoted context omitted.
When you create a repository you have the option of importing it from GitHub. You'll have to authorize it to access your GitHub repositories, but then it can pull over all of the issues that are part of the project.
The issues are public though, why does it need my authorization?
Earlier quoted context omitted.
Feature request - allow performance tracking over time allowing these kind of views to be available in gitlab - https://arewefastyet.com/ . One possible workflow - 1. User defines perf metrics in some metadata file in repo. 2. User checks in data for metrics with every commit. 3. Gitlab shows a view of the metrics changing over time.
We totally want to do this with GitLab CI. Right now you can have GitLab CI measure your code coverage, see https://gitlab.com/gitlab-org/gitlab-ci/commit/96b17c1735b65... for an example. We can just add a graph and allow people to add more metrics https://gitlab.com/gitlab-org/gitlab-ce/issues/13409 Obviously you should ensure that your performance tests are run on the same type of machine every time. But you can do…
Earlier quoted context omitted.
We totally want to do this with GitLab CI. Right now you can have GitLab CI measure your code coverage, see https://gitlab.com/gitlab-org/gitlab-ci/commit/96b17c1735b65... for an example. We can just add a graph and allow people to add more metrics https://gitlab.com/gitlab-org/gitlab-ce/issues/13409 Obviously you should ensure that your performance tests are run on the same type of machine every time. But you can do…
Thanks for opening the ticket, I have added some comments that capture my use cases to the ticket.
Earlier quoted context omitted.
Basically I just don't like some "features" which are anti-patterns IMHO: * With SPA I mean that clicking on a link, my browser doesn't load a new page, but rather some JavaScript seems to do it. * Depending on the browser width, the description of the icons on the left disappears. It should always be there, I'd rather have a horizontal scrollbar than not knowing which button does what. * Fixed headers. Vertical scre…
1. What is the problem with this? Back links and everything else should still work. And it saves a lot of time. 2. I agree the user should be able to override and made https://gitlab.com/gitlab-org/gitlab-ce/issues/13436 3. Where do we do this? 4. I don't think infinite scrolling is always bad. 5. What do you suggest we do instead? PNG's for all icons are expensive to load.
3. Do you mean the animation? You don't do this yet.
5. SVGs
Earlier quoted context omitted.
1. What is the problem with this? Back links and everything else should still work. And it saves a lot of time. 2. I agree the user should be able to override and made https://gitlab.com/gitlab-org/gitlab-ce/issues/13436 3. Where do we do this? 4. I don't think infinite scrolling is always bad. 5. What do you suggest we do instead? PNG's for all icons are expensive to load.
1. No, "everything else" doesn't still work. You're reimplementing a browser in JavaScript! For example: There's no spinning loading indication on the left side of my tab. When clicking on a link and pressing back while it's loading, it doesn't abort, but goes back instead. 3. Do you mean the animation? You don't do this yet. 5. SVGs
1. I agree that these browser functions are broken. I think the speedup is worth it but that is personal. BTW Turbolinks are a default feature of modern rails apps, doesn't mean they are right but they are common.
3. We don't plan to do this either as far as I'm aware.
5. Icons in SVG would be nicer but that looks like a lot of work.
Earlier quoted context omitted.
1. No, "everything else" doesn't still work. You're reimplementing a browser in JavaScript! For example: There's no spinning loading indication on the left side of my tab. When clicking on a link and pressing back while it's loading, it doesn't abort, but goes back instead. 3. Do you mean the animation? You don't do this yet. 5. SVGs
Thanks for your feedback. 1. I agree that these browser functions are broken. I think the speedup is worth it but that is personal. BTW Turbolinks are a default feature of modern rails apps, doesn't mean they are right but they are common. 3. We don't plan to do this either as far as I'm aware. 5. Icons in SVG would be nicer but that looks like a lot of work.
I have to say: Gitlab's support seems to be top-notch. I'm sorry for being a bit harsh and thanks for the kind response! :)
Earlier quoted context omitted.
Thanks for your feedback. 1. I agree that these browser functions are broken. I think the speedup is worth it but that is personal. BTW Turbolinks are a default feature of modern rails apps, doesn't mean they are right but they are common. 3. We don't plan to do this either as far as I'm aware. 5. Icons in SVG would be nicer but that looks like a lot of work.
I see. I have to say: Gitlab's support seems to be top-notch. I'm sorry for being a bit harsh and thanks for the kind response! :)
To add to sytses:
- We're introducing some more pagination over infinite scrolling. If we see this is successful, we might continue that trend - eventually we will replace the icons with svgs, probably when we switch to our inhouse icons. There is no due date for that, though.
Earlier quoted context omitted.
What are the high points of Phabricator? I'm reading the landing page, but the terribly self-deprecating style makes it hard to find the actual pain-point solutions buried within.
The best way to check out Phabricator is to go look around the Phabricator instance used by Phacility to manage the Phabricator project itself. https://secure.phabricator.org/ This gives has all their documentation, applications, and handy nearby search to find answers to the questions you may be thinking about while checking out each application.