大家好，

我是openEuler社区Infra-Sig组maintainer，近期对openEuler在Gitee上的代码仓库进行梳理，

发现一些不符合预期的代码仓库，需要整改，现将相关事宜知会如下：

1、openEuler社区目前的代码仓库结构：

   openEuler社区在Gitee平台有一个对应的Enterprise，名为open_euler

   其下有三个组织：

       openeuler：用于管理源码仓库，通过https://gitee.com/openeuler/community/tree/master/repository/openeuler.yaml配置文件管理

       src-openeuler：用于管理二进制仓库，通过https://gitee.com/openeuler/community/tree/master/repository/src-openeuler.yaml配置文件管理

       openEuler-competition：用于管理社区竞赛相关代码仓库，通常由相关委员会成员通知Infra-Sig组添加或删除。   

2、扫描发现部分社区成员在open_euler Enterprise下创建、Fork了部分仓库，这些仓库不属于三个组织中的任何一个，具体仓库信息见附件。

   这部分仓库通常是误操作导致，创建者在创建后又无权限删除，导致仓库残留。后续会禁用直接在企业下创建和Fork仓库的权限。

   所以Infra-Sig近期（1周后）将对上述仓库做清理，删除这些直接归属在Enterprise下的仓库。

3、清理原因：仓库占用社区资源且仓库路径容易引起混淆。

   

4、如何确认是否有自己涉及的仓库：下载附件，在附件中搜索自己的giteeId（注意是giteeId不是Gitee名称）。

    如果没有搜索到即不涉及。如果搜索到，但确认不需要该仓库，则无需特殊处理，由Infra-Sig统一清理。

5、如有特殊需求需要保留上述仓库，请联系infra@openeuler.org，说明保留仓库的原因。

  

-------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hi,

I am the maintainer of Infra-Sig of openEuler community. I recently reviewed the code repository of OpenEuler on the Giitee,

Some code repositories that do not meet expectations are found and need to be rectified. The following issues are notified:

1. The code repository structure of the openEuler community is as follows:

    The openEuler community has an enterprise named open_euler on the Gitee platform.

    There are three organizations under it:

           openeuler: manages the source code repository through the https://gitee.com/openeuler/community/tree/master/repository/openeuler.yaml configuration file.

           src-openeuler: manages the binary repository through the https://gitee.com/openeuler/community/tree/master/repository/src-openeuler.yaml configuration file.

           openEuler-competition: It is used to manage the code repository related to community competitions. Generally, the relevant committee members notify the Infra-Sig to add or delete the code repository.

2. The scan shows that some community members have created and fork some repositories under open_euler Enterprise. These repositories do not belong to any of the three organizations. For details about the repositories, see the attachment.

    These repositories are usually caused by misoperations. After being created, the creator does not have the permission to delete them. As a result, the repositories are residual. The permission to create and fork repositories in the enterprise will be disabled later.

    Therefore, Infra-Sig will clean up these repositories in the near future (one week later) and delete these repositories directly belonging to Enterprise.

3. Handling reason: The repository occupies community resources and the repository path is easy to confuse.

4. How to check whether your repository is involved: Download the attachment and search for your giteeId in the attachment (giteeId，not the name).

    If no search result is found, this issue is not involved. If the repository is found but is not need, the Infra-Sig deletes the warehouse in a unified manner.

5. If there is a special need to retain the above repositories, please contact infra@openeuler.org and explain the reason for retaining the repository.