Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
support
-
Announcing Fox Ear 0.1.0
Not OP but strace gives you a ton of info even if you filter by syscalls with -e. You really need something like https://gitlab.com/gitlab-com/support/toolbox/strace-parser to get information like what this seems to provide out of it.
-
Gitlab Handbook's HN Page
Hi @atonse - I'm a Senior Manager at GitLab Support. I appreciate you taking the time to put together your feedback. I'm happy to discuss the particularities of your support experience if you send me an email at lkozloff[at]gitlab.com
There's a couple of general points though that I'd love to comment on.
> Why can't I just SSO using my GitLab credentials into Zendesk?
I'd love to have this as well - it makes complete sense (especially for our SaaS customers - it wouldn't help as much for self-managed). In order to get it implemented we need GitLab.com to become a SAML or JSON Web Token source. We have an open feature request for that here: https://gitlab.com/gitlab-org/gitlab/-/issues/238419
Even with that implemented we'd still have some challenges identifying who should be getting support without occasionally asking for proof of a support contract. As you said, you're part of multiple GitLab groups. It's well possible that some of those are on our Free tier and others on Paid tiers. In some contexts you'd be eligible for Support, and in others you might not be.
Usually this speed bump only hits the first time you contact support. Once you've opened a ticket we'll have you linked up correctly.
Recently I've been working on improving contact management and making sure customers are aware of what they can do to make their first support ticket the best experience it can be. You can track that effort in https://gitlab.com/groups/gitlab-com/support/-/epics/156
> Why use terms like "Support Entitlement" – just say, which org/group are you with?
We have to consider both our self-managed customers and SaaS customers with our language. For GitLab.com customers naming a path completely works (and is one of the ways you can prove your entitlement: https://about.gitlab.com/support/managing-support-contacts.h...). For Self-managed we have to map account names exactly and need a bit more as some organizations have visibility of tickets between users, in which there may be sensitive data.
I think you're right that it could sound more human. I've opened up https://gitlab.com/gitlab-com/support/support-team-meta/-/is... to discuss improvements.
If you have any thoughts, feel free to participate!
-
(Telemetry) Pseudonymization Feedback and Question
Full disclosure, I have some rather strong feelings about telemetry on gitlab and the implementation process itself.
-----------------------
I originally posted a different issue labeled "Pseudonymization MVC Rollout Plan"[1] but that issue went private rather quickly after appearing here. Sadly it wasn't archived.
To keep this issue from just going private, it (and some other relevant issues) have been archived: http://web.archive.org/web/20211012193943/https://gitlab.com...
There is atleast one more telemetry related issue that[2] has had their access limited after being mentioned in the feedback thread.
Also, I'd recommend checking out:
* the last telemetry attempt from 2019: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/5672
* feedback from last time: https://gitlab.com/gitlab-com/support/support-team-meta/-/is... & https://gitlab.com/groups/gitlab-org/-/epics/2280
* self-hosted instance telemetry(operational data section) that is already live and has a pretty severe dark pattern for opting out: https://about.gitlab.com/blog/2021/07/20/improved-billing-an...
[1] - https://news.ycombinator.com/item?id=28840685
-
Wanna Learn Gitlab CI
Training used for support personnel: https://gitlab.com/gitlab-com/support/support-training/-/tree/master/.gitlab/issue_templates
gitlab
-
Gitlab Duo
Since the relevant code appears to be in the "ee" directory <https://gitlab.com/gitlab-org/gitlab/-/blob/v16.11.0-ee/ee/l...> and is not present in the foss repo, I'm guessing the answer is no, at least for now. They do have a history of "releasing" features from EE back to CE but my suspicion is not for LLM stuff
- Code Search Is Hard
- XZ Backdoor Investigation Request to Gitlab Team
-
Client side Git hooks 101
(Side note: Issues are usually hash-prefixed like #1234 both on GitLab and GitHub. However, commit messages must not begin with a hash, they would be considered a comment and ignored. Therefore, GitHub has introduced the alternative prefix GH- and I've contributed a similar prefix GL- to GitLab a while ago.)
- Assign Issue to an AI Developer
-
BuildKit in depth: Docker's build engine explained
and its "oh, you want multi-arch, do you?" friend. While prosecuting this <https://gitlab.com/gitlab-org/gitlab/-/issues/339567> I learned that https://hub.docker.com/layers/multiarch/qemu-user-static/7.2... actually mutates the binfmt_misc in buildx's context in order to exec the static copy of qemu in it https://github.com/multiarch/qemu-user-static/blob/v7.2.0-1/...
and, that the buildx plugin itself has some qemu magick in it, which got addressed in a minor version bump but I couldn't track down the relevant GitHub issue this second (I've flushed it from my mind, only recalling that there were a lot of actors in that tire fire)
-
Gitlab password reset bug leaves more than 5.3K servers up for grabs
This is actually a follow-up refactor, the fix is here: https://gitlab.com/gitlab-org/gitlab/-/commit/abe79e4ec43798...
- ExifTool CVE-2021-22204 – Arbitrary Code Execution
- Critical Gitlab vulnerability exposes 2FA-less users to account takeovers
- Upcoming critical Gitlab security issue
What are some alternatives?
www-gitlab-com
Gitea - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
marketing
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
tech-evangelism
onedev - Git Server with CI/CD, Kanban, and Packages. Seamless integration. Unparalleled experience.
uxr_insights
rich-markdown-editor - The open source React and Prosemirror based markdown editor that powers Outline. Want to try it out? Create an account:
foxear - Fox Ear is a Linux process behavior trace tool powered by eBPF.
gitlab-foss
chatwoot - Open-source live-chat, email support, omni-channel desk. An alternative to Intercom, Zendesk, Salesforce Service Cloud etc. 🔥💬
Gitbucket - A Git platform powered by Scala with easy installation, high extensibility & GitHub API compatibility