The release post has been published and can be found here: https://about.gitlab.com/releases/2023/05/05/critical-securi...
991 karma · joined March 1, 2015
The release post has been published and can be found here: https://about.gitlab.com/releases/2023/05/05/critical-securi...
0 - https://about.gitlab.com/blog/2023/05/03/gitlab-ai-assisted-...
[0] - https://about.gitlab.com/blog/2023/05/01/how-to-build-reusab...
Beautifying our UI [0] is an ongoing effort and usability improvements [1] are specifically mentioned in the product investment themes for this fiscal year.
0 - https://gitlab.com/groups/gitlab-org/-/epics/7781
1 - https://about.gitlab.com/direction/#world-class-devsecops-ex...
In our 15.10 release (March 22), we added a new section called Explore that helps with content discovery and includes a tab for Trending projects that can be filtered by language. You can read out it in the release notes [0] or just go check it out [1].
0 - https://about.gitlab.com/releases/2023/03/22/gitlab-15-10-re...
You can read more about our work on code suggestions here: https://about.gitlab.com/direction/modelops/ai_assisted/code...
We are looking at Zoekt for code search: https://gitlab.com/groups/gitlab-org/-/epics/9404
Our Code Search team is currently working on moving to Zoekt[0] which is expected to be a significant improvement as it is purpose-built for code search.
We also shipped an improvement[1] to our existing search functionality at the end of last year. If you haven't used it recently, I'd encourage you to check out code search again to see if the quality has been improved for you.
Thanks for the feedback.
I created a merge request to update our documentation based on your comment and linked to the comment in the MR description: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/107599
A link to the Epic for full project search[0] was shared in an earlier comment[1] by Eric, the Product Manager who is leading this effort. You can follow along there to track our progress.
In the meantime, you can disable the beta and continue to use the old Web IDE until all of the features you require are available[2].
[0] - https://news.ycombinator.com/item?id=34080388
[1] - https://gitlab.com/groups/gitlab-org/-/epics/9466
[2] - https://docs.gitlab.com/ee/user/project/web_ide_beta/index.h...
We released a beta version of our new Web IDE which is built using VS Code. The new Web IDE will provide users access to more features, improved performance, and the ability to securely connect to a remote development environment directly from the Web IDE.
There is more context in this blog post: https://about.gitlab.com/blog/2022/05/23/the-future-of-the-g...
The TLDR is that the Web IDE is a widely used feature (tens of millions of commits have been made using it) and building our new Web IDE with VS Code will allow us to invest in extending the experience to be more tightly integrated with GitLab and the DevOps workflow rather than re-creating VS Code features in our Web IDE.
While it's possible that it could have been 3 AM on Jan 1 in Sydney and midday on Dec 31 in the United States, I think anyone at GitLab, including the recruiter who made the call, would agree that the timing of this call was a mistake - even if the recruiter was within their working hours.
Those impacted are welcome to apply to the GitLab for Open Source program: https://about.gitlab.com/solutions/open-source/join/
I will follow up if/when I can provide more specificity but it might be Monday before I have any more information.
Edit: the notifications will appear as global alerts directly under the Nav for all group owners.
We intend to roll out the application of these limits gradually and impacted users will be notified in-app at least 60 days prior to the user limits being applied.
If you have not yet received a notification, you have at least 60 days until you will see any impact related to this change.
At GitLab, we have a clearly defined organizational structure. Within that stucture, we have Product Groups[0] which are groups of people aligned around a specific category. The name "Single-Engineer Groups" reflects that this single engineer owns the category which they're focusing on.
I'll be sure to surface your question to the leader of our Incubation Engineering org. Thanks.
[0] - https://about.gitlab.com/company/team/structure/#product-gro...
This work was produced by our AI Assist SEG (Single-Engineer Group)[0]. The engineer behind this feature recently uploaded a quick update about this work and other things they are working on to YouTube[1].
[0] - https://about.gitlab.com/handbook/engineering/incubation/ai-...
If you go to the pricing page[0] and click the “Buy GitLab <tier>” you’re interested in purchasing (Premium or Ultimate), a pop up will appear and you can purchase an on-prem license by clicking the “Purchase self-managed” button.
Storage limits will apply to both private and public namespaces.
If you are using the free tier on GitLab SaaS, there will be a 5GB storage limit per top-level namespace.
Paid tiers on GitLab SaaS will have limits of 50GB for Premium and 250GB for Ultimate.
Community programs (GitLab for Open Source, GitLab for Education, and GitLab for Startups) will have the same 250GB limit as the Ultimate tier.
Self-managed users have no limit.
You can see many of the open source projects of significance who are using GitLab here: https://about.gitlab.com/solutions/open-source/partners/
The requirements are:
- use an OSI-approved license
- not seeking profit
- be publicly visible
You are correct that in order for projects to be eligible they must not be seeking profit. This is listed as a requirement on the program page: https://about.gitlab.com/solutions/open-source/join/.
You can see many of the open source projects of significance who are part of the program here: https://about.gitlab.com/solutions/open-source/partners/