john_cogs

Some but not all parts of the dashboard are working.

Update: our team recently identified an issue impacting how we calculate storage which results in forks being counted towards Usage Quota. This will be addressed before we begin enforcement.

The phased enforcement of the limits are a part of the technical rollout plan for this change that was added to our docs. Related comment: https://news.ycombinator.com/item?id=32387597.

The communication sent to impacted users via email and future in-app notifications includes only the applicable enforcement dates and limits.

Issue to follow: https://gitlab.com/gitlab-org/gitlab/-/issues/368150

GitLab team member here. Thanks for the comment.

We understand people don’t want their quotas being filled by something outside of their control. For Open Source projects, we have GitLab for Open Source which contains higher limits from the Ultimate tier (250GB Storage, 500GB transfer/month). In addition, we intend to look into other ways to address your concern such as counting only your own traffic or allowing you to limit external traffic.

Hi, GitLab team member here. The GitLab for Open Source program provides open source projects with Ultimate benefits and higher limits. More info in previous comment: https://news.ycombinator.com/item?id=32387621

You are correct in your assumption - the storage limit impacts SaaS only. I added some context on the rollout in a previous comment. https://news.ycombinator.com/item?id=32387597

GitLab team member here. Forks of projects get deduplicated, so only the changes you make will contribute to your storage consumption as long as the fork relationship is maintained.

Hi there, in another reply I mentioned GitLab for Open Source provides Ultimate features and higher limits to Open Source projects for free: https://news.ycombinator.com/item?id=32387621

GitLab for Open Source provides OSS projects with Ultimate tier benefits, and includes 250GB of storage and 500GB transfer/month. Please apply to join the program here: https://about.gitlab.com/solutions/open-source/

No, 45,000GB wasn’t a quota. At the moment, the 5GB limit is a soft limit, and the rollout plan included tiered enforcement. This is an internal implementation detail of our technical rollout plan.

GitLab team member here. GitLab offers additional storage for $60/year for an additional 10GB of storage and 20GB of transfer/month.

Yes, the container registry and build artifacts are now correctly displayed in the free plans.

Yes, the container registry and build artifacts are now measured for Free users.

GitLab team member here. The impacted users are notified via email and in-app notifications will begin 2022-08-22, so far we've contacted 30,000 users. Only GitLab SaaS users are impacted - the limits are not applicable to self-managed users.

In many places, the plumbing might not be equipped for two-ply.

GitLab team member here.

You can see a feature comparison for the different GitLab tiers including our free tier here: https://about.gitlab.com/pricing/gitlab-com/feature-comparis...

You will also notice the tiers for which a feature is available are listed on the docs page for that feature.

GitLab team member here. Thanks for flagging. I contacted the owner of the dashboard and asked if they can get it working. Will report back if/when it is repaired.

GitLab team member here.

Nanoc (https://nanoc.app/) is the static site generator we use for our docs.

More info: https://docs.gitlab.com/ee/development/documentation/site_ar...

GitLab team member here. Sid addressed GitLab's use of Go in a comment on a previous discussion of this article from last week: https://news.ycombinator.com/item?id=31687289

He wrote: "We're moving the 20% of the app consuming 80% of the compute to Go."

His comment also highlights another benefit of the way our core services are structured: reusability.

GitLab team member here.

We are all-remote with hundreds of employees as you noted.

You can read more about how things work at GitLab via our handbook and our all-remote guide:

- https://about.gitlab.com/handbook/

- https://about.gitlab.com/company/culture/all-remote/

GitLab team member here. Thanks for the feedback.

It would be great if you could share your insights and feedback on the public epic for the strategy for remote development: https://gitlab.com/groups/gitlab-org/-/epics/7419

GitLab team member here.

We have considered Theia in the past. Here are a couple of related epics/issues:

- https://gitlab.com/groups/gitlab-org/-/epics/1619

- https://gitlab.com/gitlab-org/gitlab-foss/-/issues/56812

I worked at Lehman Brothers from 2005-2008. Traded equities on a floor with ~500 other traders/sales traders. It was a formative experience.

GitLab team member here.

In GitLab, the best way to view a summary of your jobs is the pipeline details page. This page provides a clear overview of each job including status and allows for jobs to be grouped by both stage and dependencies for easier review.

Hey, I’m on the Community Relations team at GitLab. Thanks for your contributions and the kind words. I would love to connect and learn more about your experience contributing to GitLab. You can reach me at jcoghlan at gitlab com.

I was playing golf on Sunday and a player in a nearby group made a hole-in-one. Everyone at the course got a free drink that day. I later found out that the club had insurance. Funny to see this on the HN front page a couple of days later.

GitLab has documented how to still be a startup after IPO: https://about.gitlab.com/company/still-a-startup/

I'm not aware of any plans for a GitLab x Yerbo integration right now but that's a really interesting proposal.

GitLab team member here.

While this blog post looks at what managers can do, we've also recently started using Yerbo (Slack app) internally to help individuals to assess their own risk of burnout. See: https://about.gitlab.com/handbook/communication/#yerbo-slack...

Mental health and well-being is always a concern at GitLab (ex: the Friends and Family days that we implemented and maintained throughout the pandemic to ensure team members are taking time off). This month, however, we've been adding additional focus to the topic as May is Mental Health Awareness month.

If you check out the post, you can see/read how it is a play on an infinity loop.