connorshea

I've been using Sorbet on a personal project (https://github.com/connorshea/vglist) for almost two years now, and it's been great (although I've had to build myself a lot of tooling for it over time).

I don't think I'll use the compiler (for now, at least), but I'm very interested in seeing how it grows over time :)

This makes me so happy, thank you! :D

As a user of the iOS app it used to have some admittedly frustrating problems, but pretty much every complaint I had previously has since been fixed, huge kudos on the progress you've made!

The only thing left that really bugs me is the fact that you can't paste images from the clipboard into the message field. It's made me change my entire workflow, from copying images to saving them.

Sorry to use this as a soapbox for my pet issue, but I saw the opportunity :P

The issue in question for anyone curious: https://gitlab.com/gitlab-org/gitlab-ce/issues/28996

I'm looking forward to it as well :)

Not OP but anything that makes the process smoother is good IMO :)

Libre/Starter/Premium/Ultimate are the names of plans for our distributions. CE and EE are distributions of GitLab. CE has _only_ FOSS code in it for users (e.g. self-hosting open source projects) who don’t want to run any proprietary code whatsoever. Libre features are any features that are in the CE distribution by default.

The Free/Bronze/Silver/Gold plans are for GitLab.com specifically (all open source projects get Gold features by default).

We also have an issue for running jobs only when modifications are made to a given file or files in a directory, it's tentatively scheduled for 10.7 (April's release).

https://gitlab.com/gitlab-org/gitlab-ce/issues/19232

Not Sid, but thanks for being a fan ;)

Mirroring is an Enterprise Edition feature but there are probably ways to hack around that.

We actively try to make improvements so GitLab uses fewer resources, but with the scope of the application it's definitely not easy to make it super "lightweight".

You can see the hardware requirements here: https://docs.gitlab.com/ce/install/requirements.html#hardwar...

There are no plans to migrate all of GitLab to Go. The main Rails app is going to stay a Rails app for the foreseeable future. There are a few reasons for this. For one it'd be such a huge project, but also Rails is working well for us, it's great for our pace of feature development.

We are working on moving the git layer to Gitaly[0] which is written in Go (and is what this blog post is about). It was one of our major bottlenecks and we've seen a lot of benefit from having made the switch. It's not done yet, but a lot of the calls to git that the application makes are now done through Gitaly.

[0]: https://gitlab.com/gitlab-org/gitaly

Hey, sorry about that. I just replied.

See our Stewardship page[0] for how we determine what goes in EE vs. CE, for now Burndown Charts will stay in EE. As for EBS, feel free to open an issue for it[1] since I couldn't find one :)

[0]: https://about.gitlab.com/stewardship/ [1]: https://gitlab.com/gitlab-org/gitlab-ee/issues

Thanks for the feedback, I looked into it and it looks like neither of these problems have been fixed as of yet. I've asked the CI and UX teams if we can work on the Environments page.

Here's the issue for the table size: https://gitlab.com/gitlab-org/gitlab-ce/issues/41594

For what it's worth, in the last year (since January 23, 2017) we've merged ~440 merge requests labeled "performance"[0]. It's not perfect right now and there's still plenty of work to do, but compared to when I started at GitLab almost two years ago it's night-and-day.

We've also got an entire team dedicated to porting our Git layer to Go with Gitaly[1], which has been a major bottleneck that we've started resolving over the last year or so.

[0]: https://gitlab.com/groups/gitlab-org/-/merge_requests?label_... [1]: https://gitlab.com/gitlab-org/gitaly

We do have support for macOS and Windows in Runner, though you'll have to run them yourselves. We're looking into offering hosted macOS and Windows Runners for the future, but we have no solid timeframe for those right now. https://gitlab.com/gitlab-com/infrastructure/issues/3183

I know you said you don't need them, but what features are we missing?

The current plan is to remove it in 11.0.0, if you know of anywhere this is unclear I can take a look and have it changed.

API v3 is still supported in the latest GitLab release (and will also be supported in this month's release, as well as probably the next few since we haven't decided the exact date of deprecation yet), have we communicated this incorrectly somewhere?

Thanks, the Omnibus team has worked incredibly hard over the years to make GitLab easy to install :)

Out of curiosity, is there anything we can do to make you a fan? What are we lacking?

When did you try GitLab, and was it self-hosted or GitLab.com? We've been working on improving performance, especially on GitLab.com, for the last two years now. Having started around then I can definitely say it was pretty miserable back then, but it's infinitely better now.

You can see our infrastructure issue tracker for more info on what we've worked on over the last few months and what we're doing now: https://gitlab.com/gitlab-com/infrastructure/issues

We have an issue for mailing lists in GitLab here[0] if you want to leave any comments, but it's not a particularly active issue and I'm not sure how likely we'd be to actually build this into the product. I'll update this comment if I find a more active/fleshed-out issue for the same functionality.

[0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/4272

We have repository mirroring available in GitLab Enterprise Edition Starter, and there exists an issue to move this to CE[0] but it was closed with some explanation as to why[1]. I assume with GitHub Sync you're asking for syncing of more than just the repository, but also issues and merge/pull requests?

The SourceForge sync tool appears to only include release syncing as far as I can tell (the wording is ambiguous and the docs only mention import, not active sync, so I'm not sure what they provide?).

For what it's worth, GitLab does have import tools in CE[2]. You can also use repository mirroring (along with any other Enterprise Edition features) if you're an open source project on GitLab.com.

[0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/18732 [1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/18732#note_47... [2]: https://docs.gitlab.com/ee/user/project/import/github.html

Based on the Debian Wiki, plans have since changed[0] (unless this page is outdated?). That LWN article is from June, the wiki article was last edited in September.

My understanding from the mailing list is that they're planning on using GitLab, at least that's what I heard last. I could always be wrong.

[0]: https://wiki.debian.org/Alioth#Deprecation_of_Alioth

Their infrastructure tracker has a lot of interesting info about the move[0]. You can also read through the development mailing list, it has a lot of discussion about the GitLab migration.

At GitLab we're tracking the blocking issues they've brought up in this issue[2].

[0]: https://gitlab.gnome.org/GNOME/Infrastructure/issues [1]: https://mail.gnome.org/archives/desktop-devel-list/ [2]: https://gitlab.com/gitlab-org/gitlab-ce/issues/35287

Could you link the issue so we can look into it?

Awesome news, now we can reconsider using GraphQL at GitLab! :) https://gitlab.com/gitlab-org/gitlab-ce/issues/34754#note_41...

Out of curiosity, does anyone know of any other specs licensed under OWFa?

My understanding was that the maintainer of Gogs had stopped replying to any issues/PRs for a period of a few weeks and refused to add any other maintainers to the project, so people wanted to fork and ensure that it'd always have an active maintainer.

https://blog.gitea.io/2016/12/welcome-to-gitea/

Yeah, we've been committed to improving performance and uptime on GitLab.com for over a year now, we've heard this feedback a lot and take it to heart. It's definitely been steadily improving, and we're working on getting downtime-less deploys as soon as possible.

You can see some of the issues tracked in our GitLab.com infrastructure issue tracker here: https://gitlab.com/gitlab-com/infrastructure/issues (for security reasons not everything is visible to outside users)

They don't load for me either, most likely a problem from when we rewrote most of the about.gitlab.com website last year. I'll look into it, I'm also interested to see what it looked like in 2012 :D

EDIT: It looks like the images are attempting to load from an old Wordpress blog which is no longer around, with a quick search I couldn't seem to find anything with similar file names in the current website repository :(