Whether the OpenHarmony adaptation of the ACL can be a use case

[leishu6]

Background OpenHarmony is an open - source project incubated and operated by the OpenAtom Foundation. Its goal is to build an operating system framework and platform for intelligent terminal devices in the era of full - scenario, full - connectivity, and full - intelligence.

We will submit the adaptation code through a pull request (PR) as soon as possible. We created this issue to have in - depth discussions with the community about merging the adaptation code. We sincerely welcome your valuable suggestions.

Adaptation Plan We have completed the adaptation of acl on OpenHarmony. The specific content is as follows:

Merge into the main community. Daily maintenance by the community. Test Results Large - scale compatibility tests have been completed, covering different versions of the HarmonyOS system and various types of Harmony devices. The test results show that the modified version is highly compatible with the HarmonyOS system, and there are no obvious stability issues.

Benefits for the Upstream Community It can reach the large user group and developer community of OpenHarmony. By supporting the trend of cutting - edge operating system development, it ensures the long - term development potential of the project. It enhances the project's processing ability in diverse operating environments.

[nfrechette]

Hello,

I'm glad you've found success with ACL.

Contributions are welcome, please take a look at the contributing guidelines in the root directory. I don't ask for much:

• Keep the coding convention similar to existing code where possible
• Follow the commit message convention where possible (Angular convention)
• Keep PRs self-contained where possible to facilitate reviewing, testing, and conversation

Cheers

[leishu6]

Could we showcase the OpenHarmony adaptation library as a usage example and add both the GitCode repository URL and OHPM binary repository links to the README documentation?

[nfrechette]

OpenHarmony does not appear to be significantly different and does not require much for ACL to compile on it as exemplified by your PRs. It thus bring very limited value for me to maintain this within ACL. In this is something you value, please keep it in your fork as it does not belong here. I do not have the resources to maintain code I cannot test on my own.

Please refrain from spamming ACL with spurious PRs.

I will also not accept adding new URLs to destinations that I do not control within the documentation for user's safety and security reasons.

Regards, Nicholas