Hi TC members, Infrastructure team and community members,
Recently there are many issues about adding dependencies or new packages [1][2][3].
As a linux operating system, it is extremely critical to manage the dependencies. As we know, Technical committee is managing the packages management policy, however who maintain the new packages is not clear.
I have draft idea on this. Please give your advice, opinions on how to maintain the dependencies. - policy. Dependencies are still packages, thus they follow the flow on how to introduce the packages into openEuler community. - Who to maintain: if the packages are new and only dependencies, probably one specific team is an option to do this. - How to automate: Infrastructure should provide a function on getting update from upstream automatically - Dependencies management: an expert should maintain the detailed work on how to choose for ISO and yum for each specific version of release.
[1] https://gitee.com/openeuler/community-issue/issues/I1CBYV?from=project-issue [2] https://gitee.com/openeuler/community-issue/issues/I1BHND?from=project-issue [3] https://gitee.com/openeuler/community-issue/issues/I1CBW5?from=project-issue
Here are four basic strategies for discussion [1]. We should distinguish between "Common Dependent Packages" and other packages. To improve efficiency, the maintenance of the Common Dependent Packages should be the responsibility of a dedicated organization, such as the Package Committee. [2].For the Non-Common Dependent Packages, the group who import the packages first should be maintainer. [3].If other teams need to use "Non-Common Dependent Package", they should discuss with the Maintainer of this package. On the other hand, they should apply to the Package Committee When they want to use the Common Dependent Packages. [4].If more and more people use the "Non-Common Dependent Package", TC should determine whether to make the package be the "Common Dependent Package".
| | 杨丽 软件工程师 | | 华为技术有限公司 rainbow1981@163.com | 签名由网易邮箱大师定制 On 3/24/2020 11:08，Fred Liyongle.li@gmail.com wrote： Hi TC members, Infrastructure team and community members,
Recently there are many issues about adding dependencies or new packages [1][2][3].
As a linux operating system, it is extremely critical to manage the dependencies. As we know, Technical committee is managing the packages management policy, however who maintain the new packages is not clear.
I have draft idea on this. Please give your advice, opinions on how to maintain the dependencies. - policy. Dependencies are still packages, thus they follow the flow on how to introduce the packages into openEuler community. - Who to maintain: if the packages are new and only dependencies, probably one specific team is an option to do this. - How to automate: Infrastructure should provide a function on getting update from upstream automatically - Dependencies management: an expert should maintain the detailed work on how to choose for ISO and yum for each specific version of release.
[1] https://gitee.com/openeuler/community-issue/issues/I1CBYV?from=project-issue [2] https://gitee.com/openeuler/community-issue/issues/I1BHND?from=project-issue [3] https://gitee.com/openeuler/community-issue/issues/I1CBW5?from=project-issue
-- Regards Fred Li (李永乐) _______________________________________________ Community mailing list -- community@openeuler.org To unsubscribe send an email to community-leave@openeuler.org
-
Fred Li -
杨丽