大家好， 根据社区运营团队前期对社区所有sig组的动态数据分析，并同相关sig组沟通达成一致：建议将sig-Community和sig-bootstrap两sig组停维归档。 1、sig-Community组织在社区创立之初做了很多贡献，比如社区流程、规范建立等等，特别感谢@zerodefect、@yangli69393等所有maintainer对社区的贡献。 社区正常运作后sig-communtiy的大多数动作和功能下放到其他sig组，建议停维；sig-Community目前没有管理代码仓库，仅涉及sig组信息迁移到archived目录； 2、关于sig-bootstrap 经过sig组主要maintainer讨论达成一致认为当前无需独立sig组处理相关任务； 目前sig-bootstrap管理bazel-bin仓库，该仓库尚未有实际代码, 20年8月有一个pr提交未合入( https://gitee.com/src-openeuler/bazel-bin/pulls/1 )，之后长时间无动态。计划迁移到归档仓库sig-recycle下。 我根据以上建议新建了PR： https://gitee.com/openeuler/community/pulls/3237 欢迎留言评论。 Hi all, Based on the dynamic data analysis of all SIG groups in the community by the community operation team, It is recommended that the groups sig-Community and sig-bootstrap be discontinued and archived. 1. The sig-Community organization made a lot of contributions at the beginning of the community establishment, such as community process and standard establishment. Special thanks are given to maintainers such as @zerodefect and @yangli69393 for their contributions to the community. After the community runs normally, most actions and functions of the SIG-Community are transferred to other SIG groups. It is recommended that maintenance be stopped. Currently, the sig-Community does not manage the code repository. Only the sig group information needs to be migrated to the archived directory. 2. The main maintainer of the SIG team discussed the sig-bootstrap and agreed that the independent SIG team does not need to process related tasks. Currently, the sig-bootstrap manages the bazel-bin repository, which does not have actual code. In August 2010, a PR was submitted but not incorporated into the (https://gitee.com/src-openeuler/bazel-bin/pulls/1). After that, no dynamic information was generated for a long time. Plan to migrate the data to the archive repository sig-recycle. Based on the preceding suggestions, I created a PR： https://gitee.com/openeuler/community/pulls/3237 You are welcome to leave a message in the PR comments section or reply to the email. Best regards George
Hi George, Thanks for pointing that out. I am @zerodefect. SIG-Community was created to maintain the docs about the community, and I think this will continue later this year. Before removing this SIG, we need to make it clear who will continue to maintain the docs. I would like to leave it as it is till the end of this year. On Fri, Feb 18, 2022 at 10:39 AM myeuler@163.com <myeuler@163.com> wrote:
SIG的合并和撤销上TC审议一下吧
发自我的手机
-------- 原始邮件 -------- 发件人： George <caozhi1214@qq.com> 日期： 2022年2月18日周五 上午10:34 收件人： community@openeuler.org, dev <dev@openeuler.org>, tc@openeuler.org 主 题： [Tc] 建议社区两SIG组停止维护并归档：sig-Community，sig-bootstrap
大家好，
根据社区运营团队前期对社区所有sig组的动态数据分析，并同相关sig组沟通达成一致：建议将sig-Community和sig-bootstrap两sig组停维归档。
1、sig-Community组织在社区创立之初做了很多贡献，比如社区流程、规范建立等等，特别感谢@zerodefect、@yangli69393等所有maintainer对社区的贡献。
社区正常运作后sig-communtiy的大多数动作和功能下放到其他sig组，建议停维；sig-Community目前没有管理代码仓库，仅涉及sig组信息迁移到archived目录； 2、关于sig-bootstrap 经过sig组主要maintainer讨论达成一致认为当前无需独立sig组处理相关任务； 目前sig-bootstrap管理bazel-bin仓库，该仓库尚未有实际代码, 20年8月有一个pr提交未合入( https://gitee.com/src-openeuler/bazel-bin/pulls/1 )，之后长时间无动态。计划迁移到归档仓库sig-recycle下。
我根据以上建议新建了PR： https://gitee.com/openeuler/community/pulls/3237 欢迎留言评论。
Hi all, Based on the dynamic data analysis of all SIG groups in the community by the community operation team, It is recommended that the groups sig-Community and sig-bootstrap be discontinued and archived. 1. The sig-Community organization made a lot of contributions at the beginning of the community establishment, such as community process and standard establishment. Special thanks are given to maintainers such as @zerodefect and @yangli69393 for their contributions to the community. After the community runs normally, most actions and functions of the SIG-Community are transferred to other SIG groups. It is recommended that maintenance be stopped. Currently, the sig-Community does not manage the code repository. Only the sig group information needs to be migrated to the archived directory. 2. The main maintainer of the SIG team discussed the sig-bootstrap and agreed that the independent SIG team does not need to process related tasks. Currently, the sig-bootstrap manages the bazel-bin repository, which does not have actual code. In August 2010, a PR was submitted but not incorporated into the (https://gitee.com/src-openeuler/bazel-bin/pulls/1). After that, no dynamic information was generated for a long time. Plan to migrate the data to the archive repository sig-recycle.
Based on the preceding suggestions, I created a PR： https://gitee.com/openeuler/community/pulls/3237 You are welcome to leave a message in the PR comments section or reply to the email.
Best regards George _______________________________________________ Tc mailing list -- tc@openeuler.org To unsubscribe send an email to tc-leave@openeuler.org
_______________________________________________ Dev mailing list -- dev@openeuler.org To unsubscribe send an email to dev-leave@openeuler.org
-- Regards Fred Li (李永乐)
participants (3)
-
Fred Li -
George -
myeuler＠163.com