gitlife.ru

Gitlife Inactive Account Policy

The personal/organization/enterprise space address (URL identifier, hereinafter referred to as "identifier," e.g., xxxx in https://gitlife.ru/xxxx) of a Gitlife account is unique across the system and provided to users on a first-come, first-served basis. Gitlife reserves the right to reclaim identifiers under the following two circumstances.

1. Inactive Accounts

Currently, Gitlife has some inactive accounts that occupy identifiers. To avoid resource waste, we provide a process for reclaiming identifiers from inactive accounts.

Definition of Inactive Accounts (must meet all conditions):

The account has had no activity (including code pushes, comments, private messages, follows, etc.) for 2 years.
The account has no repositories.

Handling of Inactive Accounts:

Only processed if another user requests the identifier (we will not proactively process inactive accounts).
Release the identifier occupied by the inactive account and assign the account a new system-generated identifier.
Send an email notification to the inactive account.
For accounts that do not meet the criteria, users may negotiate identifier usage independently.

2. Well-Known Brands and Trademarks

Since enterprises/organizations are important contributors to open source, to avoid individuals impersonating enterprises/organizations when publishing open-source projects or other information, which may cause misunderstandings, we provide a process for reclaiming identifiers related to well-known brands and trademarks.

The appealing party must be an enterprise/organization and provide sufficient evidence proving that the account identifier is directly related to its brand/trademark/patent, etc.

Handling of Appealed Accounts:

Only processed if an enterprise/organization requests the identifier (we will not proactively process).
If the appealed account meets the "Inactive Account" definition, it will be handled as an inactive account.
If the appealed account is not "inactive," the system will send an email/SMS notification to the account owner regarding the reclamation and handling process.
Without affecting normal usage, release the identifier occupied by the appealed account and assign a new system-generated identifier (the user may change it once later, with no impact on data).

Gitlife Inactive Account Policy

1. Inactive Accounts

Definition of Inactive Accounts (must meet all conditions):

The account has had no activity (including code pushes, comments, private messages, follows, etc.) for 2 years.

The account has no repositories.

Handling of Inactive Accounts:

Only processed if another user requests the identifier (we will not proactively process inactive accounts).

Release the identifier occupied by the inactive account and assign the account a new system-generated identifier.

Send an email notification to the inactive account.

For accounts that do not meet the criteria, users may negotiate identifier usage independently.

2. Well-Known Brands and Trademarks

Handling of Appealed Accounts:

Only processed if an enterprise/organization requests the identifier (we will not proactively process).

If the appealed account meets the "Inactive Account" definition, it will be handled as an inactive account.

If the appealed account is not "inactive," the system will send an email/SMS notification to the account owner regarding the reclamation and handling process.

Without affecting normal usage, release the identifier occupied by the appealed account and assign a new system-generated identifier (the user may change it once later, with no impact on data).