GitLab claims the policy helps keep its finances sustainable and is scheduled to go into effect in September 2022.
Given the potential backlash, GitLab issued weeks to months of early warning in order to archive the code developers depended on before it disappeared.
Even so, given that much of the code is widely used by open source projects, everyone is very worried about the huge negative impact of GitLab’s new policy.
Open source advocate and open .NET community participant Geoff Huntley criticized – GitLab is in “absolute madness”.
The source code itself doesn’t take up much disk space, and deleting the code would mean a major blow to the community and destroy GitLab’s own brand reputation.
The reason people host project code on GitLab is to make it easier for the public to remix and reuse.
Even if there is no guarantee of subsequent migration to other platforms, it is an unwritten rule of the open source community to ensure that code is available and not easily removed.
During the period of prudence, it has sent an inquiry request to the maintainer. It can be seen that the community is very angry about this, and various compilation projects that depend on the deleted product code will be deeply affected.
In addition, Geoff Hubtley launched a bombardment of the so-called “inactive” criteria– After all, once the software is written and close to perfection, “inactive” does not mean that its vitality has decreased.
It is reported that GitLabfree planOffers 5GB of storage per month, 10GB of data transfer, 400 minutes of CI/CD access, and five users per namespace.
Previously, the platform has publicly announced that it will use the free tier as its tool for attracting customers and building loyalty.
The pricing model also states that the large user base enables better support for GitLab from third-party tools/APIs/integrations, which in turn drives the ecosystem and the platform’s market position.
Sadly, as GitLab pursues a cost-control program that “gently blocks the use of certain free products,” the platform is gradually veering away from its original aspirations.
existThe RegisterGitLab finally felt the surging public opinion after the report of the company triggered a huge public response.
Moved to more obscure wording for dumping inactive repos to slower object storage.