You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "breautek (via GitHub)" <gi...@apache.org> on 2023/09/18 12:59:36 UTC
[GitHub] [cordova] breautek commented on issue #433: HarmonyOS Next Platform support
breautek commented on issue #433:
URL: https://github.com/apache/cordova/issues/433#issuecomment-1723357738
Apache Cordova has been downsizing quite considerably (e.g. removing OSX and windows as platforms to consolidate with Electorn, which is still missing support for some important plugins). Partly because there's only a handful of maintainers actively the project nowadays. Introducing a new platform, especially one that requires implementing compatiblity with new APIs, under a completely different build system is a daunting task... So unless if there is a large support from the community to maintain a new platform, I don't foresee a harmony platform coming to fruit. This is my own opinion.
The best way to see a harmony platform project, is to probably start a one. If supporting HarmonyJS will now require specialized tooling, then I'd recommend creating a platform. cordova-android can probably based used as a template for creating this new platform, just would have to strip out the android tooling bits and replace them with whatever what Harmony uses for it's build system. Electron has a mechanism to use `electron` plugins if available, but fallsback to `browser`. If this is applicable for Harmony, then Harmony platform could use `harmony` plugin implementation if available, but fallback to `android`, but it sounds like that might not be the case.
If a project is started with the intent to possibly get incorporated under Apache, then I'd recommend following Apache policies, namely ensuring that the project complies with the [third-party license](https://www.apache.org/legal/resolved.html) policy and is capable of producing source-only releases that can be consumed by end-users. Binary build releases is ok but they must be accompanied with a source-only release and the binary build must be built from the source-only release. Using Apache Cordova code conventions would also be ideal.
Lastly, if a harmony platform project is made, I alone cannot guarantee that project can get incorporated under Apache as that would require approval and vote from Apache and their Project Member Committee.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org