GitLab's `` plan to delete the project of the free account left for one year '' was pulled out and burned and immediately canceled



On August 4, 2022, it was reported on the Internet that ``GitLab, a Git repository hosting service, plans to automatically delete projects owned by free membership users that have been inactive for one year.'' Opposing voices followed. In response to this, GitLab announced a policy to store inactive projects for the long term on the following day.

GitLab plans to delete dormant projects from free accounts • The Register
https://www.theregister.com/2022/08/04/gitlab_data_retention_policy/

GitLab U-turns on deleting dormant projects after backlash • The Register
https://www.theregister.com/2022/08/05/gitlab_reverses_deletion_policy/

British IT news site The Register reported on August 4, ``GitLab plans to automatically delete projects owned by free membership users if they are inactive for one year.'' I was. The cost of projects targeted for removal by this plan reportedly accounted for up to a quarter of GitLab's overall hosting costs, and the change would cost GitLab $1 million a year. It is estimated that it may be possible to reduce the cost of

An official, who requested anonymity, told The Register that the new policy is expected to go into effect in September 2022. The Register also reached out to GitLab for comment, but GitLab did not respond.

Despite being neglected for more than a year, SNS has raised opposition to reports that the popular Git hosting service, along with GitHub, is planning to cut off free members. For example, one Twitter user warned, ``A lot of open source code that is not being actively developed could disappear if developers don't take action.''



Some people say, ``I was thinking about moving all 80 GitHub projects to GitLab,'' due to the backlash against GitHub's parent company, Microsoft.



Also, some people pointed out that 'good projects don't need constant revisions'.



Under these circumstances, GitLab said the day after The Register's report, ``We had an internal discussion about what to do with the non-working repositories.As a result, we decided to move the unused repositories to object storage. Although access is still possible after implementation, it will take a little longer to access if it has not been used for a long time.'



According to The Register, unlike GitLab's announcement, the notice sent by GitLab to employees about the internal meeting on August 9 said that 'the deletion of the code repository was the agenda'. Also, regarding the content of the meeting, 'After September 22nd, we plan to roll out a 'Data Retention Policy for Free Users'. This sub-program will allow free projects to remain inactive for a month. We plan to limit the number and automatically delete the project and data.'

In addition, it seems that there was also an exchange confirming that 'automation code for deleting inactive projects' was completed at the end of July and was ready to be rolled out after discussion and development work.

An official who provided information to The Register testified that 'GitLab was forced to reconsider because of the online pressure caused by The Register's coverage.'

The announcement of moving repositories to object storage rather than deleting them was welcomed by users, but has sparked another debate. Simon Willison, developer of open source software Datasette , said, ``If only the owner can restore the archived code from the object storage, it will be 1 after the maintainer, the project owner, dies and the activity on the site ceases. The code can become inaccessible after a year, but is that a consideration?' I asked.

Related Posts:

in Web Service, Posted by log1l_ks